Re: Fw: SMPE: Element Contains CLIST with ALIAS
Oops, missed that bit. In SMP/E, the ALIAS name(s) [up to 16] would be specified via a SYSLIN ALIAS card during the link-editing of the object modules and coded before the NAME card. Hence, via JCLIN. An IEBCOPY COPYMOD would then copy also the names of the ALIASes, IIRC. On 10/05/2021 23:04, A T & T Management wrote: > Yes it is done by a BLDL and STOW underneith. But how SMP sets an alias > in it's way of doing things I don't recall. The ALIAS Parameter one would > think should do it. I know that a ++JCLIN with linkedit would do it. But > for something via IEBCOPY I do not. > > Scott > >- Forwarded Message - From: David Spiegel > To: "IBM-MAIN@LISTSERV.UA.EDU" > Sent: Monday, May 10, 2021, 5:52:42 PM EDTSubject: > Re: SMPE: Element Contains CLIST with ALIAS > Hi Scott, > It's done by a BLDL and a STOW. > > Regards, > David > > On 2021-05-10 17:36, A T & T Management wrote: >> >> OK >> Now on to the problem, The alias should be created at apply time. How this >> is done I don't recall and don't have access to my machine at this time. >> Scott >> On Monday, May 10, 2021, 5:01:21 PM EDT, David Spiegel >> wrote: >> >> Hi Scott, >> You're right. I would've done this, but, the customer insisted it has to >> be a PTF. >> >> Regards, >> David >> >> On 2021-05-10 16:48, A T & T Management wrote: >>> Why not do this in a usermod? >>> Scott >>> >>> On Monday, May 10, 2021, 2:25:47 PM EDT, Kurt Quackenbush >>> wrote: >>> >>> On 5/10/2021 1:15 PM, David Spiegel wrote: >>> I added a CLIST as part of a PTF. (This is not vendor software.) ++CLIST(ABCXYZ) ALIAS(XYZ) DISTLIB(ACLIST) SYSLIB(CLIST). PROC 0 WRITE HI When I ran the APPLY Job, the IEBCOPY Output showed COPY OUTDD=CLIST,INDD=SMPWRK6 S M=((A000,ABCXYZ,R)) Where does (the ALIAS) XYZ get copied to //CLIST? (It is there after the Job runs, but, there is no record of it in the Job Output.) >>> After the IEBCOPY operation SMP/E creates the alias in the data set >>> directly using the STOW data management macro. >>> >>> Kurt Quackenbush -- IBM, SMP/E Development >>> Chuck Norris never uses CHECK when he applies PTFs. >>> >>> -- >>> 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
Re: Fw: SMPE: Element Contains CLIST with ALIAS
1024-byte long member alias names in a *PDS*? Perhaps now, or in Unix, but not in 1988's MVS/XA or even in z/OS (whatever it was in 2013), AFAIK . On 10/05/2021 23:53, Paul Gilmartin wrote: > On Mon, 10 May 2021 23:32:50 +0100, CM Poncelet wrote: > >> I attach the source code for aliasing members of a PDS. >> > Where I read: > * FORMAT OF SYSIN CARD IS^M > * 'MEMBER=@@...@,ALIAS=@@...@ '^M > * WHERE '@@...@' REPRESENTS A 1 TO 8 CHAR VALID MEMBER/ALIAS NAME^M > > But in Using Data Sets: > Alias names for program objects can be up to 1024 bytes long. > >> Essentially, it just sets a flag in the COFT field of the directory's >> ALIAS member and STOWs it. > -- 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
Re: Fw: SMPE: Element Contains CLIST with ALIAS
On Mon, 10 May 2021 23:32:50 +0100, CM Poncelet wrote: >I attach the source code for aliasing members of a PDS. > Where I read: * FORMAT OF SYSIN CARD IS^M * 'MEMBER=@@...@,ALIAS=@@...@ '^M * WHERE '@@...@' REPRESENTS A 1 TO 8 CHAR VALID MEMBER/ALIAS NAME^M But in Using Data Sets: Alias names for program objects can be up to 1024 bytes long. >Essentially, it just sets a flag in the COFT field of the directory's >ALIAS member and STOWs it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Fw: SMPE: Element Contains CLIST with ALIAS
I attach the source code for aliasing members of a PDS. Essentially, it just sets a flag in the COFT field of the directory's ALIAS member and STOWs it. Cheers, Chris Poncelet (r) On 10/05/2021 23:04, A T & T Management wrote: > Yes it is done by a BLDL and STOW underneith. But how SMP sets an alias > in it's way of doing things I don't recall. The ALIAS Parameter one would > think should do it. I know that a ++JCLIN with linkedit would do it. But > for something via IEBCOPY I do not. > > Scott > >- Forwarded Message - From: David Spiegel > To: "IBM-MAIN@LISTSERV.UA.EDU" > Sent: Monday, May 10, 2021, 5:52:42 PM EDTSubject: > Re: SMPE: Element Contains CLIST with ALIAS > Hi Scott, > It's done by a BLDL and a STOW. > > Regards, > David > > On 2021-05-10 17:36, A T & T Management wrote: >> >> OK >> Now on to the problem, The alias should be created at apply time. How this >> is done I don't recall and don't have access to my machine at this time. >> Scott >> On Monday, May 10, 2021, 5:01:21 PM EDT, David Spiegel >> wrote: >> >> Hi Scott, >> You're right. I would've done this, but, the customer insisted it has to >> be a PTF. >> >> Regards, >> David >> >> On 2021-05-10 16:48, A T & T Management wrote: >>> Why not do this in a usermod? >>> Scott >>> >>> On Monday, May 10, 2021, 2:25:47 PM EDT, Kurt Quackenbush >>> wrote: >>> >>> On 5/10/2021 1:15 PM, David Spiegel wrote: >>> I added a CLIST as part of a PTF. (This is not vendor software.) ++CLIST(ABCXYZ) ALIAS(XYZ) DISTLIB(ACLIST) SYSLIB(CLIST). PROC 0 WRITE HI When I ran the APPLY Job, the IEBCOPY Output showed COPY OUTDD=CLIST,INDD=SMPWRK6 S M=((A000,ABCXYZ,R)) Where does (the ALIAS) XYZ get copied to //CLIST? (It is there after the Job runs, but, there is no record of it in the Job Output.) >>> After the IEBCOPY operation SMP/E creates the alias in the data set >>> directly using the STOW data management macro. >>> >>> Kurt Quackenbush -- IBM, SMP/E Development >>> Chuck Norris never uses CHECK when he applies PTFs. >>> >>> -- >>> 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 * * THIS PROGRAM ALIASES ENTRIES IN A PARTITIONED DATASET. * MEMBERS MAY HAVE FIXED OR VARIABLE LOGICAL RECORD LENGTH (FB OR VB). * MEMBER NAME AND ALIAS MUST BE SUPPLIED VIA SYSIN CARD. * * * FORMAT OF SYSIN CARD IS * 'MEMBER=@@...@,ALIAS=@@...@ ' * WHERE '@@...@' REPRESENTS A 1 TO 8 CHAR VALID MEMBER/ALIAS NAME * AND WHERE ANYTHING (INCLUDING COMMENTS) (EXCEPT MEMBER= // /*) MAY * PRECEDE THE 'MEMBER=' START OF CARD DATA * AND WHERE THE END OF CARD DATA (AFTER ALIAS NAME) MUST BE A BLANK. * NOTE THAT THE COMMA, AFTER THE MEMBER NAME, IS MANDATORY, * EACH SEPARATE ALIAS REQUEST MUST BE ON A SEPARATE CARD * AND THE CARDS ARE FIXED RECL=80 WITH DATA IN COLS 1 TO 72 INCLUSIVE, * DECLARED VIA DDNAME SYSIN. * * MEMBER NAMES MUST BE IN ASCENDING ALPHABETICAL ORDER. * * INVALID SYSIN CARDS ARE IGNORED. * * ALIASES SUCCESSFULLY ADDED ARE LISTED UNDER DDNAME=REPORTS OUTPUT. * * 05/06/15 CMP - ALLOW ANY MEMBER OR ALIAS NAME * CREATED: CHRIS PONCELET12/10/88 * *** * PRINT ON,GEN ALIASPDS CSECT START CONTROL SECTION * * PASSING THE 'NEXT' LABEL AS A PARAMETER TO THE 'READREC' MACRO * ***
