Has anyone been able to actually view file 364 ?I was able to down load and extract the file, but I cant read it ?
---------- Original Message ---------- From: Steve Smith <sasd...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to test SUBSYS= Date: Wed, 19 Feb 2020 23:31:08 -0500 There's also the "Control Card Subsystem (CCSS)" on I believe file 364 of the CBT. It's about as simple a DD SUBSYS subsystem as you can get. It's function has been superseded by later developments, but like the other examples, gives you the infrastructure to start with. That said, I don't think it will help with the original problem. z/OS does not do an OBTAIN for a DD SUBSYS file; all it does is pack up whatever DD operands are present, and pass them on via SSI function calls to the registered subsystem. If a DSN= is present, it's just another string as far as z/OS is concerned. Anything besides SUBSYS= must pass syntax checking, but nothing else. The problem seems to be in the customer's subsystem, whatever that might be. I'd concoct a test case that did not use your product, but used JCL, ALLOC, or bpxwdyn to allocate the file (using SUBSYS=), and see how the FTP goes. I think it should show your product isn't part of the problem. My guess is the customer's subsystem is using the SSI functionality to insert itself into a more-or-less regular I/O path, and doesn't know how to deal with aliased datasets. I don't know what's issuing the OBTAIN, but it sure won't work with an alias. sas sas On Wed, Feb 19, 2020 at 10:53 PM Wayne Bickerdike <wayn...@gmail.com> wrote: > Can be done in a few 100 lines of code. > > IEFSSVT REQUEST=CREATE > IEFSSI REQUEST=OPTION > IEFSSI REQUEST=PUT > IEFSSI REQUEST=ACTIVATE > > Probably a useful test stub too if you have a few function codes added. > > > On Wed, Feb 19, 2020 at 1:40 PM Tony Harminc <t...@harminc.net> wrote: > > > On Tue, 18 Feb 2020 at 20:03, Charles Mills <charl...@mcn.org> wrote: > > > > > 1. Is there any convenient "hack" for testing whether my SVC 99 is > > operating > > > correctly and so forth? Anyone have any bright ideas how to test SVC 99 > > > SUBSYS allocation when one does not have subsystem XXXX? Suppose for > > example > > > that I wrote a test program that would try an OBTAIN against my > > allocation. > > > Is there any way to come up with a subsystem name that will at least > > succeed > > > through allocation? Is there a CBT program that implements some sort of > > > subsystem (and is not a big deal of its own)? > > > > You can write a minimal subsystem of your own. The well-known place to > > start is GPSAM on the CBT site. http://cbttape.org/cbtdowns.htm > > > > GPSAM (file 290 and another version in file 648) is indeed remarkable > > in that it's 45 years old, and the code and doc are still 99% valid on > > current z/OS. To say nothing of the high quality of Howard Gilbert's > > short but to the point doc. It's entirely possible that GPSAM may > > already provide the infrastructure for what you want to do, though > > much of its initialization would be done differently if written today. > > > > (Actually I self plagiarized the above from a posting I made here > > several years ago.) > > > > If nothing else, read Howard Gilbert's doc on how this kind of > > subsystem works. It certainly doesn't discuss OBTAIN, and I have no > > idea if the OBTAIN function includes a subsystem call to gather info, > > or if it's a conceptually wrong thing to be doing. I suspect the > > latter, but if OBTAIN works with your vendor subsystem... > > > > Tony H. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > -- > Wayne V. Bickerdike > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
