Well, he can always look to the JSCB to determine the caller, right?

Joe

On Tue, Sep 22, 2020 at 4:19 PM Seymour J Metz <sme...@gmu.edu> wrote:

> The parm list won't tell him who's calling him. I wouldn't be surprised if
> the special cases cover his requirements, but until he spells them out, ...
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> ________________________________________
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> of Joe Monk <joemon...@gmail.com>
> Sent: Tuesday, September 22, 2020 4:40 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Determining program name/number of paramaters from called
> COBOL program
>
> yeah ... but R1 should point to the parm list ... and he would calling this
> assembler stub 1st thing so ...
>
> Joe
>
> On Tue, Sep 22, 2020 at 3:23 PM Seymour J Metz <sme...@gmu.edu> wrote:
>
> > If the data are not in the called programs then chasing the save areas
> > won't find the data. The basic form of a SAVE is just an STM (24 bit) or
> > similar instructions.
> >
> >
> > --
> > Shmuel (Seymour J.) Metz
> > http://mason.gmu.edu/~smetz3
> >
> >
> > ________________________________________
> > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> > of Joe Monk <joemon...@gmail.com>
> > Sent: Tuesday, September 22, 2020 4:16 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Determining program name/number of paramaters from called
> > COBOL program
> >
> > he could work his way back thru the saveareas, no?
> >
> > Joe
> >
> > On Tue, Sep 22, 2020 at 3:05 PM Seymour J Metz <sme...@gmu.edu> wrote:
> >
> > > Standard linkage conventions don't require branching around an
> eyecatcher
> > > or that they eyecatcher be in a standardized format or even include the
> > > module name. So the question is what special cases does the OP need to
> > > handle.
> > >
> > >
> > > --
> > > Shmuel (Seymour J.) Metz
> > > http://mason.gmu.edu/~smetz3
> > >
> > >
> > > ________________________________________
> > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on
> behalf
> > > of Joe Monk <joemon...@gmail.com>
> > > Sent: Tuesday, September 22, 2020 4:00 PM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: Determining program name/number of paramaters from called
> > > COBOL program
> > >
> > > If it's using standard OS linkage, he could use an assembler routine to
> > do
> > > a traceback and get some of the items.
> > >
> > > The problem will come in if passed by value instead of by reference...
> > >
> > > Joe
> > >
> > > On Tue, Sep 22, 2020 at 2:58 PM Seymour J Metz <sme...@gmu.edu> wrote:
> > >
> > > > I doubt that it's possible in general, certain special cases are
> > > possible.
> > > >
> > > >
> > > > --
> > > > Shmuel (Seymour J.) Metz
> > > > http://mason.gmu.edu/~smetz3
> > > >
> > > >
> > > > ________________________________________
> > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on
> > behalf
> > > > of Chris Cantrell <chris.cantr...@palmettogba.com>
> > > > Sent: Tuesday, September 22, 2020 3:24 PM
> > > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > > Subject: Determining program name/number of paramaters from called
> > COBOL
> > > > program
> > > >
> > > > Hello,
> > > >
> > > > I am hoping someone out there can help me with this 'opportunity'.
> > > >
> > > > In a Z/OS enterprise COBOL environment, I want to be able to retrieve
> > the
> > > > calling program name and the number of parms passed to the called
> > program
> > > > from the called program. In other words, program A is executed in my
> > > batch
> > > > job and it calls program B passing 5 parms in the using statement. I
> > want
> > > > program B to be able to retrieve the program name for program A as
> well
> > > as
> > > > the number of parms that were passed to it.
> > > >
> > > > I think if I could get to the program stack I could probably figure
> it
> > > out
> > > > from there.
> > > >
> > > > Any assistance that any of you could provide would be greatly
> > > appreciated.
> > > >
> > > > Thanks!
> > > >
> > > >
> ----------------------------------------------------------------------
> > > > 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
> > > >
> > >
> > > ----------------------------------------------------------------------
> > > 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
> > >
> >
> > ----------------------------------------------------------------------
> > 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
> >
>
> ----------------------------------------------------------------------
> 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
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to