Re: IPCS ADPLSEQS
In article you wrote: > Since 2008, forwarding to Bob has been possible only via a literal > "ether net" connection. Unfortunately, the IBM mail network does not > have such a connection. We wish it did. We as well find understanding > how to use some of the IPCS macros to be challenging. > > It is. It has the feel of an internal product that was handed off to > > someone to externalize and it's mostly there, but there are definitely > > corners that could use some re-vamping. 64-bit was a pain as it required > > non-intuitive calls to get what was needed. Bob Wright helped me out > > in this forum and if you open an SR, that's who I'd ask it get forwarded > > to. > Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. > Poughkeepsie NY Jim, Thanks. That is sad. I don't think I knew that, but these days it seems like we're losing more than I can keep track of. He was always helpful when I had some question about IPCS and the voodoo that surrounded it. -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS ADPLSEQS
Since 2008, forwarding to Bob has been possible only via a literal "ether net" connection. Unfortunately, the IBM mail network does not have such a connection. We wish it did. We as well find understanding how to use some of the IPCS macros to be challenging. > It is. It has the feel of an internal product that was handed off to > someone to externalize and it's mostly there, but there are definitely > corners that could use some re-vamping. 64-bit was a pain as it required > non-intuitive calls to get what was needed. Bob Wright helped me out > in this forum and if you open an SR, that's who I'd ask it get forwarded > to. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS ADPLSEQS
Thanks for your help Don. I finally did get the symbol defined correctly … symbol 00. ASID(X'0046') DSPNAME(symbol) LENGTH(X'1000') AREA(symbol) DROP I was priming the ESSY with a DSECT=NO version and it had a -1 as the asid word. I was only updating the 2nd half of the word with a 2 byte ASID leaving in the top half. (dumb mistake) Thanks again, Dan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS ADPLSEQS
In article <7271721887429173.wa.zos.jes2gmail@listserv.ua.edu> you wrote: > The ESSY is rather odd ??? > If I use ABITS=64 it this request gets a RC 12. > When I list the symbol I get >symbol 00. ASID(X'0026') LENGTH(X'1000') AREA(symbol) DROP > If I issue "L symbol DSPNAME(symbol)" and list the symbols again a mysterious > "X" symbol is defined ??? > X 00. ASID(X'0026') DSPNAME(symbol) LENGTH(X'1000') > AREA(symbol) DROP > This stuff is just bizarre and not well documented. It is. It has the feel of an internal product that was handed off to someone to externalize and it's mostly there, but there are definitely corners that could use some re-vamping. 64-bit was a pain as it required non-intuitive calls to get what was needed. Bob Wright helped me out in this forum and if you open an SR, that's who I'd ask it get forwarded to. In this particular case though, did you set the BLSRXSSP field to say that you wanted ABITS(64)? EQU BIT2 BLSRESSY structures should be returned in ABITS(64) format -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS ADPLSEQS
The ESSY is rather odd … If I use ABITS=64 it this request gets a RC 12. When I list the symbol I get symbol 00. ASID(X'0026') LENGTH(X'1000') AREA(symbol) DROP If I issue "L symbol DSPNAME(symbol)" and list the symbols again a mysterious "X" symbol is defined … X 00. ASID(X'0026') DSPNAME(symbol) LENGTH(X'1000') AREA(symbol) DROP This stuff is just bizarre and not well documented. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS ADPLSEQS
In article <6648609332066356.wa.zos.jes2gmail@listserv.ua.edu> you wrote: > I'm using ADPLSEQS to define a symbol in an IPCS verb exit. > I'm trying to define a symbol to a dataspace. > When I issue "L symbol" I get > LIST 00. ASID(X'0046') LENGTH(X'01') AREA(Symbol) > ASID(X'0046') ADDRESS(00.) KEY(08) PREFIXED > I can issue "L symbol DSPNAME(symbol)" but I wonder if I can define the > symbol so that is the default. > Does someone know what field in the ESSY I need to set, and to what? > Thanks I've only done regular ASID which I set in "Integer 2". For dataspace, it looks like you need the "Integer 1" set to the ASID and "Integer 2" set to the DSPNAME. The odd part is that the macros to expand "Integer 2" to a CL8 "Second qualifier" requires coding it a different way than BLSRESSY codes it. It looks as though you'd have to modify BLSSRESSY and code BLSRDATS like: BLSRDATS ZZZASTDS,DSECT=NO -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IPCS ADPLSEQS
I'm using ADPLSEQS to define a symbol in an IPCS verb exit. I'm trying to define a symbol to a dataspace. When I issue "L symbol" I get LIST 00. ASID(X'0046') LENGTH(X'01') AREA(Symbol) ASID(X'0046') ADDRESS(00.) KEY(08) PREFIXED I can issue "L symbol DSPNAME(symbol)" but I wonder if I can define the symbol so that is the default. Does someone know what field in the ESSY I need to set, and to what? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
