z/OS BDT Installation
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


BDTUX17—BDT Job Start

z/OS BDT Installation
SC14-7582-00

Type

Customization (optional).

General Description

This exit routine can be implemented to provide information about the execution time of a job. If your installation does not use SMF accounting, or you wish to supplement IBM’s SMF provisions within BDT, this exit routine and BDTUX18 are provided for your use.

This exit routine is invoked for inbound and outbound file-to-file jobs and outbound (but not inbound) SNA NJE jobs. This exit routine runs in the scheduling processor when the processor is notified that the remote processor is ready to send or receive the job.

Register Conventions at Entry

BDTXCALL linkage is used to interface with the BDTUX17 user exit routine. Registers 2-14 are saved by BDT ASAVE processing.
Register 1
Contains the address of a one-word parameter list:
Word 1
The address of the JCT entry for the job
Register 12
Contains the address of the TVT.
Register 13
Contains the address of the register save area set up by ASAVE processing.
Register 14
Contains the address of the return point, which is saved in BDTGRSV.
Register 15
Contains the entry point address in BDTUX17.

Register Conventions at Exit

Because BDTXCALL linkage is used to establish the interface to the BDTUX17 user exit routine, registers 2-14 of BDTJSFT (for file-to-file jobs) or BDTJSNT (for SNA NJE jobs) are saved in BDTGRSV. You must store registers 12, 13, and 14 in an area you provide (either an area obtained by GETMAIN or one within your user exit routine), and those registers must be restored on return to BDTGRSV by register 14.
Register 14
Contains the address of the return point in the ASAVE routine (BDTGRSV).

Operation

This exit routine runs when the scheduling processor is notified that the remote processor has scheduled the job. This exit routine can record information in the job control table about the scheduling of the DAPs while BDTUX18 can record information about the end of a transfer.

See Initialization Flow and User Exit Routines for a diagram that depicts the steps that precede the invocation of this user exit routine.

Recovery the Exit Routine Must Establish: You should provide ESTAE protection for your user exit routine. If you do not supply an ESTAE, clean-up is provided for the user exit routine by an ESTAE exit routine established in BDTABMN.

Environment

Point Where Exit Routine Receives Control: BDTUX17 is invoked when the scheduling processor is notified that the remote processor has scheduled the job. BDTUX17 is invoked from BDTJSFT if the job is a file-to-file job, or from BDTJSNT if the job is a SNA NJE job.

Address Space in Which Exit Routine Runs: BDT address space.

Task under Which Exit Routine Runs: This exit routine runs under BDTGRJS’s TCB.

PSW State: Supervisor.

Storage Protection Key: BDTKEY (key 8).

Data Areas

Mapping Macros
  • BDTDGSD to map the GSD (for coding an ESTAE)
  • BDTDJCT to map the JCT
  • BDTDREG to map the registers
  • BDTDTVT to map the TVT
Executable Macros
  • BDTXASRV to invoke abend services for abend recovery processing

What If BDTUX17 Is Not Used?

If this exit routine is not coded, scheduled processing continues normally.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014