ASSBJBNI and ASSBJBNS were introduced in MVS/ESA SP5.1.0 (HBB5510). If you are accessing an ASCB other than your home space, they can be safer to use. If you are disabled for I/O and External interrupts, and then validate the ASCB by locating via the LOCASCB macro, the ASCB/ASSB storage cannot be freed while you remain disabled. The fields pointed to by ASCBJBNI and ASCBJBNS are located in an extension of the CSCB, and disablement does not prevent that storage from being freed.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <[email protected]> wrote on 10/12/2018 11:03:27 AM: > From: "Rob Scott" <[email protected]> > To: [email protected] > Date: 10/12/2018 11:49 AM > Subject: Re: Reasons for address space with no JSAB/other sources of job name > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > Non-JSAB jobname(s) can be found in ASSBJBNI and ASSBJBNS as 8-byte > char fields. > > Also, ASCBJBNI and ASCBJBNS may contain 31-bit pointers to storage > that contain the same values as ASSBJBNI and ASSBJBNS. > > I believe the ASSB variants were introduced in later in MVS history > - but maybe are more convenient as you don’t have to dereference them. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
