After creating a script and defining a token, we are finding that when we run the script the next day we are getting a PTE00117 Token Not Found. Why?

Document ID : KB000047044
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

After creating a script and defining a token, we are finding that when we run the script the next day we are getting a PTE00117 Token Not Found.  Why?

 

Answer:

One reason for a PTE00117 message is if the user's profile data set was allocated on a temporary volume and was being deleted every night.

The resolution is to move the profile to a permanent volume.  This can be done with IEHMOVE, CA FileMaster Plus, or just by renaming their profile, creating a new data set on a permanent volume and copying it.