Checking the message log (EQQMLOG)

After the controller has been started, ensure that the following messages appear in the message log (this example shows messages for an SNA connection: 
02/07 12.11.39 EQQZ015I INIT STATEMENT: RCLOPTS  CLNJOBPX(EQQCL)
02/07 12.11.39 EQQZ015I INIT STATEMENT:          DSTDEST(TWSFDEST)
02/07 12.11.43 EQQPS01I PRE SUBMITTER TASK INITIALIZATION COMPLETE
02/07 12.11.46 EQQFSF1I DATA FILE EQQSDF01 INITIALIZATION COMPLETED 
02/07 12.11.46 EQQFSF1I DATA FILE EQQSDF02 INITIALIZATION COMPLETED 
02/07 12.11.46 EQQFSF1I DATA FILE EQQSDF03 INITIALIZATION COMPLETED 
02/07 12.11.46 EQQFSI1I SECONDARY KEY FILE INITIALIZATION COMPLETED 
02/07 12.11.46 EQQFSD5I SYSOUT DATABASE INITIALIZATION COMPLETE     
02/07 12.11.46 EQQFL01I JOBLOG FETCH TASK INITIALIZATION COMPLETE   
02/07 12.11.46 EQQFSD1I SYSOUT DATABASE ERROR HANDLER TASK STARTED  
02/07 12.11.46 EQQFV36I SESSION I9PC33A3-I9PC33Z3 ESTABLISHED
Note:
  1. There should be an EQQFSF1I message for each EQQSDFxx file specified in the startup procedure.
  2. There should be an EQQFV36I message for each SNA connection.
  3. Verify that the DSTDEST for message EQQZ015I matches the SYSDEST in the Data Store message log.
After the server has been started, ensure that the following messages appear in the message log: 
02/07 20.16.10 EQQZ015I INIT STATEMENT:         SYSDEST(TWSFDEST)
02/07 20.16.16 EQQFSK1I PRIMARY KEY FILE INITIALIZATION COMPLETED       
02/07 20.16.16 EQQFCM2I Data Store COMMAND TASK IS BEING STARTED        
02/07 20.16.16 EQQFCC1I Data Store COMMUNICATION TASK INITIALIZATION COMPLETED
02/07 20.16.16 EQQFV01I FN APPLICATION STARTED                           
02/07 20.16.16 EQQFV24I ACB SUCCESSFULLY OPENED                          
02/07 20.16.16 EQQFSF1I DATA FILE EQQSDF01 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFV36I SESSION I9PC33Z3-I9PC33A3 ESTABLISHED            
02/07 20.16.16 EQQFSF1I DATA FILE EQQSDF02 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSF1I DATA FILE EQQSDF03 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSF1I DATA FILE EQQUDF01 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSF1I DATA FILE EQQUDF02 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSF1I DATA FILE EQQUDF03 INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSI1I SECONDARY KEY FILE INITIALIZATION COMPLETED      
02/07 20.16.16 EQQFSD5I SYSOUT DATABASE INITIALIZATION COMPLETE          
02/07 20.16.16 EQQFSD1I SYSOUT DATABASE ERROR HANDLER TASK STARTED       
02/07 20.16.16 EQQFCU1I CLEAN UP TASK STARTED                            
02/07 20.16.16 EQQFSW1I Data Store WRITER TASK INITIALIZATION COMPLETED  
02/07 20.16.16 EQQFSW1I Data Store WRITER TASK INITIALIZATION COMPLETED  
02/07 20.16.16 EQQFSW1I Data Store WRITER TASK INITIALIZATION COMPLETED  
02/07 20.16.16 EQQFJK3I Data Store JESQUEUE TASK INITIALIZATION COMPLETED
02/07 20.16.21 EQQFSR1I Data Store READER TASK INITIALIZATION COMPLETED
Note:
  1. There should be an EQQFSF1I message for each EQQSDFxx file specified in the startup procedure.
  2. Verify that the SYSDEST for message EQQZ015I matches the DSTDEST in the controller message log.
  3. There should be an EQQFSW1I message for every writer task.
  4. There should be an EQQFCC1I message to indicate that the communication completed successfully.