Try using the field. Live and learn.
On Thu, 3 Dec 2020 15:21:24 -0500 Joseph Reichman
wrote:
:>EXTENDED CONTROL PSW FROM THE RB
:>LEVEL OR LINKAGE STACK LEVEL WHICH
:>CREATED THE ESTAE EXIT AT THE TIME IT
:>LAST INCURRED AN INTERRUPT OR 0 FOR
:>ESTAI. OR PSW USED TO GIVE FRR
:>CONTROL
:>
:>
I appreciate your help regarding what SDWARBAD represents
I recall having an abend in a metal C program
Which I linked to it may well have been running in supervisor state but it was
a user
Program
I am just trying to just trying to determine the case where the abend happened
in a
On Fri, 4 Dec 2020 16:12:21 -0800, Charles Mills wrote:
>And for JCL perhaps 255 is a reasonable limit. With only about 55 usable
>columns on a JCL continuation statement, anything more than that becomes a
>little unwieldy. (Yes, one might say all JCL statements are unwieldy!)
>
Don't denigrate
On Sat, 5 Dec 2020 09:22:19 -0800, Charles Mills wrote:
>
>... IIRC I had a bug in software I was
>developing and created a dataset with what I had intended would be a PDS
>member name, TEST or FOO or something like that, and it worked with no
>issues. In some cases there might be a catalog access
By "filename" I was referring to a UNIX filename, not a legacy dataset name.
That was the topic I was responding to, the minimum and maximum lengths of
UNIS filename specifications in JCL, DYNALLOC and TSO ALLOC. I would guess
that A would be a valid dataset name. IIRC I had a bug in software I
Corroborating SMF 70 is a good source for this - as we use it in our code,
too.
Cheers, Martin
Martin Packer
Systems Investigator & Performance Troubleshooter, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
Shmuel and Lennie and I took the time to provide the correct answer. You
apparently choose to ignore. Sad.
SDWARBAD is valid only for supervisor state cases, as the comment says.
SDWANAME is never valid for that case. If a type 2/3/4 SVC routine blew
up, the RB address will be the address of
On Sat, 5 Dec 2020, at 00:12, Charles Mills wrote:
> I guess '/' is the only valid 1-byte filename in JCL, right?
I recall reading tapes (on MVS) produced on VAXes or some
other 'foreign' computer system. They had 17 character ANSI
file datasetname values (17 chars being all the HDR1 label has
