Figures

  1. Examples of distributed resources
  2. A sysplex (SYSPLEX1) comprising two MVS images (MVS1 and MVS2)
  3. A possible configuration for intercommunicating systems
  4. Function shipping
  5. The transformer program and the mirror in function shipping
  6. ISC function shipping--simple inquiry
  7. MRO function shipping--simple inquiry
  8. MRO function shipping--simple inquiry
  9. ISC or MRO function shipping--update
  10. ISC or MRO function shipping--update with ABEND
  11. Synchronous and asynchronous processing compared
  12. Asynchronous processing--remote transaction initiation
  13. Asynchronous processing--remote transaction initiation using NOCHECK
  14. Dynamic routing using a "hub" routing model
  15. Dynamic routing using a distributed routing model
  16. The elements of transaction routing
  17. ATI-initiated transaction routing
  18. Failure of an ATI request in a system where the termid is unknown
  19. Resolving a ‘terminal not known’ condition on a START request
  20. Function-shipped START request started against an incorrect terminal
  21. Static routing of a terminal-related START command issued in an AOR, using the enhanced method
  22. Dynamic routing of a terminal-related START command issued in an AOR
  23. Static routing of a terminal-related START command issued in a TOR, using the enhanced method
  24. Dynamic routing of a terminal-related START command issued in a TOR
  25. Transaction routing to an APPC terminal across daisy-chained systems
  26. Distributed program link
  27. The transformer program and the mirror in DPL
  28. DPL with the client transaction issuing a syncpoint
  29. DPL with the server program abending
  30. DTP in a multisystem configuration
  31. A typical IMS logmode table entry
  32. The figure shows two sysplexes, SYSPLEXL and SYSPLEXR
  33. Second flow, CICSL2-CICSR
  34. Third flow, CICSR1-CICSL
  35. Fourth flow, CICSR2-CICSL
  36. Example JCL for submitting the ENDAFFINITY program
  37. A network hub
  38. Defining an MRO link
  39. Example of MRO link definition
  40. Defining compatible MRO nodes
  41. Example definition for a specific EXCI connection
  42. Example definition for a generic EXCI connection
  43. Defining an APPC system
  44. Defining a group of APPC sessions
  45. Defining compatible CICS APPC ISC nodes
  46. Defining an LUTYPE6.1 link with individual sessions
  47. Defining compatible CICS and IMS nodes
  48. Defining multiple links to an IMS node
  49. Indirect links for transaction routing
  50. Defining indirect links for transaction routing
  51. Making the connection unavailable
  52. Local and remote resource names
  53. Defining a remote file (function shipping)
  54. Macro for defining remote DL/I PSBs
  55. Sample definitions for remote transient data queues
  56. Macro for defining remote temporary storage queues
  57. Defining a remote program (DPL)
  58. Defining a remote transaction (asynchronous processing)
  59. Defining a remote VTAM terminal (transaction routing)
  60. Defining a remote APPC connection (transaction routing)
  61. Defining a shippable terminal (transaction routing)
  62. Defining a remote non-VTAM terminal (transaction routing)
  63. Typical use of DFHTCT TYPE=REMOTE macro
  64. Typical use of DFHTCT TYPE=REGION macro
  65. Identifying a terminal-owning region
  66. Local and remote names for remote terminals
  67. The CEDA DEFINE TRANSACTION options
  68. Main attributes of the CICS-supplied CRTX transaction
  69. Defining a remote partner
  70. Defining a communication profile
  71. CICS architected process names
  72. Some definitions required for ISC and MRO
  73. Defining an intrapartition transient data queue
  74. Basic IMS message queuing
  75. START and RETRIEVE asynchronous processing-CICS front end
  76. RETRIEVE and START asynchronous processing - IMS front end
  77. SEND and RECEIVE asynchronous processing - CICS front end
  78. Syncpointing flows--unique session
  79. Syncpointing flows--chained sessions
  80. Syncpointing flows--multiple sessions
  81. CEMT INQUIRE CONNECTION--connections owned by system IYLX1
  82. CEMT INQUIRE CONNECTION--details of connection ISC4
  83. CEMT INQUIRE UOWLINK--UOWs that require resynchronization with system IYLX4
  84. CEMT INQUIRE UOWLINK--detailed information for UOW-link 016C0005
  85. CEMT INQUIRE UOW LINK(IYLX4)--all UOWs that have IYLX4 as the coordinator
  86. CEMT INQUIRE UOW LINK(IYLX4)--detailed information for UOW ABD40B40C1334401
  87. CEMT INQUIRE UOWENQ--resources locked by all shunted UOWs
  88. CEMT INQUIRE UOWENQ--resources locked by UOW ABD40B40C1334401
  89. CEMT INQUIRE UOWENQ--detailed information for UOWENQ ABD40B40C1334401
[[ Contents Previous Page | Next Page Index ]]