Re: Automatic reply to inquirymsgs in cobol-pgms

I forgot to say this is OPM-Cobol

Mvh. / Regards / Terveisin

Geir





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

Look at using reply list entries

On Thu, Dec 6, 2012 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.

--
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.