This subject comes up every now and then, and I have just found a way that is
new to me.
Since z/OS 2.2, SDSF has a new line command JS on the DA, H, I, O and ST panels
which displays a sub panel which shows the return code and other details for
all the steps taken from the SMF-30 sub type 4
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Wednesday, October 10, 2018 11:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cross-memory POST ERRET and return codes
You might want to create, e.g., a dump, a logrec
@listserv.ua.edu
Subject: Re: Cross-memory POST ERRET and return codes
On Mon, 8 Oct 2018 15:40:40 -0700 Charles Mills wrote:
:>Pursuant to a recent thread here I am converting a cross-memory POST to use
:>IEAMSXMP instead. However ... I still need to support older systems without
:>
ct: Re: Cross-memory POST ERRET and return codes
On Mon, 8 Oct 2018 15:40:40 -0700 Charles Mills wrote:
:>Pursuant to a recent thread here I am converting a cross-memory POST to
use
:>IEAMSXMP instead. However ... I still need to support older systems
without
:>IEAMSXMP support, so
- What is the proper return from an XMPOST ERRET routine? BR 14? I don't
see
anything in the docs.
You're really asking that? Yes, BR 14 or, I suppose, "return to the
address provided in register 14 by whatever mechanism you have chosen to
do that".
- Would an XMPOST LINKAGE=BRANCH ERRET
On Mon, 8 Oct 2018 15:40:40 -0700 Charles Mills wrote:
:>Pursuant to a recent thread here I am converting a cross-memory POST to use
:>IEAMSXMP instead. However ... I still need to support older systems without
:>IEAMSXMP support, so I will be dual-pathing the existing POST. I got to
:>looking
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jim Mulder
Sent: Monday, October 8, 2018 7:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cross-memory POST ERRET and return codes
POSTERR will get control when an abend occurs under the XMPOST
SRB in the target address space. Since you
POSTERR will get control when an abend occurs under the XMPOST
SRB in the target address space. Since you specified MEMREL=NO,
POSTERR will get control under an SRB running in ASID 1.
The return codes 4 and 8 are only for LINKAGE=SYSTEM, so
they are not relevant to your LINKAGE=BRANCH
Pursuant to a recent thread here I am converting a cross-memory POST to use
IEAMSXMP instead. However ... I still need to support older systems without
IEAMSXMP support, so I will be dual-pathing the existing POST. I got to
looking at code that I have not examined in several years, and I am trying
In 20130511.154412.1327...@webmail03.dca.untd.com, on 05/11/2013
at 07:44 PM, esst...@juno.com esst...@juno.com said:
My question is How Do I properly Test and SET the Return Code in the
EDIT MACRO
LASTCC and MAXCC to test.
EXIT CODE(foo) to set.
Any examples would be appreciated.
Thanks Dave
hats exactly what Im Looking for - After posting I located a publication for
CLISTs and CLIST Macros.
-- Original Message --
From: Dave Salt ds...@hotmail.com
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Examing Setting Return Codes in a CLIST/MACRO
Date: Sat, 11 May
Setting Return Codes in a CLIST/MACRO
Date: Sat, 11 May 2013 22:04:42 -0500
On Sat, 11 May 2013 17:09:19 -0400, Dave Salt wrote:
The edit session ends with CANCEL, which means no changes were saved, which
means ISPF sets the return code of the macro to 4. If you want to end with a
different return
Hi,
Not proffecient in CLISTS and RExx.
Can I get some assistance with examining testing a return code in a CLIST
Macro.
In A CLIST i execute the following statements to edit a member of a PDS
and use the ALTER MACRO to change all occurances of XXX.
SET IOFUNC = STR(EDIT)
SET EXITCODE = LASTCC
do more stuff
EXIT CODE(EXITCODE)
Hope that helps,
Dave Salt
SimpList(tm) - try it; you'll get it!
http://www.mackinney.com/products/program-development/simplist.html
Date: Sat, 11 May 2013 19:44:12 +
From: esst...@juno.com
Subject: Examing Setting Return
-MAIN@LISTSERV.UA.EDU
:: Subject: Examing Setting Return Codes in a CLIST/MACRO
::
:: Hi,
:: Not proffecient in CLISTS and RExx.
::
:: Can I get some assistance with examining testing a return code in a
:: CLIST Macro.
::
:: In A CLIST i execute the following statements to edit a member of a PDS
On Sat, 11 May 2013 17:09:19 -0400, Dave Salt wrote:
The edit session ends with CANCEL, which means no changes were saved, which
means ISPF sets the return code of the macro to 4. If you want to end with a
different return code, you can hard code it like this:
EXIT CODE(0)
Or set it using this
better to call the macro using VIEW
instead of EDIT.
Dave Salt
SimpList(tm) - try it; you'll get it!
http://www.mackinney.com/products/program-development/simplist.html
Date: Sat, 11 May 2013 22:04:42 -0500
From: paulgboul...@aim.com
Subject: Re: Examing Setting Return Codes in a CLIST
Greetings from Steven,
If anyone care to contribute, I am interested in known C design defects.
I am most appreciative,
Steven
Date: Thu, 9 May 2013 21:09:38 -0700
From: retired-mainfra...@q.com
Subject: Re: Return codes
To: IBM-MAIN@LISTSERV.UA.EDU
When evaluating the conditional
, May 09, 2013 7:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Return codes
In
a6cf87cbc0b60a459cb79af044a096db2227dc9...@mailccr.us.syncsort.com,
on 05/08/2013
at 08:34 PM, Blaicher, Christopher Y. cblaic...@syncsort.com
said:
Item of note, unless you are working with all your own code, you
Gilmore
:: Sent: Wednesday, May 08, 2013 8:05 PM
:: To: IBM-MAIN@LISTSERV.UA.EDU
:: Subject: Re: Return codes
::
:: This practice reflects another C design defect. In the absence of an
:: explicit boolean data type, C uses the dubious but ineluctable
:: convention that a coded-arithmetic value of 1
Hi ,
Can some one let me know why the return code generated is a mutilple of 4? e.g
4,8,12,16
Thanks,
Ron T
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the
While there's no hard and fast rule, i.e. nothing prevents you from generating
any return code from your programs, it's a tradition that return codes are a
multiple of 4.
0 - Normal
4- Warning
8 - Error
12 - Severe Error
16 - Terminal Error
Mark Jacobs
Can some one let me know why the return code generated is a mutilple of 4?
e.g 4,8,12,16
Back in the day when every byte counted, programmers would use the RC in R15 as
an index into a jump table, where each four byte entry was itself an
unconditional branch instruction, which was a four byte
On 5/8/2013 11:53 AM, Mark Jacobs wrote:
While there's no hard and fast rule, i.e. nothing prevents you from generating
any return code from your programs, it's a tradition that return codes are a
multiple of 4.
0 - Normal
4- Warning
8 - Error
12 - Severe Error
16 - Terminal Error
Which
Engineer Principal
BCBS Minnesota
Phone: 651.662.3546 Mobile: 651.428.8826
From: Ron Thomas ron5...@gmail.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 05/08/2013 12:45
Subject:Return codes
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Hi ,
Can some one let me
Ron:
To add to Mark's reply, that's because the return code (in register 15),
was traditionally used to index a table of branch instructions (each of
which were 4 bytes long), such as:
B RETTABLE(R15)
...
RETTABLE B OK
B FAIR
Mark Jacobs wrote:
While there's no hard and fast rule, i.e. nothing prevents you from generating
any return code from your programs, it's a tradition that return codes are a
multiple of 4.
0 - Normal
4- Warning
8 - Error
12 - Severe Error
16 - Terminal Error
IT version of Richter Scale
On 5/8/2013 2:14 PM, Elardus Engelbrecht wrote:
Another possible reason is - same return codes standards are also
used for macros (system services) and system exits. So one set of
convention is used to pass info including RC from one module to
another.
While I prefer the branch table
There are also situations in which one wants to be able to set more
than one of the diagnostic bits in a return code additively and
unambiguously, and the alternative use of 0, 2, 4, 8, 16, . . . ,
i.e., the sequence 2^i, i = 0, 1, 2, . . . , powers of 2, permits this
to be done.
Still, the fact
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Gilmore
Sent: Wednesday, May 08, 2013 2:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Return codes
There are also situations in which one wants to be able to set more than one of
the diagnostic bits
, by adding more
return codes. I would have preferred the old 0,4,8,12 paradigm, with R0
set to a reason code.
And ISRSUPC SRCHFOR returns RC=0 if the target is not found; RC=1 if
the target is found.
-- gil
--
For IBM-MAIN subscribe
Chris Blaicher,
Your sort of B/T has important uses, but one composed only of
addresses is useful too. Perhaps it shoul;d be called an address
table to avoid confusion. I will; send you an example privately.
John Gilmore, Ashland, MA 01721 - USA
On May 8, 2013, at 3:50 PM, John Gilmore jwgli...@gmail.com wrote:
Your sort of B/T has important uses, but one composed only of
addresses is useful too. Perhaps it shoul;d be called an address
table to avoid confusion. I will; send you an example privately.
If you have a table with 8 byte
: Paul Gilmartin paulgboul...@aim.com
Sender: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Date: Wed, 8 May 2013 15:46:38
To: IBM-MAIN@LISTSERV.UA.EDU
Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Return codes
On Wed, 8 May 2013 14:41:28 -0400
name?) return codes, and shift left by 2
or 3 bits as appropriate. But it may be that the existing convention
to some extent discourages very sparse return code domains, which
makes the branch or address table scheme largely unusable.
Tony H
| M: 512-627-3803
E: cblaic...@syncsort.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Gilmore
Sent: Wednesday, May 08, 2013 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Return codes
Chris Blaicher,
Your sort of B/T
And then you have C / C++ that uses RC=1 as the good return code. Any other is
bad.
Lloyd
- Original Message
From: Gerhard Postpischil gerh...@valley.net
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wed, May 8, 2013 2:41:51 PM
Subject: Re: Return codes
On 5/8/2013 2:14 PM, Elardus
Lloyd Fuller wrote
begin extract
And then you have C / C++ that uses RC=1 as the good return code. Any other is
bad.
/end extract
This practice reflects another C design defect. In the absence of an
explicit boolean data type, C uses the dubious but ineluctable
convention that a
Message-
:: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:: Behalf Of Lloyd Fuller
:: Sent: Wednesday, May 08, 2013 6:00 PM
:: To: IBM-MAIN@LISTSERV.UA.EDU
:: Subject: Re: Return codes
::
:: And then you have C / C++ that uses RC=1 as the good return code. Any
:: other
At 20:34 -0400 on 05/08/2013, Blaicher, Christopher Y. wrote about
Re: Return codes:
What I normally do is check for zero, if that is what you expect
most often, then, if that fails, go through all the gyrations.
BALR r14,r15Call your routine
LTR R14,R15
40 matches
Mail list logo
