Missing Cobol Library in Xpediter

[MFFLCrime]

Hi All,

I keep getting a Soc4 when I try to open a flat file as input in my Xpediter session. The file exists, and I'm able to access it with no issues when I run the same program in batch. I know I'm missing one of those COBOL loadlibs or a specific subroutine library. I have tried several but I have not been able to pinpoint which one it is. Do anyone have any ideas?

Thank you in advance,

[Robert Sample]

Why do you think a system library is missing? Why could it not be that you just did not allocate the file in TSO before starting Xpediter?

[NicC]

Why do you think that anyone not in your organisation could possibly know anything about the set-up of Xpediter at your shop?

[MFFLCrime]

You got a point. I have and continue to ask around, however, the runtime libraries that I am referring to are standard for Xpediter setup, I've used Xpediter in other shops, I just don't remember the specific one I need and thought the forum would be able to help. Thanks anyway for your response.

[Robert Sample]

Data set names are not standard -- every site has their own standard (even for system libraries -- one site migth use IGY.SIGYCOMP for the COBOL compiler whereas another uses IGY.V4R1M0.SIGYCOMP and another uses IGY.V410.SIGYCOMP). Hence, even if someone gave you the name of the library used at their site, there is little chance, if any, that the data set even exists at your site, much less resolves your problem. You asked the type of question that can only be answered by someone working AT YOUR SITE -- talk to your team leader, co-workers, or site support group for assistance.

[Quasar]

Hi,

Why don't you form a test Job-stream in your PDS, that contains just one-step - the program to be executed, along with all the necessary DD Cards. Then, supply it to Xpediter. Give me the failure screen-shot. Is it failing at the COBOL OPEN Statement?

Thanks,
Quasar

[Ed Goodman]

We used to get this if our COMPILE jcl had a different version of the libraries than the RUN TIME jcl (or tso set up).

Check for that. You may just have an older compile set up and be shooting yourself in the foot.