ORGACIDSIZE secfile parameter

Products

• Cleanup
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Top Secret
• Top Secret - LDAP
• Top Secret - VSE

Issue/Introduction

Description:

Setting ORGACIDSIZE secfile parameter to support larger owning department acids.

Solution:

In order to benefit of the big department acid you have to have RO43262 on.

Then, you have to allocate a new secfile with the following statement added to the CAKOJCL0(SECPARMS):

ORGACIDSIZE=1024 <----NEW SIZE FOR DEPT ACID

and run a TSSXTEND to copy old secfile to the new one, and just follow your procedure already in place.

If you deploy in a CPF environment where some files may not have been reallocated for 1024 support yet.

If there is a huge update that makes a "big" acid department to go beyond 512k and this update is being propagated it will fail on all nodes where big acid is not implemented yet, when going beyond the 512k boundary.

If t the change is planned to be complete before there is a real need to go beyond 512K then there will be no issue.

Environment

Release:
Component: AWAGNT