The removal of the '.' is inappropriate. If the symbol is not recognized, it should be left alone (and the '.' not removed). This only seems to occur when you specify CNVTSYS or EXECSYS. It is related to how the instream substitution service interacts with the system symbol service.
If you can open a PMR against JES2, the JES2 team will investigate changing this behavior. As for the '&&' being converted to '&' that was a long internal debate. The concern was that the instream data is being fed to a service that may also be doing substitution. We were thinking of things like the high level assembler. The intent may be that the double && was intended for that service. The instream process removing that could cause problems later down the line. So it was decided that the instream substitution service would NOT un-double the &. Also note that there is another oversight that was pointed out. The &SYSUID symbol is not being substituted in the instream data. That should have been done. OA45995 was created to correct that oversight. I mention this because you happened to use &USER in your JCL. Until the APAR is available, you could set USER=&SYSUID or even SYSUID=&SYSUID Tom Wasik JES2 Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
