The CA manuals state that the -SCAN utility statement is a read-only function (Security adm guide). Also the user guide states that -SCAN does not enqueue the master file.
This being the case, can someone tell me if a running the -SCAN batch utility can hold any other type of operation on the master file??
If it holds up nothing then what is the need for FAIRSCAN which is a UCR written COBOL using the FAIR access routines. This program is described as below in the system services guide
"Using the File Access Interface Routines, FAIRSCAN performs data scans on any AllFusion CA-Librarian master file without preventing any other batch or online jobs from accessing the master file."
My shop has all the production code inside a library master.
The signoff jobs in production are a bunch of rexx programes that execute CA-librarian batch utility from within the rexx code itself. Now they use different options of the librarian utility for different situations. Not possible to predict.
I use the librarian batch utility to run the -SCAN statement when I want to scan the master.
The scheduling team claims that running -SCAN holds up the signoff jobs.
Now the user guide states as follows
"The utility SCAN function does not enqueue the master file."
I have not been able to have a look at the enqueue when the jobs were held up. It is not possible to simulate. I got a little suspicious of the utility scan when the FAIRSCAN was described as follows
"Using the File Access Interface Routines, FAIRSCAN performs data scans on any AllFusion CA-Librarian master file without preventing any other batch or online jobs from accessing the master file."
Questions
1) Is it possible that the utility -SCAN function holds up the master?
2) Can this be avoided by using FAIR from a COBOL code??
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Hello,
I believe you will get better replies from CA support.
They will know if this (or something close) has been reported for your release of Librarian and associated applied fixes. It may be that you need some site-specific fix that is not sent without being requested.
Also
Quote:
If it holds up nothing
is not the same as "does not enqueue the master file". There are ways to hold resources that do not require issuing an enqueue against the entire Librarian master (which is how individual modules are protected).
