

Preparing for Installation › Security Setup › Security Setup on the Target Systems › Authorizations and Permissions for SDS Access
Authorizations and Permissions for SDS Access
Your System Administrator must ensure these requirements for usability. The CA CSM host must retrieve and delete output under the user credentials, so read and write permission is needed.
The Software Deployment Service (SDS) and CA Common Services need read and write access permissions to use and access your target system in the following areas:
- The remote SDS uses the SMP Work Directory (SMPWKDIR) as a scratch pad. GIMUNZIP and the SDS using PROC CCISPNSV use the scratch pad. Permissions must be set to allow users the correct access for read/write/delete/execute. The owner UID/GID must be the one that allows deployment users the ability to have read/write/execute within that work directory.
Note: Only Started Task Class (STC) needs read access. The user needs read/write access.
- FTP and the landing directory are accessible by the CA CSM deployment remote services on the target system and permissions are based on the user credentials.
Note: User needs read/write access.
- The security ID associated with the CCISPNSV started task requires a valid OMVS segment. CCISPNSV attaches a task that performs the utility functions for the deployment in your security context on the target system.
- Mount point is a directory path that must have write permission and must exist on the target system. The user ID that is doing the deployment must have write permission to this directory.
The deployment user ID must have write permissions for the mount directory. The deployment user ID must have a mount that is authorized on the target system.
Note: A mount user must have UID(0) or at least have READ access to the SUPERUSER.FILESYS.MOUNT resource found in the UNIXPRIV class.
Copyright © 2014 CA.
All rights reserved.
 
|
|