issue, they will be able to diagnose
further.
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Mark Jacobs
Sent: 08 April 2021 16:12
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: STC JESYSMSG Quandry
EXTERNAL EMAIL
AFAIK it's transparent to the user. JES2 compr
AFAIK it's transparent to the user. JES2 compresses/decompresses data
written/read to/from each track group. It's completely optional. The zEDC
Integrated Accelerator must be available on the system where JES2 is to perform
SPOOL compression, and ADVANCED_FORMAT=YES needs to be specified in the
On 2021-04-08, at 07:01:20, John S. Giltner, Jr. wrote:
>
> Not sure if it really makes a difference, but I noticed that one of the
> SYSOUT classes, A I think, had COMPRESS=YES and the class K had COMPRESS=NO.
>
Does the SDSF Rexx interface using a dynamically DDNAME uncompress
on-the-fly?
Is
Yea. Not relevant to this problem. We don't have compression hardware on this
system so it's not enabled there.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
‐‐‐ Original Message
Not sure if it really makes a difference, but I noticed that one of the SYSOUT
classes, A I think, had COMPRESS=YES and the class K had COMPRESS=NO.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
27; jobcards are the same, just a stretch here
> >
> >
> >
> > Carmen Vitullo
> >
> > -Original Message-
> >
> > From: Mark 0224d287a4b1-dmarc-requ...@listserv.ua.edu
> >
> > To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU
> >
> >
AIN@LISTSERV.UA.EDU
>
> Date: Wednesday, 7 April 2021 9:02 AM CDT
>
> Subject: Re: STC JESYSMSG Quandry
>
> I might have forgotten to mention that after the STC ends, all of the
> expected messages are in JESYSMSG, they're just not being shown in SDSF while
> the STC
nd only if your stcclass is set to not purge.
Carmen Vitullo
-Original Message-
From: Mark <0224d287a4b1-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN
Date: Wednesday, 7 April 2021 9:02 AM CDT
Subject: Re: STC JESYSMSG Quandry
I might have forgotten to mention that af
' jobcards are the same, just a stretch here
>
>
>
> Carmen Vitullo
>
> -Original Message-
>
> From: Mark 0224d287a4b1-dmarc-requ...@listserv.ua.edu
>
> To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU
>
> Date: Wednesday, 7 April 2021 8:38 AM CDT
&
;
> To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU
>
> Date: Wednesday, 7 April 2021 8:38 AM CDT
>
> Subject: Re: STC JESYSMSG Quandry
>
> I'm looking at that too.
>
> From the generated jobcard on the system that works.
>
> //XX JOB MSGLEVEL=1
>
> And the o
, 7 April 2021 8:38 AM CDT
Subject: Re: STC JESYSMSG Quandry
I'm looking at that too.
>From the generated jobcard on the system that works.
//XX JOB MSGLEVEL=1
And the on the system that doesn't.
1 //XX JOB MSGLEVEL=1
The internal text for the jobcard statement looks
I'm looking at that too.
>From the generated jobcard on the system that works.
//XX JOB MSGLEVEL=1
And the on the system that doesn't.
1 //XX JOB MSGLEVEL=1
The internal text for the jobcard statement looks the same too.
Still digging.
Mark Jacobs
Sent from ProtonMail, Swiss-based
In the description of msgIEFA111I it states:
This message is only issued if MSGLEVEL=(,1) is in effect for this job.
So if your JES STCCLASS is showing MSGLEVEL=(1,1), then perhaps somewhere else
is overriding MSGLEVEL.
Dana
On Tue, 6 Apr 2021 17:54:27 -0500, Mike Schwab wrote:
>Is the de
rv.ua.edu>
To: IBM-MAIN
Date: Tuesday, 6 April 2021 6:24 PM CDT
Subject: Re: STC JESYSMSG Quandry
The system that is showing the output.
$DSTCCLASS,LONG
$HASP837 STCCLASS
$HASP837 STCCLASS AUTH=(ALL),BLP=YES,COMMAND=EXECUTE,
$HASP837 CONDPURG=NO,DSENQSHR=ALLOW,IEFUJP=YES,
$HASP837 IEFUSO=YE
The system that is showing the output.
$DSTCCLASS,LONG
$HASP837 STCCLASS
$HASP837 STCCLASS AUTH=(ALL),BLP=YES,COMMAND=EXECUTE,
$HASP837 CONDPURG=NO,DSENQSHR=ALLOW,IEFUJP=YES,
$HASP837 IEFUSO=YES,JESLOG=(NOSPIN),LOG=YES,
$HASP837 MSGLEVEL=(1,1),MSGCLASS=A,OUTDISP=(HOL
Is the default MSGLEVEL different?
https://www.ibm.com/docs/en/zos/2.1.0?topic=mp-subparameter-definition-6
JOB statement MSGLEVEL=(1,1) should print everything.
On Tue, Apr 6, 2021 at 2:34 PM Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
>
> On one system (different JES2 MA
4b1-dmarc-requ...@listserv.ua.edu
>
> To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU
>
> Date: Tuesday, 6 April 2021 3:12 PM CDT
>
> Subject: Re: STC JESYSMSG Quandry
>
> Both systems are z/OS 2.4.
>
> Mark Jacobs
>
> Sent from ProtonMail, Swiss-based encrypted ema
1 3:12 PM CDT
Subject: Re: STC JESYSMSG Quandry
Both systems are z/OS 2.4.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Tuesday, April 6t
>
> Date: Tuesday, 6 April 2021 2:34 PM CDT
>
> Subject: STC JESYSMSG Quandry
>
> On one system (different JES2 MAS), our STCs while executing only show this
> line in SDSF.
>
> STMT NO. MESSAGE
>
> 2 IEFC001I PROCEDURE XX WAS EXPANDED USING SYSTEM LIBRARY ..
responding to myself, the IEFA111I message is stating either the ALLOCxx member
settings or system defaults for ALLOCxx
Carmen Vitullo
-Original Message-
From: Carmen
To: IBM-MAIN
Date: Tuesday, 6 April 2021 3:04 PM CDT
Subject: Re: STC JESYSMSG Quandry
Mark what OS
Mark what OS release is the first example?
IIRC the message was expanded with JES2 z/os 2.3
Carmen Vitullo
-Original Message-
From: Mark <0224d287a4b1-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN
Date: Tuesday, 6 April 2021 2:34 PM CDT
Subject: STC JESYSMSG Quand
On one system (different JES2 MAS), our STCs while executing only show this
line in SDSF.
STMT NO. MESSAGE
2 IEFC001I PROCEDURE XX WAS EXPANDED USING SYSTEM LIBRARY ..
But on other systems it's showing much more.
STMT NO. MESSAGE
2 IEFC001I PROCEDURE X WAS EXPANDED USING SYS
22 matches
Mail list logo
