![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Overview of the IMS TM Logger ExitAfter writing a record to the IMS/DB database, if IMS TM ascertains that it is appropriate according to user-supplied parameters, it calls the Logger Exit routine, DFSFLGX0, if it exists. IMS passes to the exit routine all log data after the data is all written to the IMS log. You use DFSFLGX0 to pass the log data to TIBCO Object Service Broker for processing.
x'02'= Batch IMS system (includes CICS/DLI) This field has been left here for backward compatibility. The old timestamp format value is in the 00YYDDDF HHMMSSTF format. Address of the IMS log block data that has been successfully written to the OLDS/SLDS. (This can be a copy of the original IMS buffer.) This field contains the current data and time fields, but in the IMS internal packed-decimal format. For further information on the internal packed-decimal time-stamp format, refer to IMS Version 7 Application Programming: Transaction Manager or IMS Version 7 Database Recovery Control (DBRC) Guide and Reference, or subsequent manuals. This field contains the current date and time fields, but in the IMS internal packed-decimal format. For further information on the internal packed-decimal time-stamp format, refer to IMS Version 7 Application Programming: Transaction Manager or IMS Version 7 Database Recovery Control (DBRC) Guide and Reference, or subsequent manuals. Refer the LGWXTOD field for the timestamp format used prior to IMS/ESA V6.IMS calls the Logger Exit routine with an initialization call when the logger is opened and with a termination call when the logger is closed. IMS also calls the exit routine and passes log data to it with a write call whenever a block of data is written to the logger.The Logger Exit routine uses the TIBCO Object Service Broker Call Level Interface to communicate with TIBCO Object Service Broker.
1. Using IEBCOPY, copy the IMS Logger Exit routine S6BFLGX0 and its alias DFSFLGX0 as one entity into either the IMS.SDFSRESL library or another PDS data set concatenated to STEPLIB. This library must be a PDS data set. If the library is a PDSE or the module is not present in STEPLIB, the IMS Transaction Manager control region will not load the exit nor issue any error message.
− Include the TIBCO Object Service Broker supplied $HLQNONV$.$INSTVER$.AUTH library in the STEPLIB concatenation in the IMS control region.//STEPLIB DD DISP=SHR,DSN=IMS.SDFSRESL
// DD DISP=SHR,DSN=customer.pds.containing.DFSFLGX0
...
// DD DISP=SHR,DSN=$HLQNONV$.$INSTVER$.AUTH
...
− Add a //HRNLIB DD statement pointing to the $HLQNONV$.$INSTVER$.AUTH library:
3. Include a DD statement for the HRNIN data set which should contain the following Execution Environment parameters:
4.
5.
6. The Logger exit will pass to the IMS_LOGGER rule a DATAIN area containing 2 format1 blocks of data: the first block is the IMS function-specific parameter list and the second block is the IMS log block. For details refer to Format 1 DATAIN, and the IBM manual: IMS Customization Guide (SC26-9427-05)
• The Exit was doing the STARTEE operation and was not successful, in this case the DOB was not up.
− END – if the problem can not be corrected without re-cycling the IMS, then reply END to the WTOR message to end the WTOR task so that IMS can be shutdown gracefully.
• The two first messages with the time stamp were put out by the test rule, they were not from the Logger Exit.
• The Exit was doing the CALLRULE operation and was timed out, in this case the IMS_LOGGER rule was deliberately in a “wait” and the wait time is longer than the timeout interval set by the CLITIMEOUTLIMIT= value.
Refer to TIBCO Object Service Broker Parameters for information about the CLITIMEOUTLIMIT Execution Environment parameter.END – if the problem can not be corrected without re-cycling the IMS, then reply END to the WTOR message to end the WTOR task so that IMS can be shutdown gracefully (illustrated in this case).
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |