On Mon, 31 Oct 2011 15:12:04 -0400 Joe Aulph <[email protected]> wrote:
:>My intent is to construct a proper SYSIN statement and Call IDCAMS using my :>SYSIN, this I have done. :>After IDCAMS is finished I should have some SYSPRINT which I would massage :>after the call to IDCAMS, ie... not using the IDCAMS "user I/O routine" :>fcaility. :>At this point I've modified my code to immediately exit upon return from :>IDCAMS, no massaging of SYSPRINT at all. :>As such the SYSPRINT output remains as I described earlier. If that is what you are doing, i.e., writing the input to a file and then reading the output from a file, it would make much sense to do this as two programs, P1 writes the input, IDCAMS runs and P2 reads the output. Why invoke IDCAMS from a program? :>According to the AMS for ICF catalogs, the LOAD & CALL scenario is: :>LOAD EP=IDCAMS :>then load register 15 with the address returned from LOAD: :>LR 15,0 :>Followed by the call: :>CALL (15),optionaddr,VL :>Because I have specified no IDCAMS processing options, PARM= on the EXEC :>PGM= JCL card. :>The "optionaddr" points to a half word of binary zeros. Looks fine. :>Because the 0C4 was happening in IDCAMS I thought I couldn't change IDCAMS :>code. :>So I opted for the LOAD & CALL scenario instead of the LINK, it might work, :>which I initially thought it did, I got around the S0C4. I would suggest that your plist is wrong. Is "optionaddr" an address constant (wrong) or DC H'0' (correct)? :>I have found this in my testing today. :>Initially I used an example of an IDCAMS call from a CBT tape program it :>was simply: :> LA R1,argumentlist (points to binary zeros) . :> LINK EP=IDCAMS :>Which was the format that initially worked, until the S0C4. I would suggest that "argumentlist" is defined incorrectly. :>After a bit of RTFM in the AMS guide, I find this format should be: :> LA R1,VGCARGL Useless, as the following PARAM= sets R1. :> LINK EP=IDCAMS,PARAM=options,VL=1 Options pointing to a half word of :>binary zeros. :>Now whether I use this method or the LOAD & CALL method I get my SYSPRINT :>messed up. :>As much as I am trying to avoid the "user I/O routine" is this the route I :>must take? I repeat my suggestion that you do this a two programs UNLESS you are going to use the I/O routines. :>On Sat, Oct 29, 2011 at 7:29 PM, Shmuel Metz (Seymour J.) < :>[email protected]> wrote: :> :>> In :>> <ca+vt6kp9zp4meyxjrqwkm9hilvdutrcqzonmnx2dwegqrdu...@mail.gmail.com>, :>> on 10/28/2011 :>> at 03:39 PM, Joe Aulph <[email protected]> said: :>> :>> > LA R1,ARGLIST :>> :>> What is in ARGLIST and the things it points at? :>> :>> >I was able to construct SYSIN and get the appropriate SYSPRINT. But :>> >as the program grew I ran into S0C4 rsn=0011 problems. :>> :>> Where? Did you try to resolve them? :>> :>> -- :>> Shmuel (Seymour J.) Metz, SysProg and JOAT :>> ISO position; see <http://patriot.net/~shmuel/resume/brief.html> :>> We don't care. We don't have to care, we're Congress. :>> (S877: The Shut up and Eat Your spam act of 2003) :>> :>> ---------------------------------------------------------------------- :>> 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 :>> -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- 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
