Updating Execution-Time Override Parameters for MICF inquiries and jobstreams

Products

• MICS Resource Management

Issue/Introduction

When defining MICF inquiries, there is an option to specify a 'Y' or 'N' for the 'Allow Run-Time Override of Database', 'and/or Cycle(s)'  parameters.   These parameters apply to the MICS File Selection inquiry step(s).   When set to 'Y', you can hard-code a specific database unit ID and Cycle # that will apply to the inquiry.  Once the inquiry is saved, either by PF3'ing or issuing the 'SAVE' primary command, the values specified take effect.
If the inquiry is edited again and the hard-coded database unit ID and cycle # is changed followed by a SAVE operation, execution of the inquiry again will still show the initial database unit ID and cycle #.  It is not updated with the most recent values specified.    Execution of the inquiry, either as PRIVATE, SHARED, or as part of a reporting job stream will still show the residual (previous) unit ID and cycle # in the execution prompt.  

Environment

Release : 14.2

Component : CA MICS BASE SET

Resolution

When a MICF inquiry is saved, either by PF3'ing or issuing the 'SAVE' primary command, the user.TABLES(S@iiiiiii) data-set is added/updated with the default database unit ID and cycle# specified.   
Editing the inquiry again and changing the hard-coded database unit ID and cycle # followed by a Save will not update these values.   As a result, execution of the inquiry will still show the residual (previous) unit ID and cycle # in the execution prompt.
In order to reset the values stored in user.TABLES(S@iiiiiii), edit the inquiry and set the the 'Allow Run-Time Override of Database', 'and/or Cycle(s)'  parameters to 'N' followed by PF3'ing to save or issuing the SAVE primary command.    This deletes the rows from user.TABLES(S@iiiiiii) that contain the initially specified unit ID and cycle #.
Next, edit the inquiry again and set the Overrides to 'Y' and specify the desired unit ID and cycle values followed by another SAVE.  This will add new rows to the (S@iiiiiii) inquiry in user.TABLES with the current specification.     
Before promoting any inquiries from PRIVATE to SHARED and adding them to a job-stream, follow this process to ensure that the desired unit ID and cycle # is specified. Once the desired values are set in user.TABLES(S@iiiiiii), the promotion to shared and production reporting job-stream will carry over what was set.