I was able to DL it and extract the XMI and view it with XMIT Manager V3 (also available on the CBTTAPPE website) without any problem.
Did you transmit the XMI file to your z/OS system in binary and then RECEIVE it to a PDS? Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of esst...@juno.com Sent: Thursday, February 20, 2020 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to test SUBSYS= 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 <Snipped> -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
