Re: Mark Thomen
Sad news indeed. Joining the condolences from Europe ... Klaus Stanislawiak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: "Hidden" APARs (Was: Heads Up: APAR IO11698...)
On Fri, 2 Apr 2010 08:33:40 -0700, Edward Jaffe wrote: > >I have no idea how rare they are. I have personally reported two >"hidden" APARs in the last 10 years. If that's typical for an IBM-MAIN >contributor, then there are a lot of them. I suspect it's not typical >though. I would interested to hear from others about their experiences... > To provide more input for your estimates, I have personally submitted one PMR in the last 10 years that resulted in a "hidden" APAR. Regards, Klaus Stanislawiak. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: BR problem with OBTAIN in z/OS R10
Hi Gilbert, the latest documentation should explain what you have observed (from "z/OS V1R10.0 DFSMSdfp Advanced Services"): | On return from SEARCH requests, the first 103 bytes of the first 140 byte | return area will contain: * | The 96 byte data portion of the format-1, format-4, or format-8 DSCB * | Followed by 5 bytes that contain the absolute track address (CCHHR) of | this DSCB. For VSAM object names that appear in the catalog, but not | in the VTOC or VIO data sets, these 5 bytes contain zeros. * | Followed by a 2 byte count of the total number of DSCBs associated | with the data set DSCB, even if there are insufficient return areas | into which to read them all. This count includes all DSCB types that | could describe a data set. Set to zero for DSCBs constructed from | catalog when DSCBs are not present in the VTOC. Regards, Klaus. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: original JCL via SAPI
Hi again, not quite so, SAPI is not involved in this process at all. Please see Appendix B of the "JES2 Initialization and Tuning Guide" for a description of the SDSB Interface: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS2A350/APPENDIX1.2.4?SHELF=HAS2BK61&DT=20060630010801 Regards and good luck, Klaus Stanislawiak. On Wed, 11 Apr 2007 15:01:00 +0200, Miklos Szigetvari <[EMAIL PROTECTED]> wrote: >Hi > >If I understand correctly , I got the browse token from SAPI , and I >can make a dynalloc >for the dsn : user.jobname.jobid.JESJCLIN > -- 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
Re: original JCL via SAPI
Hi Miklos, the SAPI (SYSOUT Application Interface) only provides support to read SYSOUT data sets. What you are looking for (DDNAME JESJCLIN) is not a SYSOUT data set, so you won't be able to read it through SAPI. If you are on a JES2 system, try the Spool Data Set Browse (SDSB) Interface, that will allow you to read also JESJCLIN. Regards, Klaus Stanislawiak. -- 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
