>So, yes, I think the documentation is not 100% clear having worked with a
>different mechanism.
In a way, you're sort of saying that you didn't read the documentation
carefully because you had used a different technique in the past and
perhaps were making some assumptions about the new approach.
UA.EDU
> Subject: Re: z/OS V2.1 and SETLOAD
>
> SYMUPDAT was never supported. The IEASYMUP program had been
> provided about
> 10 years ago.
> z/OS 2.1 provides IEASYMU2 instead. If you invoke the z/OS 2.1 IEASYMUP it
> will issue a message telling you so.
>
> I think
Good to know. Thanks.
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Bruce Hewson
> Sent: Sunday, June 07, 2015 9:34 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: z/OS V2.1 and SETLOAD
>
>
Lizette,
works as advertised.
update your parmlib IEASYMxx members to make your symbol change permanent.
run the SETLOAD command.
similar to creating a new dynamic LINKLIST, your system gets a new SYMBOL table
based on your updated IEASYMxx members.
Regards
Bruce Hewson
-
SYMUPDAT was never supported. The IEASYMUP program had been provided about
10 years ago.
z/OS 2.1 provides IEASYMU2 instead. If you invoke the z/OS 2.1 IEASYMUP it
will issue a message telling you so.
I think/hope it is clearly defined that SETLOAD xx,IEASYM identifies the
*entire* symbol defin
I am looking to use the SYBMOLICRELATE in our environment. In the past I used
the SYMUPDATE function to update the system symbols on a given system.
I see now that is replaced with SETLOAD.
This seems to work differently than the older process - which IBM states in its
documentation should n
