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
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
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
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
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
