Re: COBOL issue

2021-10-01 Thread Massimo Biancucci
Bernd, forget it ! :D Your code works on my zOS. Best regards. Il giorno ven 1 ott 2021 alle ore 17:55 Bernd Oppolzer < bernd.oppol...@t-online.de> ha scritto: > Many thanks to all who responded and especially to Peter for posting > this piece of ASSEMBLER > which solves the problem. > > I am

Re: COBOL issue

2021-10-01 Thread Bernd Oppolzer
Many thanks to all who responded and especially to Peter for posting this piece of ASSEMBLER which solves the problem. I am very impressed by the helpfulness of this mailing list, which I experienced this time again and many times before. @Max: the code that you provided unfortunately does

Re: COBOL issue

2021-10-01 Thread Massimo Biancucci
I'm sorry, I'm not at a terminal so my idea had not been proven. Il giorno ven 1 ott 2021 alle ore 17:46 Massimo Biancucci ha scritto: > Bernd, > > AFAIK the SET ADDRESS OF is to set a pointer to address a piece of storage. > This is why Cobol doesn't you allow to do such a command. > > If you

Re: COBOL issue

2021-10-01 Thread Massimo Biancucci
Bernd, AFAIK the SET ADDRESS OF is to set a pointer to address a piece of storage. This is why Cobol doesn't you allow to do such a command. If you want to "grab" the ADDRESS OF your working storage variable, you should define a POINTER in LINKAGE then set it to the value and then move it to

Re: COBOL issue

2021-10-01 Thread Tony Thigpen
Also, it's in the back of my mind that you can set a pointer to a '01' level, but only a '01' level. But, I work across all platforms and I may be thinking z/OS. If you are not using the SET ADDRESS against an '01' level, give it a try. Tony Thigpen Tony Thigpen wrote on 10/1/21 10:57 AM:

Re: COBOL issue

2021-10-01 Thread Tony Thigpen
Grab my small assembler program to do this: http://dinomasters.com/coolstuff/bsttezsp.txt Tony Thigpen Bernd Oppolzer wrote on 10/1/21 10:27 AM: Sorry, forgot to mention: I'm on VSE, the Compiler release is COBOL for VSE/ESA 1.1.1; this Compiler definitely only allows items from the Linkage

Re: PL/I vs. JCL

2021-10-01 Thread Seymour J Metz
I don't find EXEC's handling of positional parameters, keyword parameters with value and keyword parameters without value to be complex. But other things in CLIST drive me up the wall. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM

Re: COBOL issue

2021-10-01 Thread Farley, Peter x23353
I would agree with that assessment Bernd. The only remaining restriction on ADDRESS OF in z/OS COBOL is for FILE section items, and even that can be solved with a simple assembler "give me the address of this variable" subroutine if you need it. Most shops already have one such subroutine

Re: PL/I vs. JCL

2021-10-01 Thread Seymour J Metz
Can you guaranty that there will never be a name that is used for both a member and a ddname? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Bob Bridges Sent: Friday, October 1, 2021 9:21 AM

Re: COBOL issue

2021-10-01 Thread Bernd Oppolzer
Sorry, forgot to mention: I'm on VSE, the Compiler release is COBOL for VSE/ESA 1.1.1; this Compiler definitely only allows items from the Linkage Section. Nice to know about later version on other OSes. So there is no danger in applying an ASSEMBLER workaround and probably no other (simple and

Re: COBOL issue

2021-10-01 Thread Joe Monk
Depends on the release of the COBOL compiler. Later releases support working-storage items, earlier releases only allow linkage items. Joe On Fri, Oct 1, 2021 at 8:50 AM Bernd Oppolzer wrote: > Probably asking a COBOL question for the first time :-) > > I am thinking about writing a general

COBOL issue

2021-10-01 Thread Bernd Oppolzer
Probably asking a COBOL question for the first time :-) I am thinking about writing a general sub-program using COBOL which does several different computations, each of them needing different input and output data of different size. Because this should work with Batch and CICS, I am thinking

Re: PL/I vs. JCL

2021-10-01 Thread Bob Bridges
I would never have seen this in advance, but one advantage I found when switching to REXX is that I'm almost eliminated positional parms from my commands. In all but a few cases, the program can tell what it is by looking at it. Thus every user can enter the arguments in the order that seems

Re: Control-M

2021-10-01 Thread kekronbekron
On mainframe, BMC got it right with Control M/O/R/... The interface is just spot on, ultra easy to quickly understand what's going on. I don't know about the distributed app, but on mainframe, oh boy, I love CTM. Have even seen a guy write REXX scripts to build out CTM schedule decks. So for

Re: z/OS 2.5 Announcement out yet?

2021-10-01 Thread Richards, Robert B. (CTR)
Thanks, Gil! Very useful. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Thursday, September 30, 2021 2:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 2.5 Announcement out yet? On Thu, 30 Sep 2021 12:06:46 -0500, David Elliot wrote:

Re: Control-M

2021-10-01 Thread Radoslaw Skorupka
W dniu 22.09.2021 o 21:06, Ward, Mike S pisze: Anyone on here ever used Control-M from BMC? Any comments on the Installation/Maintenance/Performance ...ET AL? Any additional products that had to be purchased because Control-M didn't have everything it needed to run successfully? I don't