2. MICF Options › 2.1 User Profile Parameters
2.1 User Profile Parameters
User profile parameters are general parameters that apply to
overall MICF operation and include the following:
o Parameters to control translation of panel input to
uppercase for both title/label-type fields and value-
type fields.
o The default database ID and file cycles specification
for execution time overrides.
o An option to allow access to CA MICS test database
units.
o The default inquiry execution mode (foreground or batch).
o The default job statement for batch jobs submitted
through MICF and the default region size for SAS
execution in batch mode.
o Default SYSOUT data set allocation parameters for MICF
printed output.
o Parameters to control display of the inquiry save
confirmation panel, the execution mode specification
panel, the execution options panel, and the direct
inquiry processing specification panel. If these panels
are not displayed, default specifications are assumed.
o The default inquiry function selection display. Inquiry
functions can be selected through a hierarchical menu
tree or through a scrollable selection menu.
The user profile parameters are as follows:
Batch Execution - Display generated job stream before
submitting jobs (YES/NO)?
Specify YES, or Y, to display the generated inquiry job
stream in edit mode before submitting this job stream for
execution. This gives you the opportunity to alter the
generated batch job stream before the inquiry is
executed. You can also use the ISPF Edit CREATE/REPLACE
commands to save a copy of the generated batch job
stream.
Specify NO, or N, to bypass display of the generated job
stream.
This parameter applies only to inquiries executed in
batch mode.
Browse SAS log after color graphics replay and utility SAS
executions (YES/NO)?
Specify YES, or Y, to display the SAS log in browse mode
following color graphics replay, copy private color
graphics to shared inquiry output catalog, and other SAS
utility processing. This gives you the opportunity to
review the generated utility SAS statements and examine
any error or warning conditions. This option is
especially helpful when you are using an unfamiliar color
graphics device.
Specify NO, or N, to bypass display of the SAS log.
Caps. - Translate ALL panel entry "title/label" fields to
uppercase (YES/NO)?
Specify YES, or Y, to translate specifications in data
entry fields for title and label-type information to
uppercase characters.
Note: This might be necessary if your data center does
not support upper/lowercase printing and does not have
automatic JES translation.
Specify NO, or N, to allow upper/lowercase title and
label information.
Caps. - Translate ALL panel entry "value" fields to uppercase
(YES/NO)?
Specify YES, or Y, to translate specifications entered in
value-type data entry fields to uppercase characters.
Examples of value-type data entry fields are data entry
fields on the Execution-Time Parameters panel, the Value
column of the General Data Selection panel, and the
Element Derivation field of the Data Element Derivation
panel. Most character data elements in the CA MICS
database contain only uppercase characters and will not
match value fields containing lowercase characters (that
is, 'PROD' does not equal 'prod'). Specify YES to
prevent these kinds of comparison failures.
Note: You will NOT be able to specify lowercase
characters in a value-type data entry field.
Specify NO, or N, to allow upper/lowercase value fields.
Remember to specify values in uppercase when referring
to CA MICS database element values.
Color Graphics User - Do you normally use a color graphics
device (YES/NO)?
Specify YES, or Y, if you normally use a color graphics
terminal to review saved MICF inquiry outputs.
Note: MICF will NOT automatically select the color
graphics replay option unless you specify YES for this
parameter.
Specify NO, or N, if you normally do NOT use a color
graphics terminal to review saved MICF inquiry outputs.
Confirm Delete - Require confirmation to delete an inquiry
step (YES/NO)?
Specify YES, or Y, to display a confirmation panel
whenever an inquiry step is being deleted.
Specify NO, or N, to delete inquiry steps without
displaying the confirmation panel. This allows you to
delete multiple inquiry steps in a single panel
interaction.
Cycle(s) - Specify the default CA MICS file cycle(s) for
inquiry execution (cc-cc)
Specify this parameter to ensure that the Execution-Time
Parameters panel is always displayed with a default
specification for CA MICS file cycles. If no default
value is provided by the inquiry, the value specified in
this parameter is automatically supplied. You can
specify a single cycle or a range of cycles (for example,
specify 01 for a default of cycle 01 or specify 07-01 for
a default of cycles 07 through 01).
Database ID - Specify the database ID (x) of the default
inquiry database.
Specify this parameter to ensure that the Execution-Time
Parameters panel is always displayed with a default
specification for CA MICS database. If no default value
is provided by the inquiry, the value specified in this
parameter is automatically supplied. The database ID
parameter can be very useful since the distributed MICF
inquiries do not specify a default database ID. Specify
the one-character ID of the unit database that you use
most often when executing MICF inquiries. Then you will
not need to specify a database ID on the Execution-Time
Parameters panel unless you want to override your default
specification.
Note: If you have only one unit database in your CA MICS
complex, this parameter is not necessary because MICF
will specify the database ID automatically.
Direct Inquiries - Automatically execute direct inquiries on
END (YES/NO)?
Specify YES, or Y, to automatically execute direct
inquiries when END is pressed on the direct inquiry
function's primary panel. This saves one panel
interaction if you normally execute a direct inquiry
immediately after composing or modifying the inquiry.
Specify NO, or N to display the Direct Inquiry Processing
panel when END is pressed on the direct inquiry
function's primary panel. This gives you the opportunity
to save, cancel, or remodify instead of executing the
inquiry.
Direct Inquiries - Provide automatic summarization for list
reports (YES/NO)?
Specify YES, or Y, to activate the default summarization
feature for Direct Standard List and Direct Structured
List inquiries. If you do not specify a subheadings data
element (Generate Subheadings by), or if other data
elements follow the subheadings data element in the
report sequence specification (Generate Report in
Sequence by), default file summarization will
automatically summarize the selected CA MICS file
according to the report sequence specification before
printing the report. This is equivalent to specifying
these same data elements in the Data Summarization
extended option.
Specify NO, or N, to disable the default summarization
feature. If you do NOT specify the Data Summarization
extended option, the selected CA MICS file will be
reported WITHOUT summarization. This option will list
the contents of the entire CA MICS file exactly as read
from the CA MICS database.
Execution Mode - Default inquiry execution mode
(BATCH/FOREGROUND).
Specify BATCH, or B, to default to batch mode inquiry
execution. Specify FOREGROUND, or F, to default to
foreground mode execution. This value is displayed as
the default execution mode on the Database Inquiry
Execution panel and the Inquiry Step display (for
structured inquiries).
Execution Mode - Display execution mode before executing
inquiry (YES/NO)?
Specify YES, or Y, to display the CA MICS Database
Inquiry Execution panel before executing a MICF inquiry.
This gives you the opportunity to override the default
execution mode (Batch vs. Foreground).
Specify NO, or N, to bypass the CA MICS Database Inquiry
Execution panel and execute the inquiry using the default
execution mode.
Note: If BATCH is specified as the default execution
mode, you will NOT have the opportunity to override the
default batch JOB statement information.
Execution Options - Display execution options before
executing inquiry (YES/NO).
Specify YES, or Y, to display the Execution Options panel
when inquiry execution is requested.
Specify NO, or N, to bypass display of the Execution
Options panel.
If YES is specified for the display execution mode
parameter, this specification appears as the default for
the Override Execution Options parameter on the Database
Inquiry Execution panel.
File Mgmt. - Keep track of file contents and prime panel
entry fields (YES/NO)?
Specify YES, or Y, for this parameter.
Note: If you specify NO, or N, MICF will NOT validate
panel specification of CA MICS data elements and will NOT
prime data entry specifications. This will reduce MICF
processing costs and improve performance, but inquiries
will NOT be validated and results are unpredictable.
Function Selection Mode - Specify function selection path
(MENU/CATALOG).
Specify MENU, or M, to display the standard inquiry
function selection menus when composing a new inquiry or
when the Insert line command is coded on the Inquiry Step
Display panel.
Specify CATALOG, or C, to display the Inquiry Function
Catalog when composing a new inquiry or when the Insert
line command is coded on the Inquiry Step Display panel.
CATALOG allows you to select inquiry functions from the
scrollable catalog display without referencing the
inquiry function selection menus.
Hold Inq. Output/Save CSV - Hold batch inquiry outputs for
replay (YES/NO)?
Specify YES, or Y, to save inquiry outputs (that is,
color graphics, printed reports, and CA MICS/SAS logs) in
your private batch staging inquiry output catalog. You
can use the MICF Reports and Graphics option to review
inquiry outputs after the batch job completes execution.
You can replay color graphics, browse printed reports and
MICSLOG/SAS logs, and view any CSV file output from your
batch staging catalog. You can move inquiry outputs from
your batch staging catalog to your private inquiry output
catalog. You can also delete batch staging catalog
entries.
Specify NO, or N, for standard batch inquiry execution
with hardcopy outputs.
This parameter applies only to inquiries executed in
batch mode.
Note: If you specify NO, or N, any CSV file output
generated by the inquiry will be deleted when the inquiry
completes.
Inquiry Name - Specify the default name for new inquiries
(1-6 characters).
This is the default inquiry name displayed on the Insert
Database Inquiry panel.
Inquiry Title - Specify the default title (or "long name")
for new inquiries.
This is the default inquiry title, or long name,
displayed on the Insert Database Inquiry panel.
Job Card n - Default Job statement #n for ALL MICF batch
processing, where n = 1 to 4.
This is the default JOB statement for MICF batch
processing. Four lines of JOB statement information are
available. This specification will be displayed on all
panels that initiate batch processing.
Local Printer - Default local printer name for printed report
routing.
The default value for the local 3270 printer parameter on
the Print Inquiry Output panel. Specify a 1-8 character
DSPRINT printer ID or leave blank.
Local Printer - Specify DSPRINT command options for printing
inquiry outputs.
Default DSPRINT command options your data center
requires for DSPRINT processing.
PAD - Amount of space reserved for inquiry table growth (nn%
of inquiry size).
This is the amount of space, expressed as a percentage of
the size of the inquiry table, reserved for inquiry
growth. When sufficient pad space is available in the
inquiry table, inquiry changes are processed in place,
and library compress requirements are reduced. This is a
numeric value greater than 0 that can exceed 100%.
Presentation Menu - Use SAS/GRAPH presentation menu for
graphics (YES/NO)?
Specify YES, or Y, to display the SAS/GRAPH presentation
menu for color graphics replay. The SAS/GRAPH
presentation menu is recommended for normal MICF color
graphics processing.
Specify NO, or N, to exercise the full power of SAS/GRAPH
GREPLAY with access to template, color map, and graphics
copy facilities. This option is intended for advanced
graphics users with experience using the full power of
SAS/GRAPH. It will display the full-function SAS/GRAPH
GREPLAY menu for color graphics replay.
Print Inquiry Output - Print all outputs or limit to
report/log (ALL/RPT/LOG)?
This parameter applies to the inquiry output replay Print
Inquiry Output option.
Specify ALL to print reports, CA MICS log, and SAS log.
Specify RPT (report) to print just the reports.
Specify LOG to print just the CA MICS and SAS logs.
Production Reporting Hardcopy - Default additional SYSOUT
parameters.
JES SYSOUT parameters your data center requires for
SYSOUT data set allocations (for example, CHARS, COPIES,
FCB, FLASH, HOLD, UCS). Specify these parameters in JCL
statement format, separated by commas.
This option provides the default for the MICF production
reporting Hardcopy Reports and Logs panel.
Production Reporting Hardcopy - Default SYSOUT class (A-Z or
0-9).
Default JES SYSOUT class for production reporting
hardcopy reports and logs. This parameter corresponds to
the class subparameter of the DD statement SYSOUT=
parameter (that is, SYSOUT=(class,writer,form)).
Production reporting hardcopy SYSOUT class is required.
Specify one character: A-Z or 0-9.
Note: SYSOUT=* is not valid for dynamic allocation and
cannot be specified for this parameter.
Production Reporting Hardcopy - Default SYSOUT destination.
Default JES SYSOUT destination, a 1-8 character name or
(node,userid), for production reporting hardcopy reports
and logs. This parameter corresponds to the DD statement
DEST= parameter. Specify LOCAL for a local (non-RJE)
printer. Specify the remote name (for example, R15) for
a JES RJE printer. Leave this parameter blank to accept
the default established for your TSO logon-ID.
You can use the optional (node,userid) format to route
output to a VM/CMS user through JES and RSCS facilities.
Node and userid are 1-8 character names; node is required
for this destination parameter format. If your
(node,userid) format destination is longer than 17
characters, leave this parameter blank and specify
DEST=(node,userid) in the free-form production reporting
hardcopy additional SYSOUT parameters data entry area
above.
Production Reporting Hardcopy - Default SYSOUT external
writer.
Default JES SYSOUT external writer module for production
reporting hardcopy reports and logs. This parameter
corresponds to the writer subparameter of the DD
statement SYSOUT parameter (that is,
SYSOUT=(class,writer,form)). Specify a 1-8 character
name to route printed outputs to the JES spool for
processing by the specified external writer module.
Leave this parameter blank for standard JES processing of
printed outputs (that is, no external writer specified).
Production Reporting Hardcopy - Default SYSOUT form code.
Default JES SYSOUT form code for production reporting
hardcopy reports and logs. This parameter corresponds to
the form subparameter of the DD statement SYSOUT=
parameter (that is, SYSOUT=(class,writer,form)). Specify
a 1-4 character form number to route printed outputs to
the JES spool for printing on the specified form. Leave
this parameter blank for standard JES processing of
printed outputs (that is, no form number specified).
Recovery - Provide automatic inquiry recovery during
composition (YES/NO)?
Specify YES, or Y, to provide automatic recovery of
inquiry composition processing for system, ISPF, or MICF
failures. A temporary copy of the inquiry table will be
saved as you exit from each inquiry function (for
example, each time you return to the Inquiry Step
display). This prevents lost work due to system
failures.
Specify NO, or N, to bypass inquiry recovery processing.
This slightly reduces MICF processing costs.
Region size for batch job execution (for example, enter 4096
for REGION=4096K).
This is the batch job region size (1 to 4 digits) that is
used for MICF generated batch jobs. To use either the
data center default region or the region size specified
on the job card, leave this parameter blank. To override
the data center default batch job region size, specify
this parameter. This value is automatically designated
in K bytes. Do NOT append a K to your specification.
For example, specify 4096 to request a 4096K region.
Note: You CANNOT override this parameter when executing
a MICF inquiry in batch mode. It is specified only
through the MICF Options or Shared MICF Options
processes.
Reporting Job Streams? - Default display order: Alphabetical
or Execution?
Specify A, or Alphabetical, to view your Production or
User Reporting Job Stream output in alphabetical order by
inquiry name. If you prefer to see your job stream
inquiry output in the order in which they executed,
specify E, or Execution. The default is A, Alphabetical .
Reports and Graphics - Automatically select report or
graphics option (YES/NO)?
Specify YES, or Y, to automatically replay color graphics
or browse printed reports when you select an inquiry
output for review. Color graphics replay is NOT selected
automatically if you specify NO for the Color Graphics
User panel.
Specify NO, or N, to display the inquiry output replay
menu when you select an inquiry output for review.
Save Inquiries - Automatically save ALL composed inquiries
(YES/NO)?
Specify YES, or Y, to automatically save inquiries when
END is pressed on the Inquiry Step Display panel.
Specify NO, or N, to display a confirmation panel when
END is pressed on the Inquiry Step Display panel. This
gives you the opportunity to cancel inquiry changes in
case you inadvertently exit from the Inquiry Step
Display.
Saved Files - Save ALL intermediate files generated by MICF
inquiries (YES/NO)?
Specify YES, or Y, to save all intermediate files created
by MICF inquiries. This requires that each intermediate
file be assigned a unique file name. This parameter
should normally be set to NO.
Specify NO, or N, to save only those intermediate files
that have been explicitly marked as saved files. This
is the normal MICF processing mode.
SYSOUT Class - Default SYSOUT class for printed report
routing (A-Z or 0-9).
The default JES SYSOUT class for all printed outputs from
MICF, both for batch jobs and for interactive processing
(direct SYSOUT). This parameter corresponds to the class
subparameter of the DD statement SYSOUT= parameter (that
is, SYSOUT=(class,writer,form)). SYSOUT Class is
required. Specify one character: A-Z or 0-9.
Note: SYSOUT=* is not valid for dynamic allocation and
cannot be specified for the default SYSOUT class.
SYSOUT Destination - Default SYSOUT destination for printed
report routing.
The default JES SYSOUT destination, a 1-8 character name
or (node,userid), for all printed outputs from MICF, both
for batch jobs and for interactive processing (direct
SYSOUT). This parameter corresponds to the DD statement
DEST= parameter. Specify LOCAL for a local (non-RJE)
printer. Specify the remote name (for example, R15) for
a JES RJE printer. Leave this parameter blank to accept
the default established for your TSO logon-ID. You can
use the optional (node,userid) format to route output to
a VM/CMS user through JES and RSCS facilities. Node and
userid are 1-8 character names; node is required for this
destination parameter format. If your (node,userid)
format destination is longer than 17 characters, leave
this parameter blank and specify DEST=(node,userid) in
the free-form SYSOUT parameters data entry area below.
SYSOUT Form - Default SYSOUT form code for printed report
routing.
The default JES SYSOUT form code for all printed outputs
from MICF, both for batch jobs and for interactive
processing (direct SYSOUT). This parameter corresponds
to the form subparameter of the DD statement SYSOUT=
parameter (that is, SYSOUT=(class,writer,form)). Specify
a 1-4 character form number to route printed outputs to
JES spool for printing on the specified form. Leave this
parameter blank for standard JES processing of printed
outputs (that is, no form number specified).
SYSOUT Parameters - Additional, JCL format SYSOUT parameters
(for example, CHARS=).
Default JES SYSOUT parameters your data center requires
for SYSOUT data set allocations (for example, CHARS,
COPIES, FCB, FLASH, HOLD, UCS). Specify these parameters
in JCL statement format, separated by commas.
SYSOUT Writer - Default SYSOUT external writer for printed
report routing.
The default JES SYSOUT external writer module for all
printed outputs from MICF, both for batch jobs and for
interactive processing (direct SYSOUT). This parameter
corresponds to the writer subparameter of the DD
statement SYSOUT parameter (that is,
SYSOUT=(class,writer,form)). Specify a 1-8 character
name to route printed outputs to the JES spool for
processing by the specified external writer module.
Leave this parameter blank for standard JES processing of
printed outputs (that is, no external writer specified).
SAS Syntax Validation - Test panel entries for valid SAS
syntax (YES/NO)?
Specify YES, or Y, to validate MICF panel data entry
against SAS syntax rules. This is the normal MICF
processing mode.
Specify NO, or N, to bypass SAS syntax validation for
MICF panel data entry. This might be specified if you
are operating against a new version of the SAS system and
MICF has not yet been upgraded to accept new parameter
values (for example, if new SAS/GRAPH fonts are
available).
Test CA MICS - Allow access to test databases & test level
libraries (YES/NO)?
Specify YES, or Y, to allow MICF inquiries to access the
test databases in your CA MICS complex. This allows you
to test CA MICS product changes and access non-production
CA MICS components. Generally, the CA MICS Administrator
is the only CA MICS user needing this flexibility.
Specify NO, or N, to ignore the test databases in your
CA MICS complex (that is, process only the production
unit databases). This is the normal MICF processing
mode.
Validate panel entries against CA MICS file contents
descriptions (YES/NO)?
Specify YES, or Y, to validate panel data entry against
the contents of the specified CA MICS file. This applies
to data entry fields where a CA MICS file element is
normally specified. This is the normal processing mode
for MICF.
Specify NO, or N, to bypass validation against the
contents of the specified CA MICS file.
Note: This reduces MICF processing costs, but it lets you
compose invalid MICF inquiries so it is not recommended.
