Topics

1

z/OS Server / Security Exit for Document Permissions

« on: May 09, 2022, 09:29:16 PM »

I am trying to understand how document level permission exit does work with ESM. I see for Cabinet, Folder & AG we have associated RACF class defined in ESM and the RACROUTE call populates the corresponding resource name to be protected and get it validated against the ESM. But for documents, the manual does not state any resource class to be defined. Do we need to define any resource class for document level access? If it is not required then how CMOD understands which all documents the user has access. The IBM supplied sample ARSUSECZ module, it seems it allows access to all the documents. Any inputs on this are appreciated. Thank you !!

2

Report Indexing / ACIF fails with - Triggers Satisfied, but indexes were incomplete at end-of-file

« on: May 06, 2022, 07:09:06 AM »

Hello Everyone,

I have an input file where some of the PAGEs don't have required number of lines from where FIELD should be getting collected. And ACIF fails with APK460S while loading as it does not see the required line number as defined in indexer parameter in that page. We want the file still to be loaded even if we don't have the index values collected (might be with default space value) for those pages. I tried with a DEFAULT parameter but no luck. Without fixing the input file or input exit, is there any work-around we can do to get this file loaded - any advice or suggestion would be helpful. It is CMOD on distributed side. Thank you !! 

3

z/OS Server / CMOD Retention based on GDG like versions

« on: December 24, 2020, 03:26:47 AM »

Hello Everyone,

I have a requirement where client wants to retain the report versions similar like GDG versioning. Let’s say the maximum version has been defined as 5. So when a new version will be created the oldest version will get expired keeping the number of version 5. As per my knowledge, CMOD supports retention only based on the number of days. We suggested to convert this number of versions to in days (report generation frequency * number of versions), but they have many adhoc reports without any definite frequency. Does CMOD support retention based on versions or is there any other way to achieve this functionality. Any guidance will be much appreciated. Thank you and Merry Christmas !!

 

4

z/OS Server / Loading of multiple MVS PS files into CMOD

« on: July 21, 2020, 01:41:37 AM »

Hello,

We have around 750+ different Tape datasets which need to be loaded daily in CMOD (ZOS). Initially we thought to route these datasets to SYSOUT spool with specific destination/writer so that the A and AG can be determined by CMOD. But because of the huge size of the datasets the spool volume gets filled up which lead to reject this approach. We see that ARSLOAD has the option to load by a DDNAME (with option -s). But that can be used only for one dataset. Since there are too many datasets to be loaded, so creating individual 750 jobs will not be a good approach. Is there any option so that multiple datasets can be loaded through parm or some other techniques. Or if you can suggest any approach to load these datasets that would be appreciated. Thanks