Re: SMP/E question of the day

2023-12-16 Thread Jon Perryman
On Thu, 14 Dec 2023 11:54:28 -0500, Phil Smith III wrote: >++VER(Z038) FMID(VABC840) . >++ZAP(ABCDITSK) . >NAME ABCDITSK ABCPROC#C C_CODE >--NAME ABCDITSK ABCPROC#C C_CODE. >GIM23101E ** THERE IS A SYNTAX ERROR IN A ZAP CONTROL STATEMENT FOR MODULE > ABCDITSK IN SYSMOD

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Matt Hogstrom
Provides more detail on the link Kirk provided. https://developer.ibm.com/tutorials/build-java-records-from-cobol-with-ibm-record-generator/ Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook LinkedIn

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Ed Jaffe
That's silly. Anyone can do that. You don't need a go-between. It's a DIY affair! The "captain's" name is Tom Ross, works for IBM, hangs out on various email lists, comes to our PSI party at every SHARE, and his email address is tmr...@us.ibm.com... On 12/16/2023 10:29 AM, Charles Mills

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Charles Mills
Sure. ¿Porque no? Thanks, Charles On Sat, 16 Dec 2023 17:54:36 +, M. Ray Mullins wrote: >Charles, > >Would you like me to ping Captain COBOL? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Charles Mills
You know what I am actually looking at doing? You may laugh but it has worked for me in the past. I am thinking of pulling the IBM HTML documentation into MS-Word and massaging it there into C declarations. I did this for a *LOT* of RACF record layouts for the CorreLog product, so I know

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Kirk Wolf
> > I am not much of a Java guy but IIRC it would be a fairly short editing leap > from Java classes to C structs. Depends on what you mean by "fairly short" :-) It would be good if you could find the DSECTS for Cobol ADATA, but if you look at the ADATA produced by Cobol, you'll likely find

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread M. Ray Mullins
Charles, Would you like me to ping Captain COBOL? Cheers, Ray Sent from Outlook for iOS on my personal iPhone From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Saturday, December 16, 2023 9:47:54 AM To:

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Charles Mills
@Kirk, interesting. I was not aware of that tool. I have used the DSECT to C header conversion tool that is part of the XLC product, but I was not aware of this tool. I am not much of a Java guy but IIRC it would be a fairly short editing leap from Java classes to C structs. Unfortunately, as

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Charles Mills
ASM ≠ COBOL The ADATA records for the two products have a lot in common but not as much as one might hope. Charles On Sat, 16 Dec 2023 08:03:46 -0600, Ralph Spadafora wrote: >HLA.SASMMAC1(ASMADATA) -- For IBM-MAIN

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Kirk Wolf
Hi Charles, This may not be what you are looking for, but as I recall it's pretty cool: https://www.ibm.com/docs/en/record-generator/3.0?topic=what-is-record-generator-java Along with generating Java mapping classes, you can also spit out XML descriptions. I haven't looked at this in a long

Re: CSVQUERY in ARR routine return code 8 didn't have PLISTVER=MAX On CSVQUERY

2023-12-16 Thread Ed Jaffe
On 12/16/2023 5:19 AM, Peter Relson wrote: Lack of PLISTVER=MAX on the list form can result in the area for the parameter list being too small, with the result that the execute form expansion overlays something following it which perhaps something relies upon. 100 percent! Always code

Re: Looking for COBOL SYSADATA record layouts

2023-12-16 Thread Ralph Spadafora
HLA.SASMMAC1(ASMADATA) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: CSVQUERY in ARR routine return code 8 didn't have PLISTVER=MAX On CSVQUERY

2023-12-16 Thread Peter Relson
Once again, the lack of providing sufficient information about what was actually done has wasted the time of the good folks on this listserv. I suppose it might be said that we enable this bad behavior by responding. I intend to stop responding for this sort of case from repeat "offenders".