GSACCNT - range archive history file
search cancel

GSACCNT - range archive history file

book

Article ID: 106774

calendar_today

Updated On:

Products

FAQS - Automated Systems Operation

Issue/Introduction

 This job runs every Saturday:

// JOB XS02R11
// EXEC GSACCNT,SIZE=(GSACCNT,100K) ACTION SORTX,SORTWK=5 EVTSUM MERGE IN=NONE,OUT=NONE,LOG=YES /*
// TLBL AUDITHI,'XB.LACCOUNT,S:004'
// TLBL AUDITHO,'XB.LACCOUNT,S:005'
// DLBL AUDITW,'GSACCNT.WORK',0,SD // EXTENT SYS006,ESA301,,,18318,1647
// ASSGN SYS006,DISK,VOL=ESA301,SHR // EXEC TDYNASN ASSGN AUDITHI,SYS004,INPUT ASSGN AUDITHO,SYS005,OUTPUT /*
// EXEC GSACCNT,SIZE=AUTO MERGE IN=SYS004,OUT=SYS005,RESET=MONTHLY /* /&

Problem is archive history file 'XB.LACCOUNT' contains information from many years now.

I was asked to create an archive history file containing information from 2018/01/01 on.
From my understanding: - EVTSUM RANGE parameter applies to PCSEVNTS.sum file - MERGE RESET parameter applies to LACACCNT.CTL file

Is there a way to create an archive history file containing information from 2018/01/01 on? 

Environment

Release:
Component: FAQPCS

Resolution

There is currently no way to accomplish this by date range like you’re wanting to do.
I found history of another FAQS customer who was interested a few years back in an enhancement to GSDSN to be able to read input by date range and write to output.
They too, wanted to be able to do this by date, although, the enhancement was never pursued.

If this is something you’re interested in, I encourage you to submit it as an IDEA (enhancement request) to CA’s Mainframe Communities.

Working with what we have now, one suggestion is to start a new tape/ a new version of the file, every 6 months or every year…start a new archive dataset.
Another suggestion is to reduce the number of DSNs.