GJJ904W SVA BUFFER FILLED LOGGING STOPPED
search cancel

GJJ904W SVA BUFFER FILLED LOGGING STOPPED

book

Article ID: 41847

calendar_today

Updated On:

Products

FAQS - Automated Systems Operation

Issue/Introduction

GJJ904W SVA BUFFER FILLED LOGGING STOPPED

How to eliminate this message without IPL the system?

 

Resolution

 If you see this message after every job runs, recycle PCS and check the console log for

 GJJ933I PCSLOG ALREADY ACTIVE  

If you see this message, FAQS/PCS is thinking PCLOG is active when it is not active.

 

Message  "GJJ904W SVA BUFFER FILLED LOGGING STOPPED" can happen if PCSLOG abends (perhaps partition canceled).

To restart PCSLOG, one of the following can be done:                                                                           

1- IPL the z/VSE System

or 

2- If FAQS/ASO is installed, on the FAQS console, issue DSPLY SVA,P=$JOBACCT+6C  

The result should be 00nn, where nn can be any value;

if so, change nn to 00   

or

3- If FAQS/ASO is not installed, if such an error did happen, it would be necessary to alter storage to clear that task id,

ASO being one of the easiest ways to do this, but there are other methods as well. 

For instance, run a job that would use the LISTDIR SDL command in LIBR:

// EXEC LIBR
LD SDL PHASE=$JOBACCT
/*

 


To receive the location of the phase: 

      M E M B E R    ORIGIN SVA/MOVE  LOADED  PHASE  ADDRESS  ENTRY POINT 
   NAME     TYPE   SYSLIB   MODE   INTO SVA SIZE   IN SVA   IN SVA
    ------------------------------------------------------------------- 
   $$JOBACCT PHASE    YES     24       24   013419  0019D568 0019D568 

Use the ALTER command via AR (19D568+6C):

ALTER 0,19D5D4

AR 0015 1I42D ADDRESS WITHIN SUPERVISOR OR SVA 

AR 0015 OLD DATA: 01F30025 0342B000 00005000 035B4D78   *.3........&..$(.* 

AR 0015 ENTER HEX DATA (1-16 BYTES) 

 

15 0000

                  

 

 

 

 

 

 

Additional Information

This message is issued by JCLACCT.  JCLACCT gathers accounting data and writes records to a buffer in the SVA.  PCSLOG reads these records and writes them to the PCS Account File.  If JCLACCT writes records faster than PCSLOG can read them the buffer will fill up.

No data is lost and when PCSLOG has processed the backlog, normal processing continues.           

If you see this message during a busy time once or twice, it may be ignored.