MVSFORUMS.com

shekar123 · Posted: Thu Nov 03, 2005 5:23 pm Post subject: date validation in COBOL

Bithead,

I have only one occurance of CEEDAYS in my load module DVLDPGM when i opened in Browse mode.Thanks.
_________________
Shekar
Grow Technically

kolusu · Posted: Thu Nov 03, 2005 5:26 pm Post subject:

Shekhar123,

Run the following job as is and see if you get the right output.

shekar123 · Posted: Thu Nov 03, 2005 5:55 pm Post subject: date validation in COBOL

Kolusu,

I tried running the JCL as is but still the desired output is not coming.

Code:

********************************* TOP OF DATA **********************************
THE DATE IS NOT A VALID DATE
******************************** BOTTOM OF DATA ********************************

_________________
Shekar
Grow Technically

kolusu · Posted: Thu Nov 03, 2005 6:05 pm Post subject:

shekar123,

Did you make any changes in the JCL. If so list them .

Can you change the IF to the following

shekar123 · Posted: Thu Nov 03, 2005 6:29 pm Post subject: date validation in COBOL

Kolusu,

I made the changes and here is what i have.FYI ,I have seen the PDS CEE.SCEELKED in which i do not find any member by name LOADER.

My JCL
------

Code:

//TECH022R JOB TEST#,'SR',CLASS=A,NOTIFY=&SYSUID,MSGLEVEL=(1,1)
//STEP0100 EXEC PGM=IGYCRCTL
//STEPLIB DD DSN=TECH022.SIGYCOMP,
// DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT5 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT6 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSUT7 DD UNIT=SYSDA,SPACE=(CYL,(10,2))
//SYSLIN DD DSN=&&LOADSET,
// DISP=(MOD,PASS),
// UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE)
//SYSLIB DD DSN=CEE.SCEELKED,DISP=SHR
//SYSIN DD *
IDENTIFICATION DIVISION.
PROGRAM-ID. SAMPLE.
DATE-COMPILED.
ENVIRONMENT DIVISION.
DATA DIVISION.
WORKING-STORAGE SECTION.

01 WS-INP-DATE PIC 9(08) VALUE 20051103.
01 WS-OUTPUT PIC S9(9) COMP.
01 WS-FORMAT PIC X(08).
01 WS-FC-CODE.
05 FC-SEVERITY PIC S9(4) COMP.
05 FC-MESSAGE PIC S9(4) COMP.
05 FILLER PIC X(08).

PROCEDURE DIVISION.

MOVE 'YYYYMMDD' TO WS-FORMAT

CALL 'CEEDAYS' USING
WS-INP-DATE,
WS-FORMAT,
WS-OUTPUT,
WS-FC-CODE
IF FC-SEVERITY = 00
DISPLAY 'THE DATE IS A VALID DATE'
ELSE
DISPLAY 'FC SEVERITY: ' FC-SEVERITY
DISPLAY 'FC MESSAGE : ' FC-MESSAGE
DISPLAY 'THE DATE IS NOT A VALID DATE'
END-IF
GOBACK.
/*
//STEP0200 EXEC PGM=LOADER,
// PARM=('LIST,LET,XREF,DCBS,'),
// COND=(5,LT,STEP0100)
//SYSLIB DD DSN=CEE.SCEELKED,
// DISP=SHR
//SYSLIN DD DSNAME=*.STEP0100.SYSLIN,DISP=(OLD,DELETE)
//SYSLOUT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*

OUTPUT
------

Code:

********************************* TOP OF DATA **********************************
FC SEVERITY: 0003
FC MESSAGE : 2518
THE DATE IS NOT A VALID DATE
******************************** BOTTOM OF DATA ********************************

_________________
Shekar
Grow Technically

Grant · Posted: Mon Mar 06, 2006 5:54 pm Post subject: CEEDAYS

I have found that you will get unpredictable results if you do not pass the first two parameters to CEEDAYS as varying length character strings. Using fixed length strings will work most of the time, but every now and again it seems to spit the dummy.
Refer to the Language Reference Manual Programming Reference for more info...

Jaya · Posted: Tue Mar 07, 2006 3:58 am Post subject:

Yes Grant! it works after changing the input string and format information to variable length fields.

I ran the following code to test them.