Changing LOGSPILL values during MUF execution
Article ID: 255875
Updated On:
Products
Issue/Introduction
I am trying to modify the LOGSPILL values without recycling the MUF.
Is it possible to do this using a console command, and if it is possible would you please provide the correct format?
Environment
Release : 15.1
Datacom/DB
Datacom/AD
Resolution
There are multiple ways to change any of the five values related to the LOGSPILL MUF Startup Option.
As you know, the LOGSPILL MUF Startup Option is defined using the syntax:
LOGSPILL a,b,c,d,e
where "a" is the only required value, and each value requires all the previous values (for example, "d" requires "c", "b", and "a").
As a refresher, here is a brief explanation of those values:
- The percentage where Datacom/DB starts issuing console messages about the Log Area becoming full (also called the threshold)
- The percentage at which point Datacom/DB forces a checkpoint before the Log Area reaches 100% full
- The percentage when the Log Area will attempt a spill to the RXX (LOGRCV YES ONLY)
- The percentage when the last transaction requested is moved to the Force Area (FXX)
- The percentage when an active request is moved to the Force Area.
Now, to change any of these values, you would issue the LOGSPILL_x console command (where x is either "A", "B", "C", "D", or "E"). For example to change the third value to 93%, you might want to issue the console command:
/F MUFNAME,LOGSPILL_C 93
These options can be changed in several ways:
- With the SQL Console command table (SQX) using DBSQLPR and the following SYSIN:
INSERT INTO SQL_CONSOLE VALUES ('MUFNAME ','LOGSPILL_C 93'); - DBUTLTY COMM Console command using the following SYSIN:
COMM OPTION=CONSOLE,OPTION2='LOGSPILL_C 93' - SYSVIEW Batch Console command using the following SYSIN:
COMMAND=(XMVS F MUFNAME,LOGSPILL_C 93) - Issuing a console command directly in the JCL (note that these COMMAND statements execute as soon as the job is started, and not in any sort of JCL Step sequence)
// COMMAND 'F MUFNAME,LOGSPILL_C 93'
Here is JCL showing these four methods, all together (you might be using different procs, but the SYSIN format/syntax is what you are interested in):
//*
// EXPORT SYMLIST=(*)
//*
// SET WAIT=15
// SET COMND1='LOGSPILL_C 31'
// SET COMND2='LOGSPILL_C 32'
// SET COMND3='LOGSPILL_C 33'
// SET COMND4='LOGSPILL_C 34'
//*
//WAIT EXEC PROC=@WAIT,SEC=&WAIT
//*
//$$$$$$@A EXEC @DBSQL,AUTH=SYSUSR,IREC=133,PRM='ROWLIMIT=999999'
//SYSIN DD *,SYMBOLS=JCLONLY
INSERT INTO SYSADM.SQL_CONSOLE
VALUES('MUFNAME ','&COMND1');
/*
//* - - - - - -C- - - - - - - - - - - - - - - - - - - - - - - - - - -7-
//WAIT EXEC PROC=@WAIT,SEC=&WAIT
//*
//$$$$$$@B EXEC @DBUTL
//SYSIN DD *,SYMBOLS=JCLONLY
COMM OPTION=CONSOLE,OPTION2='&COMND2'
/*
//* - - - - - -C- - - - - - - - - - - - - - - - - - - - - - - - - - -7-
//WAIT EXEC PROC=@WAIT,SEC=&WAIT
//*
//SVBATCH EXEC PGM=GSVXBAT,PARM='LINECNT=100,SHOWINP=YES,MENUOFF'
//SYSPRINT DD SYSOUT=*
//SYSIN DD *,SYMBOLS=JCLONLY
COMMAND=(XMVS F MUFNAME,&COMND3)
COMMAND=(END)
/*
//* - - - - - -C- - - - - - - - - - - - - - - - - - - - - - - - - - -7-
//WAIT EXEC PROC=@WAIT,SEC=&WAIT
//*
//* Note that the following will run immediately when job is active,
//* it is not true JCL that will run in sequence.
//*
// COMMAND 'F MUFNAME,LOGSPILL_C 34'
//*
Here is an excerpt of the job output:
...+....10...+....20...+....30...+....40...+....50...+....60...+....70...+
14.31.24 JOB08942 ---- THURSDAY, 08 DEC 2022 ----
14.31.24 JOB08942 F MUFNAME,LOGSPILL_C 34
14.31.24 JOB08942 TSS7000I UUUUUUU Last-Used 08 Dec 22 08:43 System=SSSS
14.31.24 JOB08942 $HASP373 UUUUUCON STARTED - INIT 80 - CLASS C
14.31.24 JOB08942 IEF403I UUUUUCON - STARTED - TIME=14.31.24
14.31.39 JOB08942 CAJR250I STEPNAME STEP PGM= CCODE EST-COST EXCPS
14.31.39 JOB08942 CAJR251I SLEEP 1 BPXBATCH 0000 $ .00 0
14.31.40 JOB08942 +MUFNAME:DB00135I - CONNECT TO MUFNAME MUFNAM
14.31.40 JOB08942 +MUFNAME:DB00101I - STARTED JOB-UUUUUCON NUMBER-81562 C
14.31.40 JOB08942 +MUFNAME:DB00136I - DISCONNECT MUFNAME MUFNAM
14.31.40 JOB08942 CAJR251I DBSQLPR 2 DBSQLPR 0000 $ .51 103
14.31.56 JOB08942 CAJR251I SLEEP 3 BPXBATCH 0000 $ .00 0
14.32.02 JOB08942 MUFNAME:DB00135I - CONNECT TO MUFNAME MUFNAM
14.32.02 JOB08942 MUFNAME:DB00101I - STARTED JOB-UUUUUCON NUMBER-81563 C
14.32.03 JOB08942 MUFNAME:DB00136I - DISCONNECT MUFNAME MUFNAM
14.32.04 JOB08942 CAJR251I $$$$$$@A 4 DBUTLTY 0000 $3.36 59
14.32.24 JOB08942 CAJR251I SLEEP 5 BPXBATCH 0000 $ .00
14.32.28 JOB08942 GSVX014I (BATCH.UUUUUUU) UUUUUUU entered command XMVS F MUFNAME,LOGSPILL_C 33
14.32.28 JOB08942 IEA630I OPERATOR GSVX0001 NOW ACTIVE, SYSTEM=SSSS
14.33.18 JOB08942 IEA631I OPERATOR GSVX0001 NOW INACTIVE, SYSTEM=SSSS
14.33.19 JOB08942 CAJR251I SVBATCH 6 GSVXBAT 0000 $3.55 57
14.33.34 JOB08942 CAJR251I SLEEP 7 BPXBATCH 0000 $ .00
14.33.34 JOB08942 IEF404I UUUUUCON - ENDED - TIME=14.33.34
and here is what the MUF log shows:
14.31.24 JOB07928 MUFNAME:DB01311I - LOGSPILL_C 34
14.31.24 JOB07928 MUFNAME:DB01325I - CONSOLE COMPLETE, LOGSPILL_C 34
14.31.40 JOB07928 MUFNAME:DB00133I - JOB OPEN UUUUUCON 81562 UUUUUUU JOB08942
14.31.40 JOB07928 MUFNAME:DB00608I - SQL_CONSOLE COMPLETE - LOGSPILL_C 31 UUUUUCON 81562 JOB08942-2 UUUUUUU
14.32.02 JOB07928 MUFNAME:DB00133I - JOB OPEN UUUUUCON 81563 UUUUUUU JOB08942
14.32.03 JOB07928 MUFNAME:DB00608I - DBUTLTY COMM CONSOLE COMPLETE - LOGSPILL_C 32 UUUUUCON 81563 JOB08942-4 UUUUUUU
14.32.28 JOB07928 MUFNAME:DB01311I - LOGSPILL_C 33
14.32.28 JOB07928 MUFNAME:DB01325I - CONSOLE COMPLETE, LOGSPILL_C 33
Additional Information
As always, please contact Broadcom support for Datacom if you have further questions.
***
Feedback
