On 6/2/2021 10:43 AM, Binyamin Dissen wrote:
Ops. My mistake - they are aliases. I forgot how ISPF shows them.
As a side point, why does the RELFILE need the alias? Can't the apply process
assign them?
Why? That's just the way APPLY works. I don't know what the original
design point was
On Wed, 2 Jun 2021 17:43:10 +0300, Binyamin Dissen wrote:
>...
>As a side point, why does the RELFILE need the alias? Can't the apply process
>assign them?
>
I believe Kurt is saying that IEBCOPY doesn't assign aliases.
OTOH, I was dismayed long ago when I tried such as:
//SYSLIN DD *
Ops. My mistake - they are aliases. I forgot how ISPF shows them.
As a side point, why does the RELFILE need the alias? Can't the apply process
assign them?
On Wed, 2 Jun 2021 10:04:12 -0400 Kurt Quackenbush wrote:
:>On 6/2/2021 8:57 AM, Binyamin Dissen wrote:
:>> I have inherited a
On 6/2/2021 8:57 AM, Binyamin Dissen wrote:
I have inherited a product with MCS with ALIAS/MALIAS.
It appears that the RECEIVE process requires the alias to be in the RELFILE,
and that the APPLY process creates true members instead of aliases.
Am I missing something obvious in the packaging?
I have inherited a product with MCS with ALIAS/MALIAS.
It appears that the RECEIVE process requires the alias to be in the RELFILE,
and that the APPLY process creates true members instead of aliases.
Am I missing something obvious in the packaging?
--
Binyamin Dissen
