WebSphere Extended Deployment Compute Grid, Version 6.1.1
             Operating Systems: z/OS


This topic applies only on the z/OS operating system.

Enabling native WSGrid security in the z/OS environment

Access control is controlled entirely through MQ queue security.

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.

JCL usage

//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 …

Properties

Native WSGrid introduces an alternate set of required and optional control properties. The following are required, shown with example values:

  • timeout=5000
  • submit-timeout=30000
  • debug=false
where:
  • timeout specifies amount of time in milliseconds for WSGRID to wait for next output message from job scheduler. WSGRID performs a health check on the job scheduler every time a message is received, or this timeout expires. After the health check, it continues listening.
  • submit-timeout specifies the amount of time in milliseconds WSGRID waits for an initial response from the job scheduler. If this timeout expires, WSGRID concludes the job scheduler is not up and exits with an error message and RC=4084 (-16).

Common problems

  • Error in proxy job joblog:
    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 in scheduler joblog or proxy joblog:
    ERROR: ImqQueue::open ended with reason code 2042
    To resolve, ensure that the input and output queues are defined with SHARE attribute.



Related information
Running native WSGrid in the z/OS environment
Integrating Compute Grid features in z/OS operating systems
Concept topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 1:38:02 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp?topic=/com.ibm.websphere.gridmgr.doc/info/scheduler/czoscgsecurity.html