Hello,

  I found out that in case of multivolume STDOUT, only the "starting" messages are visible, all other output is gone. 

For example, simple SB application from SpringInitializr with web 

Start JCL:

//JVM      EXEC PGM=JVMLDM17,REGION=0M,PARMDD=PARMS           
//STEPLIB  DD DSN=<HLQ>.IBM.JZOS.LOADLIB,DISP=SHR             
//SYSPRINT DD SYSOUT=*,RECFM=VB,LRECL=32756                   
//PARMS    DD *,SYMBOLS=(JCLONLY)                             
/ -jar /zos-0.0.1-SNAPSHOT.jar                       
//SYSOUT   DD SYSOUT=*,RECFM=VB,LRECL=32756                   
//*STDOUT   DD SYSOUT=*,RECFM=VB,LRECL=32756                  
//STDOUT   DD  DISP=(NEW,CATLG),                              
//             RECFM=VB,LRECL=32756,                          
//             DSN=<USER>.TMP.STDOUT.SIMPLE.MULT,             
//             SPACE=(TRK,(15,75),RLSE),UNIT=(SYSDA,4)        
//*            SPACE=(TRK,(15,75),RLSE),UNIT=SYSDA            
//STDERR   DD SYSOUT=*,RECFM=VB,LRECL=32756                   
//CEEDUMP  DD SYSOUT=*                                        
//ABNLIGNR DD DUMMY                                           
//STDENV   DD *,SYMBOLS=(JCLONLY)                            
...

Output after "stop" (/P ...) is the following:

Starting ZosApplication v0.0.1-SNAPSHOT using Java 17.0.19 with PID 84018896
No active profile set, falling back to 1 default profile: "default"                     
Tomcat initialized with port 36000 (http)                                               
Starting service [Tomcat]                                                               
Starting Servlet engine: [Apache Tomcat/11.0.22]                                        
Root WebApplicationContext: initialization completed in 732 ms                          
Tomcat started on port 36000 (http) with context path '/'                               
Started ZosApplication in 1.676 seconds (process running for 2.19)                      
************************************************************************ Bottom of Data 

In case of single volume or "SYSOUT=*" there are shutdown messages:

Starting ZosApplication v0.0.1-SNAPSHOT using Java 17.0.19 with PID 50464415 
No active profile set, falling back to 1 default profile: "default"          
Tomcat initialized with port 36000 (http)                                    
Starting service [Tomcat]                                                    
Starting Servlet engine: [Apache Tomcat/11.0.22]                             
Root WebApplicationContext: initialization completed in 687 ms               
Tomcat started on port 36000 (http) with context path '/'                    
Started ZosApplication in 1.642 seconds (process running for 2.178)          
Commencing graceful shutdown. Waiting for active requests to complete        
Graceful shutdown complete                                                   
***************************** BOTTOM OF DATA **************************

Is this a limitation of JZOS or Spring boot?

Thank you.

Hi Sergey, our team is currently investigating your issue and we will get back to you soon.

Hi Sergey, 

Commencing graceful shutdown. Waiting for active requests to complete
Graceful shutdown complete

Hi Yiqun,

   In the original message, i provided link to Spring Boot initializer with Spring Web component, this application can show the problem. I'll attach it here as well, but i assume that from security standpoint, link to well-known site is better. 

You need to start it and then stop by sdsf "/P" command to produce shutdown messages.

Attachment(s)

zos.zip   14 KB 1 version

Commencing graceful shutdown. Waiting for active requests to completeGraceful shutdown complete