Run the native WSGrid in the zOS environment.
Access control is controlled entirely through MQ queue security.
The authenticated user ID of the environment that invokes WSGRID is propagated to the WCG job scheduler. The resultant WCG job runs using that user ID. This user ID must also have sufficient WebSphere privileges to submit WCG jobs, that is, lradmin or lrsubmitter role. For example, if JCL job WSGRID1 is submitted to run under technical user ID TECH1, the resultant WCG also runs under user ID TECH1. User ID TECH1 must be permitted to get and put to and from the MQ input and output queues used by WSGRID.
//WSGRID1 JOB (),MSGCLASS=H,CLASS=A //************************************************ //RUN EXEC PGM=WSGRID //STEPLIB DD DSN=USER26.CG.LOAD,DISP=SHR // DD DSN=MQSERIES.V6R0M0.SCSQLOAD,DISP=SHR // DD DSN=MQSERIES.V6R0M0.SCSQAUTH,DISP=SHR //SYSPRINT DD SYSOUT=* //************************************************ //WGCNTL DD … //************************************************ //WGJOB DD … //************************************************ //WGSUBS DD … //************************************************ //WGRSTRT DD …
Native WSGrid introduces an alternate set of required and optional control properties. The following are required, shown with example values:
ERROR:: ImqQueueManager:connect failed with reason code 2025.To resolve, considering changing the parameter IDBACK to a higher value. This parameter value is set in the start up module of the QMGR
ERROR: ImqQueue::open ended with reason code 2042To resolve, ensure that the input and output queues are defined with SHARE attribute.