The behavior you are observing is exactly what our design intended. Like any
APAR that is SEC/INT,
IBM will not discuss the rationale, design, or implementation.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mike Schwab
Sent: Friday, August 1, 2025
https://www.ibm.com/docs/en/zos/3.1.0?topic=syntax-parmlib-command
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph Reichman
Sent: Monday, June 30, 2025 11:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Tried exec pgm=
Not sure what you mean by par
The 047 abend is from MODESET. MODESET knows only that JSCBAUTH is not on.
It has no
knowledge about why JSCBAUTH is not on, and determining that requires some
investigation which is beyond the scope of MODESET.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion Lis
_
From: IBM Mainframe Discussion List on behalf of
James Mulder
Sent: Sunday, June 29, 2025 11:23:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: APF authorized TSO programs
What method are you using to initiate giving control to your program?
Jim Mulder
-Original Message-
From: IB
What method are you using to initiate giving control to your program?
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph Reichman
Sent: Sunday, June 29, 2025 9:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: APF authorized TSO programs
JUST CHECKED
CPC SI = .16n.16m..16s
Model:
Model PC:
Model TC:
Model RC:
If it is a C0D-01 abend, it means that z/OS was presented with an I/O
interrupt with what we consider to be invalid status in the IRB.
I would need to see the contents of the IRB and review the I/O architecture to
rule on whether or not the status is architecturally valid.
Jim Mulder
-O
That is correct. You program is running under a TCB that is not a jobstep
TCB when you run it under TESTAUTH.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph Reichman
Sent: Friday, June 20, 2025 12:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RE
DIDOCS/MCS consoles should support a wide range of screen sizes. I use
ScreenSize=60x160 in the PCOM emulator, with UNIT(3270-X) on CONSOLxx.
During the NIP console phase, it is treated at 24x80, and then switches to
62x160 at the end of NIP.
Jim Mulder
-Original Message-
From: IBM
I would try something like this on each system.
SLIP SET,IF,A=TRACE,N=(IEFENFFX,0,0),ID=ENFS,TD=(STD,1R?+0?,+7F),END
And run GTF with TRACE=SLIP
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mark Jacobs
Sent: Friday, June 6, 2025 9:31 AM
To: IBM-MAI
based upon your
application.
Which manual do you have?
On Wed, 4 Jun 2025 01:37:54 + James Mulder wrote:
:> You are getting the correct result. Your ALET is on the PASN access list,
and you are getting return code 8, for which the documentations says:
:>
:>Meaning: The specified
L. If CADS=YES was specified on the call, the ALET does not point to an
entry for a SCOPE=COMMON data space.
I am getting R15=8. The ALET is, in fact, in the PASN (begins with 01).
Am I missing something obvious?
On Tue, 3 Jun 2025 16:58:14 + James Mulder wrote:
:>Correcting to ad
, when
condition code 3 is set. MVS/ESA provides the
TESTART macro instruction for use instead of
the direct use of TEST ACCESS.
Jim Mulder
-Original Message-
From: James Mulder
Sent: Tuesday, June 3, 2025 2:23 PM
To: IBM Mainframe Discussion List
Subject: RE: Seerms like TAR requires AR
mode gets CC=3.
So I guess that matches your testing.
Which OS's get consistent results from TAR? VSE? Linux?
Should the POPs have a warning?
On Tue, 3 Jun 2025 16:58:14 +0000 James Mulder wrote:
:>Correcting to add a missing word "is"
:>
:>I would anticipate that i
y used for something that
was not part of the original FPFS (Final Programming Functional Specification))
for the release.
Jim Mulder
-Original Message-
From: James Mulder
Sent: Tuesday, June 3, 2025 12:23 PM
To: IBM Mainframe Discussion List
Subject: RE: Seerms like TAR require
pick up if the target address space (non-swapable) goes away, but
I am a great believer in belt and suspenders. Not obvious to me what TESTART
would add.
But, at any rate, is the POPs description incorrect and is AR mode required (as
my experience shows)?
.On Tue, 3 Jun 2025 15:23:15 +0000 Ja
On z/OS, the TAR instruction is not useful by itself. You should instead use
the TESTART macro, which PCs to the operating system to analyze a CC3 from the
TAR instruction.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Binyamin Dissen
Sent: Tuesday,
In SYS1.SBLSCLI0 I see compiled Rexx execs named CSVDYNXI and CSVLNKLS.
They are undocumented and unsupported.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Binyamin Dissen
Sent: Tuesday, April 8, 2025 2:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
For compiler listings and actual assembler listings, and assembler inlines,
and for interfacing with
z/OS via its macro interfaces, PL/X has always had a huge advantage over C/C++.
In my opinion, it is very unfortunate for the z/OS ecosystem that IBM
executive management has never chose
You could never boot z/OS from the DVD drive in the mainframe. You could
boot DSS Standalone Restore from the DVD drive in the mainframe,
and use it to restore dumped z/OS volumes from the DVD drive in the mainframe
to DASD volumes, and then boot z/OS from a restored DASD volume.
Jim Mulder
This is a design problem in the machine. LPAR notifies the SE that a
disabled wait PSW has been loaded, but there is no disabled wait PSW
provided in that interface. At some point later, the SE asks LPAR for the
current PSW, and if a subsequent IPL has already started, it gets
a PSW from tha
al Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Monday, January 27, 2025 2:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is the STIMERM ID= guaranteed to be unique within the task?
On Mon, 27 Jan 2025 18:14:43 +, James Mulder wrote:
> Other than
Other than 4G wrap, STIMERM ID= is unique within the z/OS image.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Binyamin Dissen
Sent: Monday, January 27, 2025 11:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is the STIMERM ID= guaranteed to be unique
In general, you should not use the TAR instruction directly because you would
not know what to do with
condition code 3. Instead, use the TESTART macro.
Jim Mulder
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
John Dravnieks
Sent: Tuesday, January 14, 2025
24 matches
Mail list logo
