Why all logon scripts (ACLs) failed, on session startups, for a new TPX that was recently copied from a Production TPX?

Document ID:  TEC431384
Last Modified Date:  07/13/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA TPX Session Management for z/OS

Releases

  • CA TPX Session Management for z/OS:Release:5.3
  • CA TPX Session Management for z/OS:Release:5.4

Components

  • CA-TPX for OS/390:TPX
Introduction:

Auto sign-on for applications can be invoked using TPX ACL's (script).

Question:

Why are all logon scripts (ACLs) failing, on session startups, for a new TPX that was recently copied from a Production TPX?

Answer:

The new TPX did not have a valid, permanent (or temporary) LMP key for ACL/E (code NP) authorization included in the  common services (CAS9) startup.

Once a valid LMP code(NP) was added to CAS9, the new TPX was restarted, and all logon scripts ran successfully.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >