Execute utility - connect_cdc_sqdata - Latest

Connect CDC (SQData) Utilities

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
Latest
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Utilities
Copyright
2024
First publish date
2000
Last updated
2024-11-25
Published on
2024-11-25T15:17:45.575795
The utility can be executed on z/OS with JCL similar to sample member SQDMON included in the distribution, as in the sample below:
//*-----------------------------------------------------------------
//*    EXECUTES SQDATA DAEMON CONTROL PROGRAM - SQDMON              
//*-----------------------------------------------------------------
//*    NOTE: PARMS MUST BE ENTERED IN LOWER CASE                    
//*-----------------------------------------------------------------
//JOBLIB   DD DISP=SHR,DSN=SQDATA.V400.LOADLIB                      
//*                                                                  
//SQDMON   EXEC PGM=SQDMON                                          
//SQDPUBL  DD DSN=SQDATA.NACL.PUBLIC,DISP=SHR                        
//SQDPKEY  DD DSN=SQDATA.NACL.PRIVATE,DISP=SHR                      
//SYSOUT   DD SYSOUT=*                                              
//SQDLOG   DD SYSOUT=*                                              
//*SQDLOG8  DD DUMMY                                                  
//SQDPARMS DD *                                                    
inventory [//host_name] [-s port_num | --service=port_num]

The syntax for Open Systems and Windows are identical and can be run at the command prompt or in a script:

sqdmon inventory [//host_name] [-s port_num | --service=port_num]

sqdmon typically returns a message SQDC017I sqdmon terminated successfully. This message signifies that the request was sent sucessfully to the daemon, but does not necessarily indicate a positive outcome for that request. For instance, a stop command that returns a SQDC017I message does not mean that the agent is effectively stopped, but that agent accepted and responded to that stop command successfully. Similarly a start is successful as soon as the agent process has been successfully launched. But that process may very well have stopped immediately because of faulty arguments, for instance.