Previous Topic: Remote System Deployment Security RequirementsNext Topic: Remote Deployment Service USS Considerations


Deployments with USS Parts and SUPERUSER Authority

If you create a deployment to a target system with USS parts and your UID has SUPERUSER authority, GIMUNZIP performs in a different manner than it does for non-SUPERUSER authority.

Note: CA CSM creates the Software Deployment Service (SDS) on the target system with the credentials that you define in CA CSM.

GIMUNZIP with SUPERUSER authority

When your UID has SUPERUSER authority, GIMUNZIP runs as the ROOT user. All directories that GIMUNZIP creates as ROOT, have the ROOT UID/GID .

The deployment USS parts (Owner and Permission) can be different from your expectations. Review the USS items that are created on the directory level. If necessary, switch to SUPERUSER mode to access the results of the USS parts on the target system. Use the deployed product documentation and your organization guidelines and standards to reset owner UID/GID and permissions as necessary.

GIMUNZIP without SUPERUSER authority

GIMUNZIP always attempts to switch to ROOT. If it cannot switch, it issues an information message to SMPOUT and continues to operate with your UID/GID.