Charles Mills wrote: > My "problem" is not with JCL and while the answer may be obvious from the documentation, not one person here has been able to answer it.
What about Mark Zelden? He wrote this: <quote> >FWIW in the case in question I am not using SVC 99 directly but rather using C fopen(); >Yeah, the fact that you can't code &SYSNAME in JCL seems pretty lame. I code it in lots of JCL. </quote> My suggestion: could Mark help you out there? For my part, when I use something like &SYSNAME, I would use my automation package to check up the current system and place the correct symbolic varialbe in the JCL before submit it. Something like this to be included for my job in automation package: //* %%IF %%SMFNCODE EQ ....1 //* %%SET %%SYSNAME = ....1 //* %%ENDIF //* %%IF %%SMFNCODE EQ ....2 //* %%SET %%SYSNAME = ....2 //* %%ENDIF And my job to be run is something like this: //COPY EXEC PGM=IFASMFDP //INDD1 DD DISP=SHR,DSN=<hlq>.%%SYSNAME.INDUMP.... //OUTDD1 DD DISP=(OLD,KEEP),DSN=<hlq>.%%SYSNAME.OUTDUMP... Alternative: I use REXX (or Assembler) and its functions to get SYSNAME and generate a nice JCL to be run on a correct LPAR in a correct SYSPLEX. You can also use Dynamic Allocation (BPXWDYN) functions to be used in REXX or COBOL. Insert your SYSNAME programmatically and fire of that JCL! This has been discussed in IBM-MAIN. Basically you need to 'rewrite' a JCL before execution to overcome the limits of JCL. HTH! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
