Re: Has anyone

If I can't have BookMaster or BookManager Build, LaTeX is a good choice, especially with expl3. There is a massive library of packages at Comprehensive TeX Archive Network (CTAN) . -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 _

Pass PARM by reference to COBOL

PARM is uniformly passed to a program by reference: R1 -> x'8000' + -> halfword length || parameter string If a COBOL program is called by a program other than Initiator, can it modify that parameter string as an Assembler program might to return a value to the caller? (If a program is ma

Re: Pass PARM by reference to COBOL

What the called program can do depends on the caller. The PARM might be in R/O storage. The Initiator does not pass a 64-bit PARM. From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Wed

Re: Has anyone

Fair point, but my clients hire me as a mainframe geek. I do know other things, but most of my income is from mainframe security, with occasional forays into coding for MS Office. So from my point of view, "the real thing" is MS Office. My oldest daughter is a Linux fan; I've never used it.

Re: Has anyone

The Golden Rule: he who has the gold makes the rule. But I don't use it when it's not mandatory. Would that be vi, AKA the editor from Hell? It has the advantage that if you have to use a random *ix system, there will almost certainly be some version available. If not vi, was it emacs? -- Shm

Re: Has anyone

It really depends on your requirements, but for many years we have used a Docbook based approach for our technical documentation, which allows us to easily generate HTML, PDF, and man page versions of our documentation. It's a bit of work getting the XSL styles tweaked to your liking, but aft

Re: Has anyone

Too many years ago; I don't remember. And it isn't as if "unintuitive" is a fatal error in editors or any other application; TECO (anyone ever use that?) is a powerful editor - it was on the PDP platform as I recall - with early automation features that I used extensively, and it was full of odd u

Re: Has anyone

On Wed, 16 Aug 2023 11:23:33 -0400, Bob Bridges wrote: >...; TECO (anyone ever use >that?) is a powerful editor - it was on the PDP platform as I recall - with >early automation features that I used extensively, and it was full of odd >uses for and '$' and some other characters, but it did a

Re: Pass PARM by reference to COBOL

The simple answer is yes. It is done with calling special routines for doing, say Date arithmetic. It is done in CICS, etc. In the working storage area you can define a block of storage with various variables. You may wish to do this with a COPY so that the called program gets the pointer to s

Re: Pass PARM by reference to COBOL

On Wed, 16 Aug 2023 13:44:34 +, Seymour J Metz wrote: >What the called program can do depends on the caller. The PARM might be in R/O >storage. > Irrelevant pedantry. I hope that my explicit qualification, "as an Assembler program might" precludes cases in which the PARM is in R/O storage,

Re: Pass PARM by reference to COBOL

> Irrelevant pedantry. Nonsense. > I hope that my explicit qualification, "as an Assembler program might" > precludes cases in which the PARM is in R/O storage, It doesn't. If the caller is RENT from an authorized concatenation and the PARM is a constant in the csect, it will be in SP252. >

Re: Pass PARM by reference to COBOL

What would that accomplish? Telling the INIT the AMODE of the program; That is going to be gotten from the PDS/PDSE directory. And given that this is about the INIT, if the ALC program is in an APF load lib and the load lib for the COBOL program is NON APF this JOBSTEP already failed. How of

Re: Pass PARM by reference to COBOL

On Wed, 16 Aug 2023 14:33:53 -0400, Steve Thompson wrote: >What would that accomplish? Telling the INIT the AMODE of the >program; That is going to be gotten from the PDS/PDSE directory. > It would tell the INIT to ATTACH the program with • an 8-bytes-per-entry parameter list with PLIST8ARALETS=YE

Re: Pass PARM by reference to COBOL

On Wed, 16 Aug 2023 18:23:33 +, Seymour J Metz wrote: >> Irrelevant pedantry. > >Nonsense. > Projection. >> I hope that my explicit qualification, "as an Assembler program might" >> precludes cases in which the PARM is in R/O storage, > >It doesn't. If the caller is RENT from an authorized

Re: Pass PARM by reference to COBOL

> You're peculiarly unwilling to discuss the > case in which the PARM string is simply writable. No, I'm simply unwilling to pretend that it is the only case. From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ..

Re: Has anyone

I've occasionally thought of writing a TECO-like editor for myself. But what with ISPF Edit macros, and ooRexx, and like that, I guess there isn't really much point, is there? Unless it's just for fun... --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Of a proposed course of acti

Re: Has anyone

Bob Bridges wrote, in part: >I once spent an agonizing half-hour trying to help a Unix programmer >code a program in a language I know using some kind of Unix editor >that was so unintuitive I could hardly accomplish anything. As Shmuel suggests, that sounds like vi or one of its relatives. The be

Re: Has anyone

On 8/16/2023 5:41 PM, Phil Smith III wrote: As Shmuel suggests, that sounds like vi or one of its relatives. The best description of vi I've ever heard is: "vi has two modes: one where it corrupts your data, and one where it beeps at you." ++1 I have a cert for being able to use vi from the U

Re: Has anyone

On 8/16/2023 5:41 PM, Phil Smith III wrote: As Shmuel suggests, that sounds like vi or one of its relatives. The best description of vi I've ever heard is:> "vi has two modes: one where it corrupts your data, and one where it beeps at you." Chuckle. That's good. But there are more modes. I