On Mon, 28 Apr 2014 09:24:23 -0500, Scott Barry <[email protected]> wrote:
>Appears that CA JMR (output archival) has an architecture challenge with a >shared JES environment and sites slowing migrating LPARs to z/OS V2R1 - that >is parsing the SYSTEM from the JES Log for a batch-job archival is basically >either environment, not both. With the JES log text-format change (i.e., long >JES class names) and the location of the SYSTEM identification, archived >output has a corrupted SYSTEM column and as was explained to a client we >support, "that's all we can provide." Also, a search of the CA SUPPORT ONLINE >system does not reveal any heads-up for impacted clients. > >So, JMR sites with co-existing z/OS environments (V1R13 & V2R1 for example) >will likely see this information corruption for archived batch jobs during the >phased z/OS V2R1 migration period. > >Scott Barry >SBBWorks, Inc. Is the JES2 text format change a result of having long JES2 Job Classes enabled or just from running JES2 for z/OS 2.1 without it being enabled? -- Dale R. Smith ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
