Or check out
COB2JOB from https://gsf-soft.com/Freeware/
//Lasse
-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List För David Spiegel
Skickat: den 30 januari 2024 03:56
Till: IBM-MAIN@LISTSERV.UA.EDU
Ämne: Re: How can I determine the User Name associated with the current
Hi Cameron,
Can you please send me the source of your working program?
My email address is da...@ddstar.com
Thanks and regards,
David
On 2024-01-29 16:49, Cameron Conacher wrote:
Thanks everyone,
This is just what I needed.
Appreciate the help.
Thanks
…….Cameron
From: IBM Mainframe
I didn't realize you were even old enough to retire. :)
Brian
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Thanks very much.
I struggled at first, but finally got through.
This is perfect.!!
On Mon, Jan 29, 2024 at 9:31 AM Binyamin Dissen
wrote:
> On Mon, 29 Jan 2024 13:36:51 + Cameron Conacher
> <03cfc59146bb-dmarc-requ...@listserv.ua.edu> wrote:
>
> :>Good Morning,
> :>I know I can do this
Thanks everyone,
This is just what I needed.
Appreciate the help.
Thanks
…….Cameron
From: IBM Mainframe Discussion List On Behalf Of
Lars Höglund
Sent: Monday, January 29, 2024 11:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Sv: How can I determine the User Name associated with the current
Bummer! Line macro support works but it was missing one thing at the time. I
don’t even recall for sure, maybe it was GLOBAL_LINE_COMMAND_TABLE which I see
now. I also recall opening a requirement for whatever it was. I still use
LMAC, but some of my sandbox LPARs are using a line macro
ISPF has 3 variables that an application can interrogate for the version:
ZOS90RL, ZISPFOS, and ZENVIR. The fact that the edit says the ISPF version must
be between 5.8 and 7.9 makes me suspect it is using ZENVIR.
What is in the ISPF ZENVIR variable on your z/OS 3.1 system? For example, on a
I cross posted this to
https://discord.com/channels/880322471608344597/1201602121225752746 on the
System Z Enthusiasts discord.
Have you looked at CBTTape Fole 961 for Yves Colliard’s YCLMAC - A collection
of user line commands for use in ISPF Edit and View ?
Hope this helps –
REGION=(24,31,64) memory limits is available
On Mon, Jan 29, 2024 at 12:27 PM Jon Perryman wrote:
> On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen <
> bdis...@dissensoftware.com> wrote:
>
> >Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an
> >SDWA and there is no
REGIONX=(24,31,53) memory limits is available.
On Mon, Jan 29, 2024 at 12:27 PM Jon Perryman wrote:
> On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen <
> bdis...@dissensoftware.com> wrote:
>
> >Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an
> >SDWA and there is
Hello, we just turned on z/OS 3.1, and its component ISPF 3.1 here.
Now, I just saw when editing a member that my LMAC program (from Doug
Nadel originally) no longer works, and gives me a message:
LMAC005 You must be running an ISPF version greater than 5.8 and less
than 7.9 to run LMAC.
On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen
wrote:
>Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an
>SDWA and there is no reason to check R0 for 12 and alternate code paths?
Obviously Peter is not making that guarantee but how many jobs run with
REGION=0M or
Tom - enjoy your well deserved retirement !
Jerry Whitteridge
Sr Manager Managed Services
jerry.whitteri...@albertsons.com
480 578 7889
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Horein
Sent: Friday, January 26, 2024 5:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Something like this
Code Extract:
LINKAGE SECTION.
01 CB1.
05 PTR1 POINTER OCCURS 512.
01 CVT.
05 CVT1 POINTER OCCURS 512.
01 CB2.
05 PTR2 POINTER OCCURS 256.
This thread led me to wonder if there was a change from STIMER REAL (meaning a
time interval, which is the default) to STIMER TASK (meaning a CPU time limit),
or vice versa.
Note that STIMERM does not support the "TASK" option (it was felt to be too
complex, and not necessary, to have to deal
I looked at the APAR text and I would consider it inaccurate (and/or incorrect).
>From the APAR text:
It should be noted:
IMS establishes a time limit using the STIMER macro and the
TASK parameter to indicate that the time interval is only
decreased when the associated task is running. Any ESS
Thanks for the link. Today I learned that what's included in the timing is
controlled by the STIMER parameter in IMS procedures.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Attila Fogarasi
Sent: Sunday, January 28, 2024 3:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
On Mon, 29 Jan 2024 13:36:51 + Cameron Conacher
<03cfc59146bb-dmarc-requ...@listserv.ua.edu> wrote:
:>Good Morning,
:>I know I can do this in CICS, but I am digging around to see if this can be
done in a batch COBOL program.
:>Basically, I just want to include Fred's Name in a report I
On Mon, 29 Jan 2024 12:57:53 + Peter Relson wrote:
:>But none of this is appropriate to do within a recovery routine. That is why
there is an SDWA.
:>And if the system was unable to provide the ESTAE-type recovery routine with
an SDWA, then too bad (and encourage the creator to use
Good Morning,
I know I can do this in CICS, but I am digging around to see if this can be
done in a batch COBOL program.
Basically, I just want to include Fred's Name in a report I generate, where
Fred is the RACF ID associate with the currently executing Batch JOB. (a COBOL
program).
I could
Thanks
> On Jan 29, 2024, at 7:58 AM, Peter Relson wrote:
>
>
> Is there any way to know whether this is an SVC or abend
>
> I mean I know for SVC the length must be 2 but that doesn't mean it cannot
> be a abend
>
>
> Abend is an SVC. So you could conceivably look at RBINTCOD for
Is there any way to know whether this is an SVC or abend
I mean I know for SVC the length must be 2 but that doesn't mean it cannot
be a abend
Abend is an SVC. So you could conceivably look at RBINTCOD for x'000D'.
A different question would be whether you can tell that the error was not
22 matches
Mail list logo
