Here is my JES2 procedure:
//JES2PROC MEMBER=JES2&SYSCLONE.
//IEFPROC EXEC PGM=HASJES20,PARM=(WARM,NOREQ)
//PROC00DD DSN=SYS1.&SYSNAME..PROCLIB,DISP=SHR
// DD DSN=SYS1.AQH.PROCLIB,DISP=SHR
// DD DSN=SYS1.PROCLIB,DISP=SHR
Interesting;
An experiment with using PARMLIB instead of HAPPPARM shows that the member must
be named HASJES2. The specification of the PARM= is ignored.
Matthew
--
For IBM-MAIN subscribe / signoff / archive access instruction
Hi all,
I'm looking into SMF 74 subtype 4 and gathering XCF CPU info.
I've noticed that sometimes the field R744PWAI (which shows wait time in
microseconds) can have a higher value than the RMF interval.
This caught my attention.
Is that possible or am I doing something wrong?
Best Regards
Are you summing over multiple engines for the 1 coupling facility? That section
is repeated, once for each engine.
Cheers, Martin
From: IBM Mainframe Discussion List on behalf of
Ituriel do Neto <03427ec2837d-dmarc-requ...@listserv.ua.edu>
Date: Friday, 29 November 2024 at 18:40
To: IBM-MA
Martin,
First of all, thank you for your attention.
Field SMF744PN (Number of processor CF data sections) indicates there is only
one section.
And what I was thinking was a big number, when converted to decimal, seems to
be a negative number. Field R744PWAI presents x'EB4262F2'
Is that possib
But look at the bonuses those managers and
project leads received in recognition of their contribution to the bottom line.
At 02:35 PM 11/25/2024, Itschak Mugzach wrote:
LOL.
A mainframe site in Israel plans to drop the mainframe for 15 years
or more. They started with a six years project to
W dniu 29.11.2024 o 17:39, Matthew Stitt pisze:
Interesting;
An experiment with using PARMLIB instead of HAPPPARM shows that the member must
be named HASJES2. The specification of the PARM= is ignored.
Wrong.
HASJES2 is default name of the member. And it seems the member name was
not specif
Indeed, HASPPARM DD is used to define location of the member.
However my goal is to get rid off the DSN and use logical parmlib
concatenation instead.
Nowadays most of the procedures, like TSO, SDSF, CSF, DFRMM, etc. no
longer use DDname for specification of parmlib member.
Instead logical parml
FedEx moved to AWS. ING too. All these smug comments are a bit misplaced.
> On 30 Nov 2024, at 07:49, Michael Oujesky wrote:
>
> But look at the bonuses those managers and project leads received in
> recognition of their contribution to the bottom line.
>
> At 02:35 PM 11/25/2024, Itschak Mu
It is NOT a JCL.
We have two different animals, both having same name:
1. PARM keyword in START command
2. PARM in EXEC card in JCL
It is never said that PARM or DISP or SPACE or any other keyword can be
specified in MVS START command to override the keyword in JCL. Obvious
reason: a procedure
Three of my last four clients have two-year projects going to get off the
mainframe. All three (as I recall) are between five and eight years into their
projects and no end in sight. It's an open jest among all the IT guys, but no
sign that management thinks any differently about it in any of
Yes, 25 years and counting. Some things just weren’t meant to be. This
project is in the category of ‘Of being involved in conducting an Unnatural
Act’.
Sent from my iPhone
> On Nov 29, 2024, at 18:49, Michael Oujesky wrote:
>
> But look at the bonuses those managers and project leads rece
12 matches
Mail list logo
