Can I use OCCURS clause in the structure of the Output file

William Thompson · Posted: Tue Jun 12, 2007 4:31 pm

We could have saved a lot of time if you had started with this.....

What does your JCL look like? Please post it.

mkk157 · Active User Joined: 17 May 2006 Posts: 310

//ACS2813A JOB (MSDV,,T),'PRELIM PYMT',
// CLASS=T,MSGCLASS=T,
// NOTIFY=&SYSUID,COND=(4,LT),REGION=40M
//*
/*JOBPARM L=9999
//* LOGONID MSPRJOB
//*
//MSDVLIB JCLLIB ORDER=(MSDV.TEST.PROCLIB)
// INCLUDE MEMBER=JOBLIB
//*********************************************************************
//* *
//* PS020 - PREIMINARY PAYMENT PROCESSING (YCMX4510) *
//* *
//* ABORT-RESTART PROCEDURES *
//* 1. RESET PGEN010 TO '+0' *
//* 2. RESTART JOB IN THIS STEP *
//* *
//*********************************************************************
//PS020 EXEC PGM=IKJEFT01,COND=(0,NE)
//***
//*** INPUT FILES
//***
//C4501SA DD DSN=MSDV.TEST.YCMX4510.INPUT2,
// DISP=SHR /* SORTED PAID/DENY CLMS
//C4501SB DD DSN=MSDV.TEST.YCMX4510.INPUT2,
// DISP=SHR /* SORTED PAID/DENY CLMS
//***
//*** OUTPUT FILES
//***
//*
//C4511SD DD DSN=MSDV.TEST.YCMX4510.OUTPUT.BACKUP,
// DISP=(MOD,KEEP,KEEP) /* BACKUP REPORT
//***
//*** SYSTEM FILES
//***
//SYSTSIN DD DSN=MSDV.TEST.SYSIN(PROG4510),DISP=SHR
//*
//PROCSMRY DD SYSOUT=*
//SYSTSPRT DD SYSOUT=* /* SYSTEM SYSTSPRT
//SYSOUT DD SYSOUT=* /* SYSTEM OUTPUT
//SYSPRINT DD SYSOUT=* /* SYSTEM PRINT
//SYSDBOUT DD SYSOUT=* /* SYSTEM SYSDBOUT
//SYSUDUMP DD SYSOUT=* /* SYSTEM DUMP
//SYSABOUT DD SYSOUT=* /* SYSTEM SYSABOUT
//

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi William,

This is my JCL.

William Thompson · Posted: Tue Jun 12, 2007 4:38 pm

Access mode defaults to sequential.
With sequential, a write is not permitted for a file opened I-O.
Look at Table 47. Permissible statements for sequential files

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Thanks William,

I will modify the code and then i will let u know the status.

William Thompson · Posted: Tue Jun 12, 2007 4:48 pm

Why I-O? It appears to be just an output file......

mkk157 · Active User Joined: 17 May 2006 Posts: 310

No William,

I am applying the Checkpoint-Restart Logic for the program. So When I am restarting the program after an abend occurs I need to read the same file and then i should continue the process.

For this purpose I make the OPEN mode as I-O.

William Thompson · Posted: Tue Jun 12, 2007 5:12 pm

I think you want:

mkk157 · Active User Joined: 17 May 2006 Posts: 310

William,

But Can I read the records in an EXTEND mode?

dick scherrer · Posted: Tue Jun 12, 2007 5:26 pm

Hello,

You might consider not doing this all in the one file. . .

William Thompson · Posted: Tue Jun 12, 2007 5:29 pm

Why do you need to read them?
Are you using the file for the restart info and backup?

Open input
read until eof
last record read is restart point
close
postion other input to restart point
open extend
write loop

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi Dick,

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi William,

for every record processed in the Input file, some data is moved to the WT-003 temporary table. This data is used to write the original report which contains the list of claim types, reimbursement amount, Number of Paid and denied claims etc... only after the successful execution of the program.

For this program I am implementing the Checkpoint - Restar Logic. For that I am taking the backup of the WT-003 temporary table in to a REPORT-BACKUP-FILE.

When an abend occurs I have a backup of the temporary table in this file. So, Whenever I restart the program I write the code to recover the data from the REPORT-BACKUP-FILE to the WT-003 temporary table.

Normally If the data is small I can use the Checkpoint-Tables using Database as in a normal process. Since the data is very large I prefer file instead of Checkpoint-tables.

mkk157 · Active User Joined: 17 May 2006 Posts: 310

William,

To find out the Restart point in the input file, I maintain the latest processed record in the Checkpoint-tables. As it is small.

William Thompson · Posted: Tue Jun 12, 2007 5:59 pm

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi William,

Ok, I find out the problem and I am very much thankful to u for spending valuable time with me.

Problem is only with the Organization and access mode. I am just changing the code.

Thanks a lot once again.

dick scherrer · Posted: Tue Jun 12, 2007 7:07 pm

Hello,

Similar to Bill, i too am a bit confused. . .

For this

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Yes Dick,

I considered all the points u mentioned here.

I am using Checkpoint-tables to get the latest processed record from the input file as the data is small, and I am using one output file to save the reimbursement amount and some other parameters of the each claim in the input file.

U raise another question?

dick scherrer · Posted: Tue Jun 12, 2007 7:41 pm

Hello,

Many of the places i've supported restart from the beginning for jobs that do more than a million updates - the rationale is that if no checkpointing was done, the automatic rollback could be finished before the restart was ready to run (depending on why the process abended or was canceled). If you have 1000 or so records, i'd probably leave out the complexity of a restart process. 1000 updates should run very quickly - a matter of several seconds.

If there are questions, please let us know.

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi dick,

I agree with ur words. But Still I have a small doubt? How can I know Whether to restart from the beginning or from the abeneded record. U said this decision depends on the readon for abend.

Can I put an If condition based on the number of records in the input file like.

If wk-000-num-input-records > 100000

perform S900-000-units of recovery.

End-if.

dick scherrer · Posted: Tue Jun 12, 2007 9:54 pm

Hello,

If you restart from the beginning, there will be no restart logic. All will be much simpler.