Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
BDTUX08—User-Defined File-to-File Transaction Keywords z/OS BDT Installation SC14-7582-00 |
|
TypeCustomization (optional). General DescriptionThis exit routine allows an installation to define additional keywords that can be specified on file-to-file transactions. BDTUX08 extends the language processor’s keyword table. The extension is built through the use of the BDTDKYWD macro. This macro generates entries in the user-defined keyword table extension located in a data CSECT called UX08KYWD. The macro creates one or more entries in the CSECT. BDTDKYWD issues BDTDTUD, another macro, which creates the corresponding text unit descriptor entries located in the data CSECT UX08TUD. When the language processor reaches the end of BDT’s keyword table without finding the keyword, it starts searching the user-defined keyword table located in BDTUX08. Register Conventions at EntryBecause this exit routine is only a table and not executable code, there are no registers involved. Register Conventions at ExitBecause this exit routine is only a table and not executable code, there are no registers involved. OperationThe data CSECT called UX08KYWD is created as the extension to the language
processor’s keyword table. You should use the BDTDKYWD macro to create
the keyword entries that make up this extension. An associated text unit
descriptor entry may also be created. The CSECT name, UX08KYWD, is generated
when the BDTDKYWD macro is used.
Note: The default, &USER=YES,
must be specified when coding the BDTDKYWD macro.
Since this exit routine is part of the language processor, it must be link-edited with the language processor load module, which may be loaded into the link pack area. Loading exit routines in the link pack area requires an MVS IPL. Any exit routines loaded in the link pack area (BDTUX08, BDTUX10, BDTUX19, and BDTUX28) should be link-edited at the same time. This prevents the need for you to perform more than one MVS IPL to load those exit routines. EnvironmentPoint Where Exit Routine Receives Control: BDTLP invokes BDTUX08 when it reaches the end of BDT’s keyword table without finding a keyword. Address Space in Which Exit Routine Runs: User’s address space (JES3, TSO, or batch) and BDT address space. Task under Which Exit Routine Runs: Because the language processor (BDTLP) is reentrant, it can be used by more than one user at a time. This exit routine operates under the TCB of the module that invokes the services of the language processor. Those modules include IGX0034, BDTGRXD, BDTCMDV, BDTTQI, and IATBDCI, a JES3 module. PSW State: Supervisor. Storage Protection Key: The language processor, from which this exit routine is invoked, runs in the key of the user. This key can be the user’s (key 8), JES3 (key 1), or key 0 from SVC 109. Data AreasMapping Macros
What If BDTUX08 Is Not Used?If this exit routine is not provided, a user-defined keyword not recognized by the language processor will result in message BDT1003 being issued and the unrecognized keyword displayed. The file-to-file transaction fails. |
Copyright IBM Corporation 1990, 2014
|