SUMMARY

What system authority is required for a user profile to run the STRDG8SVR command successfully? How/why does STRDG8SVR fail?

SYMPTOMS

When a user attempts to execute the STRDG8SVR command, an error is logged indicating that the job could not be submitted.

CAUSE

The user does not have adequte permissions.

RESOLUTION

The STRDG8SVR command runs a simple program that invokes the SBMJOB command to start the DataGate server.  The command is very similar to the following command:

USER(DG8SVCPRF) OUTQ(*USRPRF) SYSLIBL(*SYSVAL) +

CURLIB(*USRPRF) INLLIBL(*JOBD) HOLD(*NO) MSGQ(*NONE)

In the above command, <instlib> is replaced with the name of the library into which DataGate was installed.  Thus, the user profile executing STRDG8SVR must have authority to run SBMJOB.  For the command to succeed, the user profile running STRDG8SVR must also have the following permissions:

     ·        *USE authority to the DG8SVCPRF user profile.   

·        *USE authority to the DG8SVC command.

·        *USE authority to the DG8_SVC job queue.

·        *EXECUTE authority to the installation library containing DG8SVC and DG8_SVC.

·        *READ authority to the job description assigned by the SBMJOB command default for the JOBD parameter (this is usually, but not always, the job description associated with the DG8SVCPRF user profile).

·        *EXECUTE authority to the library containing the job description assigned by the SBMJOB command default for the JOBD parameter (this is usually, but not always, the job description associated with the DG8SVCPRF user profile).

·        *USE authority to the sort sequence table assigned by the SBMJOB command default for the SRTSEQ parameter (this is usually, but not always, the sort sequence table associated with the current job).

·        *EXECUTE authority to the library containing the sort sequence table assigned by the SBMJOB command default for the SRTSEQ parameter (this is usually, but not always, the sort sequence table associated with the current job).

For the DataGate server to be successfully started by the above SBMJOB command, the DG8SVCPRF user profile must also have the following permissions:

 

*USE authority to the job description assigned by the SBMJOB command default for the JOBD parameter (this is usually, but not always, the job description associated with the DG8SVCPRF user profile).

*READ authority to the output queue associated with DG8SVCPRF.

*USE authority to all auxiliary storage pool (ASP) device descriptions in the initial ASP group assigned by the SBMJOB command default for the INLASPGRP parameter (this is usually, but not always, the initial ASP group of the current job).

*USE authority to the current library associated with DG8SVCPRF.

*USE authority to all the libraries specified in the initial library list of the job description assigned by the SBMJOB command default for the JOBD parameter (this is usually, but not always, the job description associated with the DG8SVCPRF user profile).

Generally, the installation program will set permissions and grant authorities on the objects it installs to DataGate requirements (DG8SVCPRF, DG8SVC, DG8_SVC, et.al.).  If SBMJOB fails, a warning screen is shown with the full parameter list detail of the SBMJOB command used.

  MORE INFORMATION

Note also that the program invoked by STRDG8SVR checks for the existence of a marker left by a running DataGate server, in the form of a data area object.  By design, DataGate creates, grants *PUBLIC authority to, and exclusively locks a data area named DG8SVCPID in the installation library when it is started.  The STRDG8SVR program checks for the existence of this data area before issuing the above SBMJOB command.  If the data area exists but the user profile does not have authority to use it (i.e., a non-DataGate job has changed its permissions), STRDG8SVR may fail to start the server and issue the “DataGate server already started” warning screen