> And given that this is about the INIT, if the ALC program is in > an APF load lib and the load lib for the COBOL program is NON APF > this JOBSTEP already failed.
No, being in an APF authorized concatenation is not enough to make the programm authorized. As long as the program object (load module) has the default AC(0), it is unauthorized regardless of where it is loaded. The only effect of authorized libraries on an AC(0) jobstep is what subpool it goes into. > How often have you seen an APF LOADLIB contain COBOL based modules? Is there an RFE for a secondary linklist that is not used when the jobstep is authorized? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Steve Thompson [ste...@wkyr.net] Sent: Wednesday, August 16, 2023 2:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Pass PARM by reference to COBOL What would that accomplish? Telling the INIT the AMODE of the program; That is going to be gotten from the PDS/PDSE directory. And given that this is about the INIT, if the ALC program is in an APF load lib and the load lib for the COBOL program is NON APF this JOBSTEP already failed. How often have you seen an APF LOADLIB contain COBOL based modules? Ok, I know you can do it, because I have while running certain tests. Steve Thompson On 8/16/2023 2:23 PM, Seymour J Metz wrote: >> Irrelevant pedantry. > Nonsense. > >> I hope that my explicit qualification, "as an Assembler program might" >> precludes cases in which the PARM is in R/O storage, > It doesn't. If the caller is RENT from an authorized concatenation and the > PARM is a constant in the csect, it will be in SP252. > >> That's a horrible misdesign. > I don't like what the Initiator does, but it is BAD and documented. > >> Second choice would be to add an >> option to EXEC indicating the AMODE of the PGM. > RFE? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of > Paul Gilmartin [0000042bfe9c879d-dmarc-requ...@listserv.ua.edu] > Sent: Wednesday, August 16, 2023 1:49 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Pass PARM by reference to COBOL > > On Wed, 16 Aug 2023 13:44:34 +0000, Seymour J Metz wrote: > >> What the called program can do depends on the caller. The PARM might be in >> R/O storage. >> > Irrelevant pedantry. I hope that my explicit qualification, "as an Assembler > program might" > precludes cases in which the PARM is in R/O storage, not addressable, etc. > >> The Initiator does not pass a 64-bit PARM. >> > That's a horrible misdesign. It introduces a persistent incompatibility > between CALL/LINK/ATTACH and EXEC PGM=. > > Regardless of the difficulty of sussing the AMODE of the PGM, the > initiator should have done so. Second choice would be to add an > option to EXEC indicating the AMODE of the PGM. > > ________________________________________ > From: Paul Gilmartin > Sent: Wednesday, August 16, 2023 9:18 AM > > PARM is uniformly passed to a program by reference: > R1 -> x'80000000' + -> halfword length || parameter string > > If a COBOL program is called by a program other than Initiator, can > it modify that parameter string as an Assembler program might to > return a value to the caller? > > (If a program is marked AMODE 64, does Initiator pass a 64-bit PLIST?) > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Regards, Steve Thompson VS Strategies LLC Westfield IN 972-983-9430 cell ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
