Hello List, I'm having an issue with calling IDCAMS from within my program and if anyone could shed some light on this I'd appreciate it.
The scenario is like this my program manipulates the SYSIN input to IDCAMS and would, post call, manipulate the SYSPRINT output. The execution JCL allocates both SYSIN & SYSPRINT. Initially I was having good success using the call format: No options specified. LA R1,ARGLIST LINK IDCAMS I was able to construct SYSIN and get the appropriate SYSPRINT. But as the program grew I ran into S0C4 rsn=0011 problems. After wrestling a bit with that I switched to the LOAD & CALL format: LOAD EP=IDCAMS LR R15,R0 CALL (15),OPTIONS,VL once again no options specified. This worked just fine, getting around the S0C4 problem, except that now the SYSPRINT output is a total mess. The output is 146 lines of VBA/125 output. Interlaced through out are the IDCAMS headders, page numbers, SYSIN commands stuff you'd expect to see. But no actual output from the SYSIN commands, everything else is hundreds of x'4B', an ocassional other odd character but mostly periods, x'4B' . The code is not-reentrant, I've done no GETMAIN's, has anyone ever ran into this sort of thing? Any help would be appreciated. TIA -- Joe Aulph, Florida Dept. of Children & Families Senior Systems Programmer: 850-487-8945 ---------------------------------------------------------------------- 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
