I'm having trouble imagining a scenario where an EBCDIC representation of an address would be useful. The problem is, in a job step situation, how would you figure out an address to pass?
//STEP1 EXEC PGM=my-pgm,PARM=??? How would I figure out what address to pass? If instead my-pgm is called from another program, then I would not use the JCL parm format being discussed. In that case, I would pass the address directly without the EBCDIC conversion game. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Monday, November 25, 2019 3:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: AUTHPGM in IKJTSOxx On Mon, 25 Nov 2019 23:26:32 +0000, Jeremy Nicoll wrote: >On Mon, 18 Nov 2019, at 19:35, Seymour J Metz wrote: >> A program designed to run as a jobstep expects a parameter list whose >> first word points to a halfword length field followed by a character >> string of that length. The Initiator will always flag the first word >> with an end-of-list bit. So if the program follows normal rules, you >> can't pass it an address that way. > >Why can't the character string contain eg the eight character hex >representation of a 4-byte address, which the program converts back to >binary and tries to pass control to? > In fact, that character string could be any four octets comprising a legitimate AMODE 31 address. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
