Internal reader jobs using wrong ACID after applying TSS PTFs
Article ID: 107694
Top SecretTop Secret - LDAP
After applying the latest Top Secret 16.0 maintenance to my test LPAR, jobs submitted to the internal reader are failing. They are using the ID of the submitting job - CICS or CA Dispatch - instead of the user's ACID. For example on test: //PNAPDP JOB (JOB0F00T),'NEW PRINT', // CLASS=H,MSGCLASS=X,REGION=8M Prod LPAR is correct: //PNAPDP JOB (JOB0F00T),'NEW PRINT', // CLASS=H,MSGCLASS=X,REGION=8M, // USER=USER002 I copied the TSS security file from prod to test yesterday and bounced TSS. Dispatch archive is using the CASDISP ID on test, while on prod it is using CASDIS (without the "P").
Release: Component: TSSMVS
AFTER SO04024 NOVERIFY DOES NOT INSERT USER= ON JOBCARD
SO04627 PROBLEM DESCRIPTION: After fix SO04024, JES(NOVERIFY) does not insert USER= on the jobcard. Also, CICS will fail to insert USER= on jobs submitted thru either the TD QUEUE or SpoolWrite commands regardless of the (VERIFY/NOVERIFY) JES control option setting. As a result submitted jobs will run under the wrong ACID.
SYMPTOMS: The job fails indicating the user is not authorized.