Are symbols being updated outside an IPL with SETLOAD IEASYM? Poking around a bit, I found the following in the JES3 Init and Tuning Guide:
JES3 updates the system symbols table each time the system connects to the JES3 global, including each instance of the JES3 global connecting to itself. You can therefore update system symbols by running the JES3 *S main,CONNECT command. If you update system symbols using the SETLOAD IEASYM command, you can use these updated symbols for future conversions by running the *S main,CONNECT command, where main is the name of the updated system. This system symbols update will not affect jobs that have already undergone conversion. FWIW, we automate "IEF900I SYSTEM SYMBOLS WERE UPDATED FROM ..." to issue *S &SYSNAME,CONNECT On Thu, May 11, 2023 at 9:15 PM Mark Charles <markchar...@eworldes.com> wrote: > Client has 3 systems in JES3 Sysplex. System A is z/OS 2.3 JES3 Global. > System B is z/OS 2.5 JES3 Local with no CIs defined. Other system not > important. > > When starting STC with system symbols on System B, the symbols are > "replaced" by information from System A. Is this normal? Is there a way > to get the symbols "replaced" with information from the Local System B? > > ---------------------------------------------------------------------- > 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
