Top Secret TSS0317E vs TSS0318E Messages

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

- When a dataset is not already owned, when trying to permit it, for example: 

TSS PER(acid) DSN(xxxxx.) ACC(ALL) 

the following message is issued: 

TSS0317E DATASET/PREFIX NOT FOUND IN SECURITY FILE 
TSS0301I PERMIT FUNCTION FAILED, RETURN CODE = 8 

- When a dataset is owned at a longer resource name, when trying to permit it, for example, DSN(ABC.XYZ) is already owned: 

TSS PER(acid) DATASET(ABC.) ACC(ALL) 

the following message is issued: 

TSS0318E RESOURCE NOT FOUND IN SECURITY FILE 
TSS0301I PERMIT FUNCTION FAILED, RETURN CODE = 8

Environment

Release:
Component: TSSMVS

Resolution

This is working as designed:

- TSS0317E is issued when the resource is not owned. To own the resource, issue:

TSS ADD(dept) resclass(resname)

where:
'dept' is the department ACID to own the resource.
'resclass' is the resource class (ie DSN)
'resname' is the resource name (ie SYS1. to own DSN(SYS1.) ).

- TSS0318E is issued when the resource is owned but the permit name is shorter than the owned name (name specified on the ADD command). To own the shorter resource name:

TSS ADD(dept) resclass(shortres) UNDERCUT

where:
'dept' is the department ACID to own the resource.
'resclass' is the resource class (ie DSN)
'shortres' is the shorter resource name (ie if trying to permit DSN(abc.), but the ownership is DSN(abc.def), the shorter resource name would be DSN(abc.) ).

Additional Information