Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
SB - Starting a session with a BLDL identifier z/OS MVS Program Management: Advanced Facilities SA23-1392-00 |
|||||||||||||||||||||
The calling application identifies the program object by providing an open DCB and an entry returned by the MVS™ BLDL service.
This service is primarily designed for DCBs opened within the job step in the job step key. It can, however, also be used for DCBs opened by MVS, such as JOBLIB/STEPLIB, LINKLIB, or PGM=*.DD. The service makes a number of tests to determine if the DCB passed by the caller can be used. These tests involve the access method and record format specified when the DCB is opened, the key in the DCB that is opened, and the current program authorization level. If the DCB cannot be used, the service attempts to open a DCB for the same DDname. If the DDname exists, but the OPEN fails, the request is rejected. Reason codes are expected from an SJ request rather than an SB request. If the caller's DCB cannot be used, and the DDname does not exist for the current job step (as is the case for the LINKLIB DCB), a special authorized service is used to read the program object. In this case, the program object image is maintained in 31-bit storage within the address space rather than in 64-bit storage. This can change the storage requirements significantly. Sample assembler code
|
Copyright IBM Corporation 1990, 2014
|