USS file corruptions or contentions when multiple AS (address space) are generated for the server. Customer experienced event file corruption and contention when the Tivoli Workload Scheduler server generated processes with parent process id (ppid) equal to 1 (for instance, Batchman process). The reason for this problem was the cancellation of the server started task when multiple address spaces had been generated; only one address space must be generated for all the server tasks/processes/threads. ­ PTF PK01415 offers the following solution. Avoiding USS file corruptions and contentions generated by multiple AS for the server. To avoid the generation of multiple address spaces, the following actions are performed: 1) Rework of the environmental variables; in particular the _BPX_SHAREAS variable is now always set to YES for all the processes and threads. 2) Batchman, mailman, and writers processes have the same PGID of the netman process. Wrong definitions of server and Daily planning batch job users and groups. Wrong definitions of RACF users and groups, even concerning user IDs not related to the end-to-end server, can cause errors in the Server or Daily Plan batch processing that sometimes does not have a direct relationship with the original error on the users/groups. ­ PTF PK01415 resolution checks on users and groups definitions in the RACF database have been introduced: The server, at startup and every five minutes, checks: · · · · · User assigned to the server UID of this user All users with UID equal to the user assigned to the server Group for every user found GID for every group Every user or group that does not have an OMVS segment assigned is reported in EQQMLOG with an error message. Error messages are issued only once, even if the related problem has not been solved. When the problem is solved, a new message is issued to the EQQMLOG. If there is an RACF access error, the problem is reported with a warning message in EQQMLOG. ­ PTF PK01415. Daily Plan batch, at startup, makes the same checks as the server, but only once. If the user starting Daily Plan batch has no UID or the default group has no GID, Daily Plan batch is stopped and it ends with RC=12. If there are users with the same UID of user starting Daily Plan batch, and one of them has a default group with no GID defined, Daily Plan batch is stopped; Daily Plan batch such as current plan extension, replan, and trial return RC=12, while Symphony renew returns RC=8. Appendix A. Version 8.2 PTFs and a Version 8.3 preview 669