RE: CL program

["John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>]

I need to monitor for message CPF2130. how do I put that in my cl job and
how do respond with an I to ignore (if that's what I want to do)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Peter.Colpaert@xxxxxxxxx
Sent: Tuesday, January 31, 2006 8:48 AM
To: Midrange Systems Technical Discussion
Subject: RE: CL program

Make sure the source type is CLLE and not CLP.

HTH,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
31/01/2006 14:41
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: CL program






When I enter the cource in QCLSRC, it doesn't like the CALLPRC lines

-----Original Message-----
From: midrange-l-bounces+jacandidi=rutgersinsurance.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+jacandidi=rutgersinsurance.com@xxxxxxxxxxxx] On
Behalf Of michael@xxxxxxxxxxxxxxxxxx
Sent: Tuesday, January 31, 2006 8:33 AM
To: Midrange Systems Technical Discussion
Subject: RE: CL program

That is an ILE CL program. Create it with CRTBNDCL, or option 14 from
PDM with a CLLE source type.

> -------- Original Message --------
> Subject: RE: CL program
> From: "John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>
> Date: Tue, January 31, 2006 8:18 am
> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
> 
> Is this an ILE C program. Do it compile it that way?
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Monday, January 30, 2006 5:44 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: CL program
> 
> 
> Why use RTVSYSVAL instead of CEELOCT?  Seems like CEELOCT would be 
shorter

> than RTVSYSVAL followed by CEEDAYS -- plus, the way you're doing it 
> assumes that the system value is in MMDDYY format, which it may not be. 
So

> your code would be shorter and more correct using CEELOCT.
> 
> Also, if you supply a feedback code (&FC) you should check it to see if 
> the API failed.  If you don't want to do any checking, pass *OMIT so 
that 
> the operating system's default error handling mechanish can kick in.
> 
> (I just posted an example very similar to yours, but uses CEELOCT)
> 
> > pgm
> > DCL &DATE *CHAR 6
> > DCL &LILDATE *CHAR 4
> > DCL &FC *CHAR 12
> > dcl &monthyear *char 7
> > /* get system date */
> > rtvsysval qdate &date
> > /* change to first of month */
> > CHGVAR &DATE (%SST(&DATE 1 2) *CAT '01' *CAT %SST(&DATE 5 2))
> > /* get "lillian" date number */
> > CALLprc CEEDAYS (&DATE 'MMDDYY' &lildate &fc)
> > /* subtract 1 day to get last day of previous month */
> > CHGVAR (%BIN(&LILDATE)) ((%BIN(&LILDATE) - 1))
> > /* get 3-char month name + 4-digit year */
> > CALLprc CEEDATE (&lildate  'MMMYYYY'  &monthyear  &fc)
> > endpgm
>