Re: Automatic reply to inquirymsgs in cobol-pgms

My small testsystem regarding these things are now working.

Summary:

- Calling the API 'QLRSETCE' in the first cobol-pgm in the run unit transfers control to a self-made error handling pgm wherever an exeption appears in the run unit.(Tanks to Mark Austin for the example code)
- In the error handling pgm, I can decide what response to the error I want to give(G, C, D, F). I normally want a dump for error fixing.
- All this combined with ' CHGJOB INQMSGRPY(*SYSRPYL)' in the calling CL gives me full automatic control in case of an error situation, and no manually responses is needed in my batch-CLs(hopefully).

Mvh. / Regards / Terveisin

Geir Kildal





-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of geir.kildal@xxxxxxxxxx
Sent: Wednesday, January 09, 2013 8:22 AM
To: cobol400-l@xxxxxxxxxxxx
Subject: Re: [COBOL400-L] Automatic reply to inquirymsgs in cobol-pgms

Jon,

Yeah right, deja-vu. I even found those testpgms I referred to.
May be it's time for me to retire?

But thanks to you anyway.



Mvh. / Regards / Terveisin

Geir

PS.: I think I'll keep on for some years still...



-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Tuesday, January 08, 2013 4:08 PM
To: COBOL Programming on the IBM i (AS/400 and iSeries)
Subject: Re: [COBOL400-L] Automatic reply to inquirymsgs in cobol-pgms

Geir,

Does this have a deja-vu feel for you? It did for me so I went back and found this thread http://archive.midrange.com/cobol400-l/201002/msg00020.html

Some guy called Geir asking a very similar question <grin>

That link is part way through the thread and has sample code etc. plus answers to related issues. But to directly answer your question there are 5 parms and they would normally be 01s or 77s.


On 2013-01-08, at 9:49 AM, <geir.kildal@xxxxxxxxxx> <geir.kildal@xxxxxxxxxx> wrote:

Hi Jon.

A question about calling the QLRSETCE API from an OPM-cbl-pgm: Should the parameters be five 01-levels or only one?
Maybe you have a simple example showing how to call this API from an OPM-pgm?

Mvh. / Regards / Terveisin

Geir





-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Thursday, December 06, 2012 5:16 PM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] Automatic reply to inquirymsgs in cobol-pgms

Oooppppsss - senior moment - forgot the link
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=
%2Fapis%2Fhll2.htm

.
On 2012-12-06, at 10:36 AM, Jon Paris wrote:

COBOL actually has a built-in mechanisms for this - They are different for OPM COBOL and ILE COBOL but you'll find the links here.

We added this support way back when I was responsible for COBOL architecture but sadly most COBOL shops seem unaware of it. It should handle the kind of situation you describe.


On 2012-12-06, at 10:15 AM, <geir.kildal@xxxxxxxxxx> wrote:

Hi.

I'm looking for a method to get automatic reply to inqmsg in running Cobol-pgms.
Example: A batch containing CL-programs and Cobolpgms is runnig. A cobolpgm fails and awaits reply (I, D, C etc). How can this be answered automatically, and how will I know that an error has occurred afterwards?

Regards

Geir Kildal






-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Essinger
Sent: Thursday, November 29, 2012 12:05 AM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] how to extract the most common date format
- YYYYMMDD

Nice Jon!

Group levels are always character, so that makes sense!

Jim


On Wed, Nov 28, 2012 at 2:53 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Sorry - I misunderstood the original intent.

There's a much easier answer than the one you derived - you should
be able to just redefine the target field. It may not fit directly
into what you are doing depending on how/where A0468X-DUE-DATE is
defined but all you need to do is this:

01 ATR.

05 A0468X-DUE-DATE.

10 ws-num-date Pic 9(8).

and then:
compute ws-num-date
= function EXTRACT-DATE-TIME (ws-date '@Y%m%d').

A0468X-DUE-DATE is now an alpha field with the desired value.



On 2012-11-28, at 2:57 PM, Stone, Joel wrote:

Thanks but here is IBM doc example from "Websphere Development
Studio

ILE COBOL reference" v5 SC09-2539-02:

MOVE FUNCTION EXTRACT-DATE-TIME (date-2 '%m/%d') to alphanum-1.

It's a stinker - I guess I will have to format as 2012/11/28 and
then

SUBSTRING out the slashes.

It seems that once the slashes or spaces are gone from the edit
string,

the compiler chokes because it thinks it is numeric.

Is it possible that it is impossible to pull the most common date

format? Does no one else use the cobol compiler with dates?

So here is the ugly code that I created:

move function EXTRACT-DATE-TIME (ws-date '@Y/%m/%d') to
ws-date-yyyy-mm-dd string ws-date-yyyy-mm-dd (1:4)
ws-date-yyyy-mm-dd (6:2)
ws-date-yyyy-mm-dd (9:2)
delimited by size into A0468X-DUE-DATE of AFTR

Does anyone else use DATE functions in COBOL/ILE? Maybe the are
full of

bugs??

There are no examples on a google search.





-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:

cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris

Sent: Wednesday, November 28, 2012 12:20 PM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] how to extract the most common date
format
-

YYYYMMDD

Haven't got time to test Joel but if I recall correctly the
editing

should go in the target field's pic.

On 2012-11-28, at 1:16 PM, Stone, Joel wrote:

This works:

move function EXTRACT-DATE-TIME (ws-date '@Y %m %d') to
A0468X-DUE-DATE of AFTR

But result is "2012 11 28" (embedded spaces).

The obvious fix is

move function EXTRACT-DATE-TIME (ws-date '@Y%m%d')

<--------no spaces between ymd

to A0468X-DUE-DATE of AFTR


But this gives compiler error

* 445 MSGID: LNC2780 SEVERITY: 30 SEQNBR: 027800
Message . . . . : Numeric function 'FUNCTION

EXTRACT-DATE-TIME' was

found, but was not allowed in this context. Statement

discarded.

Any idea how to get YYYYMMDD result?

Thanks

_________________________________________________________________
_ _ ___ This outbound email has been scanned for all viruses by
the MessageLabs

Skyscan service.

For more information please visit http://www.symanteccloud.com
_________________________________________________________________
_
_
___
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing

list

To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing

list

To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.


__________________________________________________________________
_ _ ____ This inbound email has been scanned for all viruses by
the MessageLabs

SkyScan

service.
__________________________________________________________________
_
_
____

__________________________________________________________________
_ _ __ This outbound email has been scanned for all viruses by the
MessageLabs

Skyscan service.

For more information please visit http://www.symanteccloud.com
__________________________________________________________________
_
_
__
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing

list

To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list To post a message email:
COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.