Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-03 Thread Kurt Quackenbush
How would this work for ++MOD elements in RELFILE format. Should I supply the IDENTIFY as input to Binder when I link the ++MOD element so Binder will imbed it in the IDR? Same for ACCEPT into DLIB? Yes. Kurt Quackenbush -- IBM, SMP/E Development

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-02 Thread Kurt Quackenbush
OTOH, we're already digesting SYSLIN to generate CSECT parameters for SMP/E ++MOD MCS. It would be quite natural to append Binder IDENTIFY commands at that point. But I believe SMP/E doesn't recognize Binder commands appearing in SYSLIN. Huh? I assume you're talking about the SYSLIN for a

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-02 Thread Paul Gilmartin
On Tue, 2 Dec 2014 09:13:56 -0500, Kurt Quackenbush wrote: OTOH, we're already digesting SYSLIN to generate CSECT parameters for SMP/E ++MOD MCS. It would be quite natural to append Binder IDENTIFY commands at that point. But I believe SMP/E doesn't recognize Binder commands appearing in

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread Shmuel Metz (Seymour J.)
In 8902901628988927.wa.paulgboulderaim@listserv.ua.edu, on 11/30/2014 at 11:51 AM, Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu said: Can this information be supplied from HLASM Yes. (but this would be harder for us to automate.) Why can't you pass the necessary

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread Shmuel Metz (Seymour J.)
In CAE1XxDHQB8Mn99LQZcydqGc5QHGPR5HJC-bNPmv0H==um7c...@mail.gmail.com, on 11/30/2014 at 01:19 PM, John Gilmore jwgli...@gmail.com said: AINSERT is then used to 'save' them, and AREAD is used to put them into the output. That's not even wrong! He needs a PUNCH or REPRO to get them into the

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread John Gilmore
Shmuel was, of course, entirely correct in saying that a PUNCH or REPRO statement is necessary to get them into the output; but this surpassingly obvious observation is not very interesting. The AINSERTs and AREADs are needed to sequence IDENTIFY binder control statements properly: They must

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread Paul Gilmartin
On Sun, 30 Nov 2014 19:32:45 -0500, Shmuel Metz (Seymour J.) wrote: at 11:51 AM, Paul Gilmartin said: Can this information be supplied from HLASM Yes. Can it be more straightforward than JWG's suggestion? (but this would be harder for us to automate.) Why can't you pass the necessary

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread Shmuel Metz (Seymour J.)
In CAE1XxDG4NRGnr2hk-=cdsgdxqs1nuv7ucbru4ntyy_ebkmx...@mail.gmail.com, on 12/01/2014 at 11:18 AM, John Gilmore jwgli...@gmail.com said: surpassingly obvious It should have been obvious *before* you incorrrecvtly described the roles in AINSERT and AREAD. The AINSERTs and AREADs are needed to

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-12-01 Thread Robert A. Rosenberg
At 11:18 -0500 on 12/01/2014, John Gilmore wrote about Re: SMP/E and IDR (was: Binder SETSSI ...?): Shmuel was, of course, entirely correct in saying that a PUNCH or REPRO statement is necessary to get them into the output; but this surpassingly obvious observation is not very interesting

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Paul Gilmartin
On Sun, 30 Nov 2014 11:51:39 -0600, Paul Gilmartin wrote: On Sun, 30 Nov 2014 09:03:18 -0500, John Gilmore wrote: The availability of control-section specific IDRs and the IDENTIFY binder control statement have, however, made SETSSI obsolescent. Does SMP/E support the Binder IDENTIFY statement?

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Paul Gilmartin
On Sun, 30 Nov 2014 13:19:31 -0500, John Gilmore wrote: One formats the text of an IDENTIFY control statement as a sequence of character set symbols that are card images. AINSERT is then used to 'save' them, and AREAD is used to put them into the output. Feels a lot like PUNCH. This really

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Ed Gould
It sure does. Ed On Nov 30, 2014, at 11:51 AM, Paul Gilmartin wrote: On Sun, 30 Nov 2014 09:03:18 -0500, John Gilmore wrote: The availability of control-section specific IDRs and the IDENTIFY binder control statement have, however, made SETSSI obsolescent. Does SMP/E support the Binder

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Paul Gilmartin
On Sun, 30 Nov 2014 16:05:04 -0600, Ed Gould wrote: It sure does. Cite? Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Ed Gould
A large percent (all?) of IBM SMP maintenance comes along with a setssi card. Not exactly what I was looking for but I think it will do: http://publibz.boulder.ibm.com/epubs/pdf/gim3rf01.pdf v The only IMASPZAP control statements allowed in a SYSMOD are: Control statements ABSDUMP DUMP NAME

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Paul Gilmartin
On Sun, 30 Nov 2014 22:53:22 -0600, Ed Gould wrote: A large percent (all?) of IBM SMP maintenance comes along with a setssi card. Not exactly what I was looking for but I think it will do: http://publibz.boulder.ibm.com/epubs/pdf/gim3rf01.pdf v The only IMASPZAP control statements allowed in a

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Ed Gould
Paul: I am not going to do your homework. IDENTIFY is a valid binder control statement so it must work in SMPE. Ed On Nov 30, 2014, at 11:10 PM, Paul Gilmartin wrote: On Sun, 30 Nov 2014 22:53:22 -0600, Ed Gould wrote: A large percent (all?) of IBM SMP maintenance comes along with a

Re: SMP/E and IDR (was: Binder SETSSI ...?)

2014-11-30 Thread Mike Schwab
http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/lmodacc.htm?lang=en On Sun, Nov 30, 2014 at 11:42 PM, Ed Gould edgould1...@comcast.net wrote: Paul: I am not going to do your homework. IDENTIFY is a valid binder control statement so it must work in SMPE.