Same version of Sysview (V17) with the same commands being executed on 2 different LPARs have the date format different

Products

• SYSVIEW Performance Management

Issue/Introduction

Just installed Sysview 17.0 on our z/OS 2.4 operating systems. The same version of Sysview (V17) with the same commands being executed on 2 different LPARs have the date format different.

Examples:

SYSX

//STEP1    EXEC PGM=GSVXBAT                             
//SYSPRINT DD  SYSOUT=*           
//SYSIN    DD  *                                         

COMMAND=(SET PRINTDSNAME 'PRINT.DATASET.NAME')
COMMAND=(SET PRINTDEST R974)                            
COMMAND=(MVS V 0100-01FF,ONLINE)                        
COMMAND=(WAIT 20 SECONDS)                                
COMMAND=(SPACE =)                                       
COMMAND=(PRINT FROM,1 TO 999999,MEMBER $PRTDASD)        

 

BROWSE    XXXXXXX.STORAGE.XXX.IEHLIST($PRTDASD)                                                          Line 0000000000 Col 001 132
Command ===>                                                                                                         Scroll ===> CSR 
*********************************************************** Top of Data ************************************************************
SYSVIEW 17.0 SYSX                                         DASD Free Space                                         06/30/23 08:00:29

--------------------------------------------------------------------------------------------------- Lvl 2 Row 1-36/36 Col 1-131/241

Options NORESERVPROT HEXEDIT NOTRKCALC NODATALEN NOKEYLEN NOSPLIT                                                                   

Total bytes 1.12T  Used  418G  37%  Free  725G  63%  Errors     0                                                                  

-----------------------------------------------------------------------------------------------------------------------------------

    =      =        ALL                                                                                                            

SYSB

//STEP1    EXEC PGM=GSVXBAT                             
//SYSPRINT DD  SYSOUT=*                                  
//SYSIN    DD  *                                         

COMMAND=(SET PRINTDSNAME 'XXXXXXX.STORAGE.XXX.IEHLIST')
COMMAND=(SET PRINTDEST R974)                            
COMMAND=(MVS V 0100-01FF,ONLINE)                         
COMMAND=(WAIT 20 SECONDS)                                
COMMAND=(SPACE =)                                        
COMMAND=(PRINT FROM,1 TO 999999,MEMBER $PRTDASD)         

 

BROWSE    XXXXXXX.STORAGE.XXX.IEHLIST($PRTDASD)                                                          Line 0000000000 Col 001 132 
Command ===>                                                                                                         Scroll ===> CSR  
*********************************************************** Top of Data ************************************************************
SYSVIEW 17.0 SYSB                                         DASD Free Space                                       2023/06/30 04:01:09 
--------------------------------------------------------------------------------------------------- Lvl 2 Row 1-39/39 Col 1-131/241 
Options NORESERVPROT HEXEDIT NOTRKCALC NODATALEN NOKEYLEN NOSPLIT                                                                   

Total bytes 1.22T  Used  359G  29%  Free  891G  71%  Errors     0                                                                   

----------------------------------------------------------------------------------------------------------------------------------- 
    =      =        ALL                                                                                                             

Environment

Release : 17.0

Resolution

The most plausible explanation is that the two regions were using different PROFLIBs, leading to the differences seen. In the end, the user decided to make the following change to jobs -

            COMMAND=(SET DATEF,YYYY/MM/DD,GENERAL) 

That way the same date format will be used regardless of any change to the format in future releases.