The customization wizard IQIWIZRD
The customization wizard IQIWIZRD provides the means for a complete customization of Data Set Commander.
The IBM® delivered default installation options are stored in member IQIDFLTS of the SIQIPLIB target library (panel target library). The customization process updates the input member IQIDFLTS and replaces it in its library. It is recommended to first copy the latest IQIDFLTS member into a library that is different from the SMP/E controlled SIQIPLIB target library, and perform the customization there.
The following figures show you what is available in the wizard:
READY
%IQIWIZRD
PLEASE ENTER THE NAME OF -DSC- TABLE LIBRARY OR JUST PRESS ENTER TO EXIT.
EXAMPLE: IQI.SIQITLIB
===> DSC.V9R1M0.SIQITLIB
PLEASE ENTER THE NAME OF -DSC- TABLE LIBRARY OR JUST PRESS ENTER TO EXIT.
EXAMPLE: IQI.SIQITLIB
===> DSC.V9R1M0.SIQITLIB
PLEASE ENTER THE NAME OF -DSC- PANEL LIBRARY OR JUST PRESS ENTER TO EXIT.
EXAMPLE: IQI.SIQIPLIB
===> DSC.OVERRIDE.SIQIPLIB
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Please select which tasks you want to perform:
1 Customization - Set up IBMDSC options and defaults.
X EXIT - Exit - do not customize, do not set up password.
====================== Web Link ======================================
https://www.ibm.com/us-en/marketplace/data-set-commander-for-z
======================================================================
Make your selections in the following screens and then:
Press the Enter key to continue, or the END key to exit.
+---------------------------------------------------------------------+
| PREVIOUS DEFAULTS WERE UPDATED BY -IBM- ON 09/03/18 AT 08:27:53 |
+---------------------------------------------------------------------+
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
+---------------------------------------------------------------------------+
| Welcome to the IBMDSC customization wizard. You will be presented with a |
| series of screens where you will fill in different customization options. |
| |
| The selected options will determine which screens will be displayed, so |
| don't be surprised if you get different results when you run this utility |
| again with different selected options. |
| |
| Some of the options you select will force a change on all IBMDSC users, |
| while others will only change their defaults. Those options that change |
| default values will only affect new IBMDSC users. Existing users have |
| their defaults already set in their ISPF profile. |
| |
| Note that IBMDSC users can change their defaults via the SET command (by |
| entering "DSC SET" or shortcut "ISET" on any ISPF panel). |
| |
| You may display a list of all command shortcuts by entering main command |
| "DSC?" from any ISPF panel. |
+---------------------------------------------------------------------------+
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Please select the options you would like to inspect or specify:
(some options are pre-selected by IBMDSC)
Select Option Notes
------- ----------------------------------- ----------------------
S DASD storage management Activate built-in support
S Browse/View preferences Specify VIEW data integrity
S Obtain info about -DSC- objects Recommended for new installation
S Install -DSC- session exits Specify CLIST/REXX/module name
Install -DSC- command user exit Specify load-module name
Change names of general commands Rename -DSC- command names
S Copy/Move/Compress utility options Specify IEBCOPY utility options
S Session diagnostics options Control PANELID and other options
S User interface options Action bars, hotbars, etc.
N Disable -DSC- at startup by default Command DSCON manually enables DSC
S Panel-Extension-Language options Support for user defined panels
S -DSC- Monitor Options Specify monitor execution options
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Verify Object List (OLIST) defaults (for first time IBMDSC users):
Default OLIST command ===> B (B=Browse, E=Edit, V=View)
(When a line is selected by number, with the S line command, or with cursor )
Check edit recovery when list opens ===> N (Y=Yes, N=No)
Default cursor position ===> M (M=Main command, L=Line command)
Show VOLSER of cataloged data-sets ===> Y (Y=Yes, N=No)
Insert VOLSER in OLIST invoked CLISTs ===> N (Y=Yes, N=No)
Native (generic) DSNAME patterns ===> Y (Y=Yes, N=No)
Allow OLIST name of a cataloged alias ===> N (Y=Yes, N=No)
Permanent OLIST automatic validation ===> N (Y=Yes, N=No)
Maximum size of permanent OLIST ===> 5000 (Min=10 Max=99999)
Maximum size of temporary OLIST ===> 50000 (Min=10 Max=99999)
Maximum size of Dataset-History list =====> 100 (Min=10 Max=999)
Temporary OLIST prompt threshold ===> 2000 (Min=10 Max=99999)
(When threshold is reached user is prompted to stop or resume filling list)
Implicitly created OLIST library UNIT name ===> SYSALLDA
Implicitly created utility work files UNIT name ===> SYSALLDA
Default suffix qualifier for CLONE data sets ===> CLONE
Catalog search pattern rules ===> 1 (0, 1, 2)
(0) Unrestricted dataset name patterns
(1) First character may not be a "wild card"
(2) High level qualifier may not have any "wild card" characters
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC searches for the user PRIVATE OLIST library in the following order:
1. In the list of allocated files, for a DD name PLSTLIBW . If it is
pre-allocated (before OLIST is invoked), IBMDSC will use it.
2. In the catalog. If a library by the name "qual1.PLIST.LIBRARY" is
catalogued, IBMDSC will use it. "qual1" stands for the first level
qualifier you specify on this screen.
3. In the list of allocated files, for a DD name IPITBLIB . If it is
pre-allocated (before OLIST is invoked), IBMDSC will use it.
If IBMDSC cannot find the library pre-allocated or catalogued (as
explained above), it will try to allocate a new PDSE library, using the
name "qual1.PLIST.LIBRARY" with the UNIT name specified below.
Enter/Verify OLIST library defaults (as explained above):
PREFIX ("qual1") ===> U ( U USERID, P TSO PREFIX)
Allocation UNIT name ===> SYSALLDA (Unit name, blank for SYSALLDA ,
or * for default TSO unit name)
IBMDSC also uses DD(IPITBLIB) for specifying a personal library as a
repository of persistent tables, such as CUT/PASTE clipboards and
the TSO-SHELL command lists. This library may be dynamically allocated
at IBMDSC startup whenever DD(IPITBLIB) is omitted from the logon procedure.
Elect persistent table library use: Y (yes), N (no) ===> Y
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Object List FINDTEXT and FINDMEM Control
STOP AFTER ===> 999 Number of items to process successfully
PROMPT AFTER ===> 999 Number of items to process before prompt is issued
START COLUMN ===> 1 Starting column in target data record
END COLUMN ===> 99999 End column in target data record
Specify Y (Yes) or N (No) for the following options:
AUTOMATIC ===> N Search without stopping at successful items?
EXCLUDE ===> N Exclude failing items from object list?
PACKED DATA ===> N Expand ISPF packed data format?
FIND PROMPT ===> Y Prompt with FIND command upon selecting an object?
FULL REPORT ===> N Default option for FINDTEXT
DETAILED ===> N Break down by search criteria?
Member Selection List GLOBAL Control
STOP AFTER ===> 999999 Number of members to process successfully
PROMPT AFTER ===> 999999 Number of members to process before prompt is issued
START COLUMN ===> 1 Quick FIND starting column in target data record
END COLUMN ===> 99999 Quick FIND end column in target data record
Specify Y (Yes) or N (No) for the following options:
AUTOMATIC ===> Y Process without editing successful items?
LINK ===> Y Process each command only if previous command succeeds?
EXCLUDE ===> Y Exclude failing items from selection list?
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
When a user selects a permanent OLIST, IBMDSC searches for an ISPF table
member with a similar name. The search is done in the following order:
1. The PUBLIC OLIST library that is allocated to DD name PLSTLIBP .
A public OLIST can only be imported for use and never be replaced by
the user. He may modify it and save it as a PRIVATE OLIST with a
different (non public) name.
2. The PRIVATE OLIST library that is allocated to DD name PLSTLIBW .
The user has complete control over his private OLISTs.
A private OLIST name can not be same as of a public OLIST or any of
the following reserved names: "@DD", "@H", "@HH", "@L" . It is also
not allowed to start with "@LIST" or "IQI" .
3. The READ-ONLY OLIST library that is allocated to DD name PLSTLIBR .
A read-only OLIST can be imported for use, modified and stored as
a PRIVATE OLIST with the same (or different) name.
You may specify here the default names of the public and read-only OLIST
libraries to be dynamically allocated by DSC when their corresponding
DD statement is either omitted from the DSC logon procedure, or specifies
a dummy data set.
PUBLIC OLIST library ==> IQI.PUBLIC.OLISTLIB
READ-ONLY OLIST library ==> IQI.READONLY.OLISTLIB
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC uses object-oriented technology to provide users with access to
different classes of objects they commonly use. The most common object
class is a data set. Within the DATA SET object class, IBMDSC supports
several subclasses (for example sequential data sets, PDS data sets).
Each object class is internally associated with a "METHOD" - an access
mechanism that indicates how IBMDSC should handle each class. This is
similar to the "OLE" concept in Microsoft's Windows on the PC.
Some methods are provided internally by IBMDSC (for example the method
that handles PDS libraries and display the MSL -the Member Selection
List). Other methods are IBMDSC interfaces to third party products - for
example the DB2-table class method requires a third party product that
can browse or edit DB2 tables.
The following screens you will select which object classes should be
supported by IBMDSC, and which methods each supports.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Select the optional object classes to be supported. Internal
object classes are already preselected. If you are unsure, select
all options to get more information about each one. You will be
able to de-select undesired option later.
Select Object Class Notes
------- ------------------------------------ ----------------------
S Open Edition files (IQI$UNIX CLIST) Requires z/OS UNIX Services
S PC files (IQI$PC CLIST) Requires ISPF workstation
S IBM SCLM support Activates built-in support
Panvalet libraries Interfaces to third party product
Librarian files Interfaces to third party product
PDSMAN libraries Activates built-in support
S VSAM data sets Interfaces to third party product
S DB2 tables Interfaces to third party product
S User defined objects Define your own interface
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Specify DASD management products support:
Name of MIGRATION/ARCHIVAL system ===> HSM (HSM, DMS, ASM2, ABR or BLANK)
Name of secondary ARCHIVAL system ===> (ABR or blank)
Name of MIGRATION/ARCHIVAL volume ===> MIGRAT (e.g. MIGRAT, ARCIVE)
Name of secondary ARCHIVAL volume ===>
Name of "DELETE migrated" command ===> HDELETE (e.g. HDELETE)
(Command name, CLIST, or REXX EXEC to be used instead of the DELETE command
when a user tries to delete a migrated/archived data set in OLIST).
Notes: - If you leave this field BLANK, IBMDSC will recall/restore the
data set and then display a confirmation screen (that displays the
data set contents if the DSORG is PO or PS).
- If you do specify a command, CLIST or REXX EXEC, IBMDSC will
invoke that command after receiving a confirmation on a panel
that only lists the name of the data set (no contents displayed).
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC VIEW FUNCTION CUSTOMIZATION:
IBMDSC provides two types of VIEW: SHARED-VIEW and EXCLUSIVE-VIEW .
EXCLUSIVE-VIEW is similar to EDIT - only one user can access the
file (member) at a time. Additionally, a confirmation screen will
be displayed before changes are saved back to the file.
SHARED-VIEW does not issue ENQ on the file, thus allowing others to
edit the file at the same time. Under SHARED-VIEW the save command
is disabled, but the REPLACE/CREATE commands can still be used.
Specify the type of VIEW for your installation:
VIEW TYPE ===> S (E=Exclusive, S=Shared)
Should users be allowed to override the above setting?
USER CAN OVERRIDE THE VIEW TYPE ===> Y (N=No, Y=Yes-Override is allowed)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
DEFAULT PROCESS FOR MAIN PANEL OPTION 1 (BROWSE, VIEW)
The program used to invoke BROWSE on the ISPF main menu can have two
modes - BROWSE or VIEW. The program ("ISRBRO") is invoked by a statement
in the ")PROC" section of the panel: "PGM(ISRBRO)"
When PGM(ISRBRO) is invoked, IBMDSC displays an entry screen that
includes a "DEFAULT ACTION ===>" field which provides the ability
to set the action to B rowse, V iew, or E dit.
The "DEFAULT ACTION" settings on this screen determines how IBMDSC
handle browse requests. This setting is easily overridden by users
via the SET command which can be issued on the same panel.
The advantages of VIEW are the ability to change the file, to use CUT
and PASTE, and to exclude lines. The disadvantage is that VIEW
pre-loads the entire file and uses more resources.
Specify the default action when PGM(ISRBRO) is invoked:
DEFAULT ACTION ===> B (B=Browse, V=View)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
You have indicated that you want to activate the IBMDSC initialization exit.
Verify or change the exit specification:
Exit type ===> C (P=Program, C=CLIST or REXX EXEC, M=ISPF selection menu)
Exit name ===> IQICRTBL (Name of program, CLIST, or panel)
When invoked ===> I (I=ISPF session start-up, S=Every split screen start-up)
If you specify an exit, IBMDSC will invoke it via the ISPF SELECT
service. That means that your exit has the ability to issue ISPF dialog
services as well as other functions.
A typical use of such an exit is to invoke a mail interface program that
displays appropriate news to the user. Another typical use is to
allocate user-specific files (like test files, the IBMDSC object-list
(OLIST) library etc.
------------------------ IBMDSC - Customization Wizard ------------------------
OPTION ===>
Name of COPY and COMPRESS utility program ===> IQIBUTIL (Default=IQIBUTIL)
Utility default PARM='LIST=YES|NO|ONLY' ===> YES (Default=YES)
When IQIBUTIL is invoked via EXEC PGM=IEBCOPY it should assume:
Utility default PARM='FULLFUNC|PASSTHRU' ===> FULL (Default=FULL)
Please select data integrity option (for COMPRESS/EXPAND/FREE TRACK functions):
Integrity option ===> 2 (1 or 2)
1 EXCLUSIVE CONTROL:
IBMDSC will use ISPF's COMPRESS function to compress libraries (ISPF uses
DISP=OLD for compression). IBMDSC will also use DISP=OLD for the expand
directory and FREE tracks functions.
2 SHARED WRITE:
IBMDSC will use DISP=SHR with compress/expand, but will utilize the ISPF
serialization protocol to ensure that no program that adheres to that
protocol writes to the file while it is being processed.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
You have indicated that you need to provide support for the IBMDSC
Panel-Extension-Language (PEL) in certain user defined panels.
All panel names starting with "IQI" are already PEL-eligible.
You may enter here the panel name mask of your other PEL-eligible panels.
Following are the panel name mask rules:
- It may contain only alphanumerics, national symbols, and * or % .
- First character cannot be numeric.
- There must be at least one alphanumeric character or national symbol .
- An * will automatically be appended to a nonblank short name.
PEL-eligible user panel name mask ===> XYZ*
You may also specify values (alphameric) of PEL optional user dialog variables:
UDLG1 = 1 to be used in a ))IF-VAR.UDLG1=? statement
UDLG2 = 2 to be used in a ))IF-VAR.UDLG2=? statement
UDLG3 = 3 to be used in a ))IF-VAR.UDLG3=? statement
UDLG4 = 4 to be used in a ))IF-VAR.UDLG4=? statement
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Notes:1. The values set here are active only until the first time
users log on to IBMDSC. Thereafter these values can be
changes by each user with the IBMDSC "SET" command.
2. There is no overhead in activating these options.
Verify Diagnostic options (Enter Y for YES, N for NO):
Diagnose panel errors ===> N (Display errors)
Diagnose program errors ===> N (Abends by ISPF called programs)
Display panel identifier ===> N (forcing "PANELID ON" on all panels)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC includes an APF authorized started task Monitor (IQIMONTR).
It is protected via the following RACF defined resource entities:
ENTITY=IQIMONTR.OPER of CLASS=FACILITY
ENTITY=IQIMONTR.TSO of CLASS=FACILITY
A user may have one of the following Monitor related authority levels:
FULL - Complete control to start, stop, modify, and display Monitor status.
LIBS - Modify monitored LLA libraries status and display Monitor status.
VIEW - May only display Monitor status.
NONE - No authority at all.
The expected RACF user authorization levels are:
FULL - LEVEL=CONTROL for ENTITY=IQIMONTR.OPER of CLASS=FACILITY
LIBS - LEVEL=ALTER for ENTITY=IQIMONTR.OPER of CLASS=FACILITY
LIBS - LEVEL=UPDATE for ENTITY=IQIMONTR.OPER of CLASS=FACILITY
LIBS - LEVEL=CONTROL for ENTITY=IQIMONTR.TSO of CLASS=FACILITY
VIEW - LEVEL=READ for ENTITY=IQIMONTR.OPER of CLASS=FACILITY
VIEW - LEVEL=UPDATE for ENTITY=IQIMONTR.TSO of CLASS=FACILITY
VIEW - LEVEL=READ for ENTITY=IQIMONTR.TSO of CLASS=FACILITY
NONE - All other possible RACF levels.
Set the default user authority ===> L (Libs, View, None, Disable)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Specify the default User Interface options for users who have not yet
used IBMDSC. (Enter Y for YES, N for NO):
Activate HOTBARS (on IBMDSC panels) ===> Y (Cursor sensitive command fields)
Globally activate action bars ===> Y (CUA style pulldown menus)
If action bars are globally active:
Use action bars in edit/BROWSE ===> Y (Note:action bar takes 2 panel lines)
Use action bars in MSL ===> Y (IBMDSC's Member Selection List)
Use action bars in OLIST ===> Y (IBMDSC's Object list)
Use action bars in DSLIST ===> Y (ISPF option 3.4)
Notes 1. Users can change these defaults. The recommended method of changing
these options is by entering the DSC SET command on the main menu.
2. Pre-processing ISPF panels will prevent IBMDSC from changing these
options on ISPF panels. IBMDSC panels should never be pre-processed.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Prompt with FIND command after a Global FIND ==> Y (Y=Yes, N=No)
Insert VOLSER in MSL invoked CLISTs ==> N (Y=Yes, N=No)
Display member titles whenever available ==> Y (Y=Yes, N=No)
Scroll member list to target member name ==> Y (Y=Yes, N=No)
Support PDSE member generations (z/OS V2.1) ==> Y (Y=Yes, N=No)
If member generations exist, display only generation 0 ==> Y
Copy/Delete/Rename Generation 0, affects all generations ==> N
Support Program Object member generations ==> N
Automatically store modified member titles ==> N (Y=Yes, N=No)
Default SAVE NEWGEN (PDSE member generation) ==> Y (Y=Yes, N=No)
Default EDIT STATS ON for ISPF statistics ==> N (Y=Yes, N=No)
If STATS ON by default, generate extended statistics ==> N
Display PRESERVE ON/OFF warning message ==> N (Y=Yes, N=No)
RENAME member updates title and change date ==> N (Y=Yes, N=No)
The following optional DSC functions are implemented as EDIT macros
and may be switched back to their ISPF equivalent commands:
DSC EDIT A (Assist) command ==> Y (Y=Yes, N=No)
DSC EDIT CREATE/REPLACE commands ==> N (Y=Yes, N=No)
DSC EDIT STATUS command ==> Y (Y=Yes, N=No)
DSC EDIT SUBMIT command ==> Y (Y=Yes, N=No)
DSC EDIT CUT/PASTE commands ==> Y (Y=Yes, N=No)
If DSC CUT/PASTE in use set the following default options:
CUT APPEND (instead of REPLACE) ==> N (Y=Yes, N=No)
CUT APPEND AFTER (instead of BEFORE) ==> Y (Y=Yes, N=No)
PASTE AFTER (instead of BEFORE) ==> Y (Y=Yes, N=No)
Specify the site-wide member name for storing library member titles:
Member title list name ===> Z999TITL
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
MSL (Member Selection List) is the IBMDSC built-in method of displaying
member lists in ISPF. MSL provides stacking of multiple commands,
filtering of the member list, global actions (global find, change,
edit), member-preview windows, and other powerful functions.
Specify below the following MSL defaults:
Disable STATS command: disallow to manually change ==> N (N=No, Y=Yes)
directory entry ISPF statistics data.
Disable J line command: disallow to submit a member ==> N (N=No, Y=Yes)
as a JCL JOB. To prevent from accidental submission.
User modifiable defaults (via the SET command of MSL)
Automatic preview: display top of member window ==> Y (N=No, Y=Yes)
following the Locate, Find, or FindText commands.
Enable special characters support in target member ==> N (N=No, Y=Yes)
names of line commands: Alias, Copy, Rename.
Enable support for IEBCOPY member name convention: ==> Y (N=No, Y=Yes)
accept "_" (x'6D') and "{" (x'C0') in a member name. Also implied by above.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC has a built-in printing engine that directs printouts to a
SYSOUT file without the intermediate ISPF LIST data set.
Users can direct their IBMDSC print requests to the ISPF
list data set, or use IBMDSC's faster method.
When the IBMDSC method is selected, IBMDSC dynamically allocates
a SYSOUT file using the specifications that reside in each
user's profile. On the following screen you will specify the
defaults for users who have not yet run under IBMDSC. Users who
have already run under IBMDSC have their defaults saved in their
ISPF profile.
To change the defaults, users can use the SET PRINT command (in
MSL or OLIST).
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
In case IBMDSC print requests directed to the IBMDSC print engine rather then
the ISPF LIST dataset, specify the SYSOUT allocation defaults (for users who
have not yet used IBMDSC).
IBMDSC users can change these options via the SET command.
Enter/Verify SYSOUT attributes:
DESTINATION ID ===> (Node-id<.User-id>)
CLASS ===> A (or Sysout class)
Lines per page ===> 60 (page size)
Keep in HOLD queue ===> Y (Y=Yes, N=No)
FORM number ===>
FCB name ===>
WRITER name ===> (Output WRITER)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
IBMDSC provides an alternative TSO command shell that provides
command history, permanent commands entries, execution of ISPF dialog
manager statements, and substitution of data sets pointed by the
cursor (create your own point-and-shoot commands).
For example, if a permanent entry number 5 is defined as:
%TRANSFER SYSB.JONES DSN(/)
then by entering "TSO 5" on any ISPF screen while placing the cursor
on a data set name appearing on that screen would execute the %TRANSFER
command on the pointed data set.
The SET command is used to activate or deactivate the IBMDSC TSO command shell.
For users who have not yet used IBMDSC, indicate the desired defaults:
Use IBMDSC shell ===> Y (Y=Yes - Use the IBMDSC TSO shell, N=No)
Initial screen ===> H (H=History list, P=Permanent list)
Command list limit ===> 100 (History and Permanent maximum number of entries)
Automatic filling ===> Y (Y=Yes - Automatically fill permanent list, N=No)
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Specify DSLIST (option 3.4) parameters:
IBMDSC adds the ability to invoke OLIST (Object/dataset list) directly
from the DSLIST panel. These object lists are faster and more powerful
than the ISPF Data set list (DSLIST).
The following option specifies the DEFAULT action taken on the DSLIST panel
when the user presses the ENTER key with a blank "OPTION ===>" field:
Default action ==> TP ( DS DSLIST, PL Permanent List, TP Temporary List)
DSLIST M line command ==> N ( B Browse, E Edit, V View, N Normal ISPF)
Notes: - Regardless of the selected default, users can select any other
option by explicitly entering one of the other DSLIST
panel options (like DS V PV etc.).
- The default action may also be set by each user via the
SET command on the DSLIST panel.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
CLM is ISPF's Software Configuration and Library Manager. SCLM provides
ontrolled edit capabilities within standard PDS libraries (with member locking,
heck-in/check-out), full development life cycle of applications (including
"MAKE"), and extensive reporting. SCLM is an integrated part of ISPF.
BMDSC can provide significant benefits to SCLM users by integrating SCLM
upport into the standard member list, DSLIST and OLIST. If your installation
ses SCLM, it is recommended that you activate the SCLM support on this screen.
ctivate SCLM support ===> D Y =Yes - Support SCLM for all users
N =No - Do not provide SCLM support
D =Conditional support. SCLM will only be
supported for users who at the time IBMDSC is
started, have a preallocated DD "IQISCLM" .
This DD can be allocated in the LOGON PROC/CLIST.
Example: ALLOC DD(IQISCLM) DUMMY
or //IQISCLM DD DUMMY
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
Verify SCLM options:
SCLM parameter prompt ===> F Y =Yes - Whenever an SCLM library is accessed.
N =No - Users must preset the parameters with
the SCLMPARM command (in the Member List).
F =A prompt screen is displays only on first time
access to a specific library. Thereafter the
previous parameters for that library are used.
Note:the above option can be changed by individual users via the SET command.
Override SCLMCHK value ===> * (W=WARN, E=ERROR, N=NONE, *=no override)
This setting allows you to override the value of the "SCLMCHK" field in
ISRCONFG (ISPF's configuration table). This field defines how edit should
react when attempting to edit an SCLM-saved file without SCLM locking.
SCLMCHK values (See ISPF Customization for more details):
WARN -Display a warning message if edited project/member is SCLM controlled.
NONE -No checking is done. No warning messages issued.
ERROR -Reject editing of SCLM-saved members without SCLM or IBMDSC locking.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
When IBMDSC detects a VSAM data set (in BROWSE, EDIT, VIEW, DSLIST, or object
list), it may use an interface to process it. You may select which kind
of VSAM support you want in your installation, if any. The table below
shows what CLIST will handle the support you have selected.
VSAM interface ===> 2 (Select one of the following options)
ption Invoked VSAM interface Interface CLIST
----- ------------------------------------------------------ ---------------
0 None (IBMDSC will not handle VSAM files.) . . . . . . Not applicable
1 Installation-written VSAM interface . . . . . . . . . IQIVSAM
2 IBM File Manager for z/OS . . . . . . . . . . . . . . IQI$FMGR
3 File-Aid VSAM browser/editor(Version 10 and above) . . IQI$FAID
4 File-Aid VSAM browser/editor(Version 9 and below) . . IQI$FAR8
5 File-Aid VSAM browser/editor(Version 7 and below) . . IQI$XPRT
6 Data-Xpert VSAM browser/editor . . . . . . . . . . . . IQI$XPRT
7 MacKinney ISPF VSAM Utility . . . . . . . . . . . . . IQI$MCKN
8 IBM Ditto/ESA . . . . . . . . . . . . . . . . . . . . IQI$DIT
9 Serena STARTOOL . . . . . . . . . . . . . . . . . . . IQI$STOL
10 VSAM RECORD BROWSER (A SAMPLE WORKING INTERFACE) . . . IQIVBRO
Notes: Options 2-9 require a third-party product. If such a product uses
LIBDEFS, include the LIBDEF statements in the interface CLIST.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
When IBMDSC detects a data set name that starts with a hyphen (in BROWSE
EDIT, VIEW, and the object list), it assumes that the text string
following the hyphen is the name of a DB2 table. You may select which
kind of DB2 support you want in your installation, if any. The table
below shows what CLIST will handle the support you have selected.
DB2 interface ===> 9 (Select one of the following options)
ption Description CLIST
----- --------------------------------------------------------------- --------
0 None (IBMDSC will not handle DB2 tables.) . . . . . . . . . . . None
1 Installation-written DB2 interface . . . . . . . . . . . . . . IQIDB2
2 Computer Associates Pro-EDIT Version 5.0 or earlier . . . . . . IQI$PRED
3 Computer Associates Pro-EDIT Version 5.1 or above . . . . . . . IQI$PR51
4 Computer Associates Pro-EDIT Version 7.0 or above . . . . . . . IQI$PR70
5 Platinum Technology's RC/UPDATE browser/editor . . . . . . . . IQI$RCUD
6 Platinum Technology's RC/UPDATE browser/editor VER 2 or above . IQI$RCU2
7 Compuware's FileAID for DB2 table browser/editor . . . . . . . IQI$FAB2
8 CDB Software's CDB/EDIT table editor . . . . . . . . . . . . . IQI$CDBE
9 IBM File Manager/DB2 for z/OS table browser/editor . . . . . . IQI$FMD2
Note: If you use LIBDEFs to invoke your DB2 editor, include
the LIBDEF statements in the appropriate CLIST named above.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
You have indicated that you want to define user objects.
IBMDSC will assume that a data set name (in BROWSE, EDIT, VIEW, and OLIST)
that starts with the greater-than sign (>) is a user object, and pass
control to a CLIST (or REXX EXEC) to handle the object. A skeleton CLIST,
indicating the available parameters, resides in the IBMDSC CLIST library
under the name IQI$USER.
Specify below the name of the user object handler:
CLIST/REXX EXEC name ===> IQI$OUT (Leave BLANK for no user-object support)
NOTE: A sample object handler called IQI$OUT is in the IBMDSC CLIST library.
------------------------ IBMDSC - Customization Wizard ------------------------
Command ===>
The customization wizard has completed the first phase of interviewing you for
the installation options.
You can now proceed to finalize the customization process (press the ENTER key)
or you may cancel (press the END key) and redisplay the initial screen.
-DSC- ------------ TSO COMMAND SHELL - RESTRICT HISTORY RECORD Row 1 to 2 of 2
Command ===> SCROLL ===> CSR
Main commands: CANCEL, DOWN, END, UP
Line commands: I insert, D delete
+-------------------------------------------------------------------+
| TSO commands (or CLIST or REXX EXECS) specified here with the |
| "No History" set to Y (YES) will not be recorded in the command |
| history list of the TSO Command Shell (option 6). |
+-------------------------------------------------------------------+
Line Command No
COMMAND or CLIST History
--------- -------- ------
PASSWORD Y
PROTECT Y
------------------------
Specify Disposition of Log Data Set
Command ===>
Log Data Set (MROTTER.SPFLOG1.LIST) Disposition:
Process Option . . . . 1. Print data set and delete
2. Delete data set without printing
3. Keep data set - Same
(allocate same data set in next session)
4. Keep data set - New
(allocate new data set in next session)
Batch SYSOUT class . .
Local printer ID or
writer-name . . . . .
Local SYSOUT class . .
List Data Set Options not available
Press ENTER key to complete ISPF termination.
Enter END command to return to the primary option menu.
Job statement information: (Required for system printer)
===>
===>
===>
===>
+----------------------------------+
| INSTALLATION DEFAULTS WERE SAVED |
+----------------------------------+