Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
TP Profile Conversion Exit z/OS MVS Programming: Writing Transaction Schedulers for APPC/MVS SA23-1398-00 |
|||||||||||||||||||||||||||||||||||||||||
The transaction scheduler TP profile conversion exit is established when the transaction scheduler invokes the Identify service, specifying the exit name. The TP profile conversion exit allows a transaction scheduler to convert the contents of a TP Profile when the first inbound allocate request arrives for the TP. The exit then returns the converted form of the TP profile, which APPC/MVS saves and uses on subsequent inbound requests. EnvironmentThis exit is invoked on each inbound request for a TP profile that has not been previously converted and saved. The exit receives control in the following environment:
The TP profile conversion exit receives control after the unconverted TP profile is retrieved on an inbound request. The exit cannot invoke wait routines. Exit RecoveryThe caller of the exit routine should establish its own recovery
environment before calling the exit routine. The exit routine should
also establish its own recovery environment and, within its recovery,
request a tailored dump. Before each exit routine returns control
to its caller, the exit routine must delete the recovery environment
it established and free all storage it obtained. If the exit routine
does not establish its own recovery environment, the caller does the
following when the exit routine ends abnormally:
The dump and the logrec data set error record might not contain enough information to diagnose the error. For more information on providing recovery, see z/OS MVS Programming: Authorized Assembler Services Guide. Programming RequirementsTo preserve the registers of the caller, the exit routine must follow the linkage conventions described in “Linkage Conventions” in z/OS MVS Programming: Assembler Services Guide. InstallationThe TP profile conversion exit must reside in LPA or in the LNKLST concatenation. It must be a reentrant and reusable module. See the PROGxx or LNKLSTxx parmlib member description in z/OS MVS Initialization and Tuning Reference for more information about the LNKLST concatenation. Entry SpecificationsAPPC/MVS passes information to the TP profile conversion exit in registers and in a parameter list. Registers on EntryOn entry to the extract exit, the registers contain the following information:
Parameter List ContentsThe parameter list is pointed to by GPR 1, and is mapped by the ATBDFTPE mapping macro. It contains such information as:
Return SpecificationsBefore returning control to its caller, the exit must place the length of the converted TP profile in the Conv_data_length field, if the conversion was successful. Also, the exit must ensure that the register contents are as follows:
|
Copyright IBM Corporation 1990, 2014
|