Ibm SC33-1683-02 Bedienungsanleitung Seite 589
- Seite / 875
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
v If you want to keep information about how transactions are routed, it must be
done in the user routing program, perhaps by writing the information to a
temporary storage queue associated with this terminal.
v Several transactions can form a single conversation with the end user. At the
start of the conversation, resources are allocated to record the state of the
conversation. Because these resources are local to the system to which the first
transaction in the conversation was routed, the routing program must be able to
continue to route to this system until the end of the conversation.
v It is important to avoid creating “tangled daisychains”: for any transaction that is
being dynamically routed, you must avoid routing back to a node that has
previously been routed from.
v The dynamic routing program can be RMODE ANY but must be AMODE 31.
Unit of work considerations
Depending on the terminal type, the CICS relay program, the dynamic routing
program, and the routed transaction may constitute a single unit of work. Any
protected resources owned by the dynamic routing program could therefore be
affected by the syncpoint activity of the routed transaction. This means that these
resources may be committed or backed out inadvertently by the routed transaction.
If you want to avoid this, you have to define the routing program’s resources as
unprotected rather than protected.
Dynamic routing of DPL requests
For a program-link request to be eligible for dynamic routing, the remote program
must either:
v Be defined to the local system as DYNAMIC(YES)
or
v Not be defined to the local system.
Note: If the program specified on an EXEC CICS LINK command is not currently
defined, what happens next depends on whether program autoinstall is
active:
– If program autoinstall is inactive, the dynamic routing program is
invoked.
– If program autoinstall is active, the autoinstall user program is invoked.
The dynamic routing program is then invoked only if the autoinstall
user program:
- Installs a program definition that specifies DYNAMIC(YES), or
- Does not install a program definition.
See “Autoinstalling programs invoked by EXEC CICS LINK commands”
on page 540.
As well as “traditional” CICS-to-CICS DPL calls instigated by EXEC CICS LINK
PROGRAM commands, program-link requests received from outside CICS can also
be dynamically routed. For example, all the following types of program-link request
can be dynamically routed:
v Calls received from:
– The CICS Web Interface
dynamic transaction routing
Chapter 16. Writing a dynamic routing program 557
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- CICS Customization Guide 1
- Contents 5
- Contents v 7
- Contents vii 9
- Contents ix 11
- Contents xi 13
- Contents xiii 15
- Contents xv 17
- Trademarks 21
- What this book is about 23
- Who this book is for 23
- How to use this book 23
- Notes on terminology 23
- Bibliography 25
- Other CICS books 26
- Books from related libraries 26
- ACF/TCAM books 26
- MVS books 27
- VTAM books 27
- Other related books 27
- Summary of changes 29
- Summary of changes xxix 31
- Performance Guide 32
- Global user exit programs 36
- Register conventions 36
- Using CICS services 37
- The global work area 38
- Making trace entries 39
- DFHUEPAR standard parameters 40
- 12 (decimal) 41
- 12 (decimal) in this 41
- Returning values to CICS 42
- Errors in user exit programs 44
- The DFH$PCPI program: 47
- Sample program definitions: 48
- Resource Definition Guide 49
- CICS Shared Data 49
- Tables Guide 49
- Exit XAKUSER 57
- WRITE JOURNALNAME 58
- Important 58
- Basic Mapping Support exits 59
- Exit XBMIN 60
- Exit XBMOUT 60
- Programming the XBMIN exit 62
- Programming the XBMOUT exit 62
- Cumulative mapping operations 63
- Message routing 63
- Bridge facility exit 64
- Exit XFAINTU 64
- Exit XDTRD 65
- Exit XDTAD 68
- Exit XDTLC 69
- Exit XXDFB 72
- Exit XXDTO 73
- Exit XDSBWT 74
- Exit XDSAWT 74
- DL/I interface program exits 76
- Exit XDLIPRE 77
- Exit XDLIPOST 79
- Exit XDUREQ 81
- Exit XDUREQC 84
- Exit XDUCLSE 87
- Exit XDUOUT 87
- Exit XNQEREQ 89
- Exit XNQEREQC 90
- Sample exit program, DFH$XNQE 95
- The command parameter list 97
- Bypassing commands 98
- Exit XEIIN 98
- Exit XEISPIN 99
- Exit XEIOUT 100
- Exit XEISPOUT 100
- EXEC interface program exits 101
- Modifying input fields 107
- Modifying the EID 108
- Use of the parameter UEPFSHIP 109
- Exit XFCREQ 111
- Exit XFCREQC 112
- Example program 114
- Exit XFCAREQ 116
- Exit XFCAREQC 117
- Modifying user arguments 127
- Exit XFCSREQ 129
- Exit XFCSREQC 132
- Recovery and Restart Guide 137
- Exit XFCNREC 138
- Exit XFCVSDS 140
- file control quiesce send exit 142
- Order of invocation 144
- Migration note 149
- The XISCONA exit 159
- Exit XISCONA 160
- CICS Performance Guide 161
- The XISLCLQ exit 162
- Exit XICREQ 164
- Exit XICEXP 165
- Exit XICTENF 165
- XICEREQC 166
- Exit XICEREQ 166
- Exit XICEREQC 167
- Modifying output fields 174
- Using the task token UEPTSTOK 177
- CICS Intercommunication Guide 178
- Exit XLDLOAD 179
- Exit XLDELETE 180
- OS/390 MVS Authorized 181
- Exit XLGSTRM 182
- Message domain exit XMEOUT 184
- Exit XMEOUT 185
- Monitoring domain exit XMNOUT 188
- Exit XMNOUT 188
- XPCHAIR, XPCTA, and XPCABND 190
- XPCREQ and XPCREQC 190
- Exit XPCREQC 191
- Modifying input fields: 194
- Modifying output fields: 194
- In XPCREQ: 196
- In XPCREQC: 196
- Exit XPCFTCH 197
- Exit XPCHAIR 198
- Exit XPCTA 200
- Exit XPCABND 201
- Exit XRMIIN 203
- Exit XRMIOUT 204
- Exit XRSINDI 205
- Exit XSNON 209
- Exit XSNOFF 210
- UERCPURG 211
- Task purged during XPI call 211
- XPI calls 211
- All can be used 211
- Statistics domain exit XSTOUT 212
- Exit XSTOUT 212
- Exit XSRAB 214
- could be determined 215
- CICS Data Areas 216
- Exit XSTERM 218
- XTSPTOUT 219
- Exit XTSQRIN 219
- Exit XTSQROUT 220
- Exit XTSPTIN 222
- Exit XTSPTOUT 223
- XTSEREQC 225
- Exit XTSEREQ 226
- Exit XTSEREQC 227
- Command See 228
- WRITEQ TS Table 7 on page 200 228
- READQ TS Table 8 on page 200 228
- Adding user arguments 233
- Removing user arguments 233
- Exit XALCAID 235
- Exit XTCIN 237
- Exit XTCOUT 237
- Exit XTCATT 238
- Exit XTCTIN 238
- Exit XTCTOUT 239
- The exits 240
- Exit XALTENF 241
- Exit XXMATT 248
- Exit XTDREQ 250
- Exit XTDIN 251
- Exit XTDOUT 252
- XTDEREQC 253
- Exit XTDEREQ 253
- Exit XTDEREQC 255
- Coding the exit programs 262
- Enabling the exit programs 263
- Exit XRCINIT 264
- Exit XRCINPT 264
- Exit XZCATT 266
- Exit XZCIN 267
- Exit XZCOUT 267
- Exit XZCOUT1 268
- VTAM working-set module exits 269
- Exit XZIQUE 272
- Design considerations 275
- Sample exit program design 276
- Exit XXRSTAT 278
- The stub program 282
- Figure 5. The stub concept 283
- User exit parameter lists 285
- Caller parameter lists 289
- CICS task manager parameters: 292
- CICS EDF build parameters: 293
- The schedule flag word 297
- Saving CICS registers 298
- Addressing-mode implications 299
- Work areas 301
- CICS System 302
- Programming Reference 302
- Return codes 303
- Limitations 304
- Resynchronization 306
- (Part 1 of 2) 309
- (Part 2 of 2) 310
- ) and (E 311
- ) expressions in Figure 10 311
- Adapter administration 312
- The administration routines 313
- TRACETYPE command 314
- Overview 315
- General form of an XPI call 318
- DFHUEXIT TYPE=XPIENV 322
- XPI register usage 323
- The XPI copy books 323
- XPI examples 325
- The XPI functions 330
- OPTION(addr,len) 331
- OPTION(bufdname) 331
- OPTION(addr,maxlen,*) 331
- Dispatcher functions 332
- The ADD_SUSPEND call 334
- The SUSPEND call 336
- The RESUME call 339
- The DELETE_SUSPEND call 340
- The WAIT_MVS call 341
- CICS Problem Determination 343
- The CHANGE_PRIORITY call 345
- Dump control functions 346
- The SYSTEM_DUMP call 346
- RESPONSE REASON 347
- The TRANSACTION_DUMP call 348
- Enqueue domain functions 350
- The ENQUEUE function 350
- The DEQUEUE function 351
- Kernel domain functions 352
- Loader functions 353
- The DEFINE_PROGRAM call 353
- The ACQUIRE_PROGRAM call 357
- The RELEASE_PROGRAM call 359
- The DELETE_PROGRAM call 360
- Log manager functions 361
- The INQUIRE_PARAMETERS call 361
- The SET_PARAMETERS call 361
- Monitoring functions 362
- The MONITOR call 362
- CICS Resource Definition Guide 363
- Program management functions 366
- The INQUIRE_PROGRAM call 367
- Intercommunication Guide 368
- The SET_PROGRAM call 375
- The START_BROWSE_PROGRAM call 378
- The GET_NEXT_PROGRAM call 379
- The END_BROWSE_PROGRAM call 381
- The INQUIRE_AUTOINSTALL call 382
- The SET_AUTOINSTALL call 382
- State data access functions 384
- The INQ_APPLICATION_DATA call 384
- The INQUIRE_SYSTEM call 387
- The SET_SYSTEM call 391
- Storage control functions 393
- The GETMAIN call 393
- The FREEMAIN call 396
- The INQUIRE_ACCESS call 396
- INQUIRE_ELEMENT_LENGTH: 398
- The INQUIRE_TASK_STORAGE call 399
- The SWITCH_SUBSPACE call 400
- Trace control function 401
- The TRACE_PUT call 401
- The INQUIRE_CONTEXT call 402
- The INQUIRE_DTRTRAN call 403
- The INQUIRE_MXT call 404
- The INQUIRE_TCLASS call 406
- The INQUIRE_TRANDEF call 407
- The INQUIRE_TRANSACTION call 415
- The SET_TRANSACTION call 419
- User journaling function 420
- The WRITE_JOURNAL_DATA call 420
- Initialization programs 425
- First phase PLT programs 425
- Second phase PLT programs 426
- Shutdown programs 426
- General considerations 428
- Storage keys for PLT programs 428
- PLT programs—general 429
- IBM ESA/370 Principles of 433
- Operation 433
- CICS System Definition Guide 434
- CICS Recovery and 439
- Restart Guide 439
- Terminal control program 448
- Terminal error program 448
- The communication area 449
- TEP error table 450
- TEP default table 451
- Entry and initialization 452
- Error processor selection 452
- Error processing execution 452
- General exit 453
- Common subroutines 453
- DFHTEPM TYPE=USTOR 458
- DFHTEPM TYPE=USTOREND 458
- DFHTEPM macro examples 462
- DFHTEPT TYPE=INITIAL 464
- ,MAXTIDS=number 464
- [,MAXERRS={25 464
- [,OPTIONS={TIME 464
- Name Type Description Library 470
- CICSTS13.CICS.SDFHMAC 470
- increased by 473
- 8 in real TCTLE) 473
- USING DFHTCTTE,TCTTEAR 474
- DROP TCTLEAR 474
- USING DFHTCTLE,TCTLEAR 474
- CICS Intercommunication 481
- An overview of writing a NEP 483
- The default NEP 484
- The sample NEP 484
- Coding the sample NEP 485
- Multiple NEPs 487
- The sample node error program 497
- Entry section 498
- Routing mechanism 499
- Node error table 499
- Optional common subroutines 500
- Table 22. Register assignment 504
- Entry and addressability 508
- Coding for session failures 509
- Writing multiple NEPs 510
- DFHZNEPI macros 510
- CICS/ESA 3.3 XRF 512
- Changing the recovery message 514
- Preliminary considerations 517
- Coding entries for MTS 519
- SNA Network Product Formats 520
- Returning information to CICS 523
- CICS Resource Definition 524
- Setting the TERMINAL name 525
- WAS MODEL_NAME: mmmmmmmm 526
- CINIT BIND: cccccccc... 526
- MODEL BIND: bbbbbbbb... 526
- MISMATCH BITS: xxxxxxxx 526
- Testing and debugging 528
- Definition Guide 530
- Assembler language 531
- Leaving it all to CICS 537
- Benefits of autoinstall 546
- Requirements for autoinstall 546
- Recovery and restart 547
- Resource definitions 553
- CICS-generated aliases 556
- Autoinstall models 563
- Terminal identifiers 564
- Why override TERMIDs? 565
- Autoinstall model definitions 572
- System autoinstall 573
- Saving in virtual storage 573
- Faster startup times 574
- Resource definition 579
- Dynamic transaction routing 582
- Dynamic transactions 582
- Changing the program name 585
- CICS Application Programming 587
- Monitoring the output TIOA 588
- Unit of work considerations 589
- Changing the transaction ID 592
- ‘tranid’ 598
- Reference 599
- System Programming Reference 605
- CICS Business Transaction 611
- Services 611
- CICS System Programming 612
- External Interfaces Guide 631
- CICS Internet Guide 633
- Environment variables 635
- IBM ESA/370 Principles 640
- The sample overseer program 641
- The display function 642
- The restart-in-place function 643
- CICS Operations and 644
- Utilities Guide 644
- The DFHWOSM macros 646
- The DFHWOSM tokens 647
- DFHWOSM FUNC=BUILD macro 647
- DFHWOSM FUNC=CLOSE macro 648
- DFHWOSM FUNC=DSECT macro 648
- DFHWOSM FUNC=JJC macro 648
- DFHWOSM FUNC={JJS 649
- DFHWOSM FUNC=OPEN macro 650
- DFHWOSM FUNC=OSCMD macro 650
- DFHWOSM FUNC=READ macro 651
- DFHWOSM macros 652
- DFHWOSM FUNC=TERM macro 654
- Loop or wait detection 656
- IBM ESA/370 660
- Principles of Operation 660
- Log stream storage 661
- Primary storage 662
- Tertiary storage 662
- Secondary storage 662
- Fixed length 666
- Reserved 667
- Start-of-run record 668
- Format of caller data 668
- Variable length 669
- FLJB GENERAL DATA 672
- FLJB DELETE DATA 672
- Fixed length Variable length 672
- Base key Path key 672
- File-close record types 673
- Tie-up record types 674
- Terminal control prefix data 676
- FEPI prefix data 676
- System header 680
- User prefix Journal data 680
- System prefix 680
- Variable 682
- The SMF block header 686
- The CICS product section 686
- The CICS data section 687
- Chapter 24. CICS monitoring 689
- DFHMCT TYPE=EMP 691
- DFHMCT TYPE=RECORD 691
- Examples of MCT coding 692
- Exception class data 693
- Controlling CICS monitoring 694
- CICS Supplied Transactions 695
- OS/390 MVS System Management 697
- Facilities (SMF) 697
- CICS data section 698
- Performance data sections 704
- Exception data sections 706
- CICS Performance 707
- Chapter 25. CICS statistics 709
- Resetting statistics counters 713
- CICS statistics record format 714
- STSMFDS DFHSTSMF PREFIX=SMF 715
- CICS statistics data section 717
- CICS with TCAM SNA 724
- Protocol management 724
- Transaction control 725
- Batch processing 726
- Error processing 726
- The CICS-TCAM interface 727
- Data format 728
- Logic flow 729
- Segment processing 732
- Line pool specifications 733
- Line locking 734
- TCAM queues 735
- TCAM devices 736
- TCAM with 3270 devices 738
- TCAM user exits 739
- Starting and terminating TCAM 739
- CICS-TCAM startup 739
- CICS-TCAM abend and restart 739
- CICS-TCAM termination 740
- TCAM MCP 741
- CICS Application program 741
- Terminal operation 746
- Help feature 747
- DYNALLOC flow of control 749
- CICS RACF Security 752
- The MVS router 753
- The MVS router exit 754
- Router exit return codes 755
- ESM exit programs 756
- CICS security control points 759
- Early verification processing 761
- INCLUDE SYSLIB(DFHXSEAI) 763
- INCLUDE SYSLIB(DFHEAI) 763
- ENTRY verify-program 763
- *ASM XOPTS(NOPROLOG,NOEPILOG) 763
- What the sample program does 768
- An overview of DFHCSDUP 773
- DFHCSDUP as a batch program 774
- The EXTRACT command 774
- The sample EXTRACT programs 776
- The DB2 formatting program 778
- An assembler-language version 780
- A VS COBOL II version 781
- A PL/I version 782
- Entry parameters for DFHCSDUP 784
- The initialization exit 787
- The get-command exit 788
- The extract exit 789
- The put-message exit 791
- The sample program, DFH$CUS1 792
- COMMAREA(CEDAPARM) 793
- CICS Distributed 794
- Transaction Programming Guide 794
- DFHEDAP in a DTP environment 795
- Part 9. Appendixes 797
- TYPETERM device types 800
- VTAM MODEENT macro operands 802
- PSERVIC screen size values 807
- Messages and Codes 821
- CICS Messages and Codes 832
- (DFH$TDWT) 835
- Using the XZCIN exit 837
- Using DFHTCTDY 837
- TS data sharing messages 838
- Special Characters 855
- Numerics 855
- (continued) 856
- Index 827 859
- Sending your comments to IBM 873
- SC33-1683-02 874
- Spine information: 875
Verwandte Produkte und Handbücher für Computers Ibm SC33-1683-02
Computers Ibm H SERIES RS/6000 Bedienungsanleitung
(290 Seiten)
(290 Seiten)
Computers Ibm 3.1 Bedienungsanleitung
(12 Seiten)
(12 Seiten)
Computers Ibm xSeries 330 Bedienungsanleitung
(158 Seiten)
(158 Seiten)
Computers Ibm SC34-6814-04 Bedienungsanleitung
(953 Seiten)
(953 Seiten)
Computers Ibm System x3400 Bedienungsanleitung
(15 Seiten)
(15 Seiten)
Computers Ibm 6274 Bedienungsanleitung
(96 Seiten)
(96 Seiten)
Whirlpool GE641TX manuály
Uživatelské manuály a uživatelské příručky pro Sporáky Whirlpool GE641TX.
Poskytujeme 1 manuály pdf Whirlpool GE641TX ke stažení zdarma podle typů dokumentů: Návod k použití
Kommentare zu diesen Handbüchern