home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
lansystk.zip
/
MPTSUTIL
/
APPLETS
/
CASSETUP.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1998-05-08
|
87KB
|
2,826 lines
ΓòÉΓòÉΓòÉ 1. Overview ΓòÉΓòÉΓòÉ
The Setup Utility (CASSETUP) for Redirected Installation is an applet that
provides a presentation manager interface for installing and configuring a code
server for redirected installation. The setup utility also provides a user
interface to assist administrators in creating bootable diskettes for use by
clients to initialize and process redirected installation sessions.
ΓòÉΓòÉΓòÉ 1.1. Functions ΓòÉΓòÉΓòÉ
The Setup utility provides the following functions to assist administrators in
preparing for redirected installation:
o A Presentation Manager interface for the installation and removal of
redirected installation support. Redirected installation support includes
the LAN CID Utility and the Service Installable File System (SRVIFS).
o Installation and removal of diskette images for:
- The IBM OS/2 2.1 program
- The IBM OS/2 2.11 program
- The IBM OS/2 Warp Version 3.0 program
- The IBM OS/2 Warp Version 3.0 program with WIN-OS2
- The IBM Service Paks
- The IBM Network Transport Services/2 (NTS/2) program
- The IBM LAN Server 4.0 program, including: IBM Multi-Protocol Transport
Support (MPTS).
Note: The utility processing is controlled by "profiles" defining the
installation operation for images. The on-line documentation
provided with the utility defines the contents of these profiles
and how additional application profiles can be created to extend
the support.
o A method of recording application diskette images that were previously loaded
onto the server. This function allows you to use the utility with these
images without having to reload them.
o Creation of a LAN CID Utility casprep and command file that will allow
clients to install selected product images that were installed on the code
server through the setup utility.
o Creating boot diskettes for use by clients to initialize and process
redirected installation sessions.
Note: The code server must be operating on an IBM OS/2 2.0 or later system to
use the setup utility.
ΓòÉΓòÉΓòÉ 1.2. Requirements ΓòÉΓòÉΓòÉ
The following are requirements to execute the setup utility:
OS/2 program - The OS/2 diskette images must be version 2.1 or later.
Furthermore, the OS/2 diskette images must be installed before client
boot diskettes can be created.
MPTS or NTS/2 - IBM Multi-Protocol Transport Support (MPTS) or IBM Network
Transport Services/2 (NTS/2) must be installed and configured for
NETBIOS before you can use the setup utility to install Redirected
Install Support. The MPTS or NTS/2 diskette images must also be
installed before client boot diskettes can be created.
REXX - Redirected Installation Support requires REXX. Therefore, the Setup
Utlity requires REXX to be installed on the workstation before you
can install Redirected Installation Support.
The Rexx utility package "REXUTILS" must additionally be installed.
ΓòÉΓòÉΓòÉ 1.2.1. Installation and Setup ΓòÉΓòÉΓòÉ
The Setup utility is installed by invoking the CASINST.CMD. The install program
can be initiated from an OS/2 command line by either specifying only
CASINST.CMD or the user may specify the following parameters:
CASINST.CMD /T=<target_path> /S=<source_path> /L=<log_file>
/T= defines the target path (i.e; drive and optionally directory) on
which the setup utility is to be installed.
/S= defines the source path to the setup utility program images.
/L= defines a fully qualified file specification to which all
installation messages, status and error, are to be logged.
When invoked without parameters, the source and target paths are assumed to be
the current path. No files are transferred, but the desktop and config.sys are
updated.
The installation processing is:
o The setup utility program files are copied to the directories, unless the
source and target directories are the same. These files consist of:
<user_target>
CASBOOTD.EXE ........ program for finding the boot drive
CASENG1.CMD ........ command file for application image loads
CASENG2.EXE ........ program for remote install support loads.
CASENG3.CMD ........ command file for create client (boot) diskettes.
CASENG4.EXE ........ program for remote install support removal.
CASENG6.CMD ........ command file for LAN CID utility casprep generation.
CASRXRM.CMD ........ command file for application image deletes.
CASSETUP.EXE ........ main graphical user interface program.
CASSETUP.DAT ........ profile of file names and locations.
CASSETUP.MSG ........ message file.
CASSETUP.INF ........ online documentation source.
CASSETUP.STR ........ initial code server persistent storage
file, containing defaults.
CASSETUP.DLL ........ resource DLL containing iconic (BMPs)
used to represent object.
CASSFUNC.DLL ........ support routines library.
CMSGBOX.EXE ........ message box routine.
GETBOOT.CMD ........ retrieves boot drive.
GETFIX.CMD ........ retrieves operating system fix level.
GETREXX.CMD ........ insures that Rexx is installed.
<fn>.PRO ........ Application profile(s)
<fn>.SCR ........ Create diskette script file(s)
o A workplace shell object from which to invoke the setup utility is created.
o The SET PATH, SET DPATH and LIBPATH statements in config.sys are updated. The
target directory is appended if it is not already in a statement. If the
target directory is already in all three statements, then the config.sys file
is not changed.
ΓòÉΓòÉΓòÉ 1.2.1.1. Run time file generation ΓòÉΓòÉΓòÉ
During the operation of setup utility additional files are created and stored
within the directory. Examples of these files are:
<filename>.BKU ........ Code Server persistent storage backup,
created whenever the Code Server storage
is changed (i.e; rewritten to disk).
<filename>.RPT ........ Code Server report files.
Note: the file extension can be
changed, but "rpt" is the default.
miscellaneous temporary processing files...
ΓòÉΓòÉΓòÉ 1.2.1.2. Run time directory creation ΓòÉΓòÉΓòÉ
During execution processing setup utility will generate additional directory
structures. The structures are of two types:
o Predefined structures - follow specific naming conventions. An example of
these directory structures is:
<user drive\path>\SERVER ........ SRVIFS server data
o User controllable structures - are created based on user input definitions.
ΓòÉΓòÉΓòÉ 1.2.2. How to proceed ΓòÉΓòÉΓòÉ
Once the setup utility is installed, the operation is simple. When the
workplace shell object is opened, the code server setup utility container is
displayed. From this container all operations performed by the setup utility
may be started.
Two objects appear within the code server setup utility container, an
Applications folder and a code servers folder. Both folders open into
containers by double clicking on the iconic representation of the object.
The applications container opens to display iconic representations of
application objects known to the setup utility. The applications become known
to setup utility by the presence of application profiles contained within a
specific, user definable, directory. The setup utility when installed is
shipped with a set of default profiles. These objects are the basis for
application image loads onto a code server. By selecting an application icon
and dragging the icon onto the code server object contained within the code
servers container the image load operation is invoked.
The code servers container opens to display a single code server object within
a hierarchical (i.e; "tree") display. Wherein the code server object is the
"tree trunk" and applications loaded on the code server are "limbs" on the
tree. This object may or may not display applications, depending on whether
applications have been previously loaded or registered onto the code server via
this utility.
The code servers container is the primary interface for the setup utility user.
From this Container all operations, except the definition of some file
locations, can be performed.
On-line help is available for each operation and panel displayed. The setup
utility user can access the help via the container menu-bars or the help push
buttons on individual panels. The help displayed is contextual based on the
panel from which the help is activated.
The following sections define the contents and operation of each panel
displayed.
ΓòÉΓòÉΓòÉ 2. Graphical User Interfaces (GUI) ΓòÉΓòÉΓòÉ
Exceptions to standard panel processing.
o Container Objects do not have popup menus.
o Bitmaps are used for object representation within containers instead of
icons.
o Menu mnemonic keys are not operational.
ΓòÉΓòÉΓòÉ 2.1. Code server setup utility container ΓòÉΓòÉΓòÉ
The Code server setup utility container is displayed at invocation of the setup
utility. The code server setup utility container provides access to all other
functions supported by the setup utility.
Controls:
Menu Bar - The panel menu bar provides two options:
o Setup - provides a single sub-option.
Open as->Settings - Opens the Code Server Setup Container settings
notebook.
o Help-> - provides sub-options of help information for the setup utility
and code server setup container operations.
- User guide - displays Cassetup user guide contents.
- About - displays ABOUT panel.
Container - is initialized to contain two objects:
o Applications - by double clicking on this object the Applications
Container is opened.
o Code Servers - by double clicking on this object the Code Servers
Container is opened.
ΓòÉΓòÉΓòÉ 2.1.1. Code server setup - settings notebook ΓòÉΓòÉΓòÉ
The code server setup settings notebook contains a single page containing a
single field. The Persistent storage path field permits the user to define the
location where the setup utility storage information is to reside.
This field is required and is defaulted to <user_install_path> at installation.
ΓòÉΓòÉΓòÉ 2.2. Applications Container ΓòÉΓòÉΓòÉ
The applications container displays icons representing all applications for
which profiles where detected in the path defined by the "Application profile
directory path" attribute contained within the Applications Container settings
notebook.
The application profile directory path is defaulted to <user_install_path> at
installation.
The Application Profile File defines the processing logic necessary for the
setup utility to install application images, to generate LAN CID Utility
casprep files and generate client boot diskettes.
Controls:
Menu Bar - The panel menu bar provides two options:
o Applications - provides a single sub-option.
Open as -> Settings opens the Applications Container - settings notebook.
o Help provides on-line help information on the operation of the
applications container.
Container - Selecting one of the icons representing an application and dragging
the icon onto a "code server" object contained within the Code
Servers Container invokes the application Image load processing.
Double clicking on one of the icons opens the Application settings
notebook for the application.
ΓòÉΓòÉΓòÉ 2.2.1. Applications container - settings notebook ΓòÉΓòÉΓòÉ
The settings notebook provides a single page containing a single attribute.
The Application profile directory path attribute permits the setup utility user
to define where the application profile information resides.
Note: Changes to this field do not take affect until the utility is stopped
and restarted.
ΓòÉΓòÉΓòÉ 2.2.2. Application - settings notebook ΓòÉΓòÉΓòÉ
The settings notebook provides a single page displaying key attributes for the
application.
Name - Application name (i.e; title).
Profile - file specification of application profile.
Nick Name - Application unique nick name.
Package - define the mode Application, Fix (i.e; CSD's).
Type - defines the type of application
o Operating System
o Transport
o Redirector
o Other
Maintenance System required - a yes or no indication of whether or not a
maintenance system is required in order to install this
application.
Note: All fields are displayed "read only". The source for updating the
attributes shown within this notebook are keyword/values sets contained in
Application Profile File.
ΓòÉΓòÉΓòÉ 2.3. Code Servers Container ΓòÉΓòÉΓòÉ
The code server container displays a hierarchical ("tree") view of a code
server object and any applications which have been loaded on the code server.
By double clicking on an object (Code Server or Application) a settings
notebook for the object is displayed:
o Code Server settings notebook
o Code Server Application settings notebook
The code server container menu bar provides two options:
Selected - defines that the sub-menus are enabled or disabled based on the
object type selected.
If a code server object is selected, the following are enabled:
o Open as -> Settings - opens the Code Server settings notebook
o Create client (boot) diskettes - displays the Create Client (boot)
Diskettes dialog.
o SRVIFS/LAN CID utility support - displays three sub-menus
- Load - invokes Load SRVIFS/LAN CID utility support.
This sub-menu is disabled, if SRVIFS is currently loaded on the code
server.
- Remove - invokes the Removal of SRVIFS redirection support from the
code server.
This sub-menu is disabled, if SRVIFS is not curently loaded on the Code
Server.
- Configure - generates a new updated "SERVICE.INI" file, containing the
current SRVIFS settings and the current alias definitions.
This sub-menu is disabled, if SRVIFS is not curently loaded on the Code
Server.
The configuration updates do not take affect until the "SRVIFS" server
is stopped and restarted.
o Code server report - displays the Code Server Report Generation dialog,
which permits the generation/display of an output report defining the
attributes of the code server and applications loaded on the code server.
o Create Casprep/Command files - displays the LAN CID Utility
casprep/command files dialog, which permits the selection of applications
to include in the generated casprep file and an option to convert a
casprep file into a command file.
If an application object is selected, the following are enabled:
o Open as -> Settings - opens the Code Server Application settings notebook
o Remove Application images - removes the application Images from the code
server. Application images are removed from a code server by selecting the
application icon from the code server hierarchical tree and then selecting
the "Remove application images" option from the code server container
menu-bar.
An intermediate popup is displayed requesting confirmation that the
application images are to be removed. The user may cancel the remove
operation via this popup or elect to continue.
ΓòÉΓòÉΓòÉ 2.3.1. Code Server - settings notebook ΓòÉΓòÉΓòÉ
The code server (object) settings notebook defines attributes for the operation
of the code server.
Six notebook pages are displayed and each notebook page contains common
pushbuttons:
o Apply - causes any changes made to the notebook page attributes to be
validated and stored.
o Undo - resets any changes to the notebook page attributes to the value
assigned during the last notebook store.
o Help - displays help information on the contents and operation of the
notebook.
The six notebook pages are:
(1). Server - defines code server definition information.
Code server title - defines the title of the code server used within the
graphical displays. The title is free-form text and may
contain "^" symbols to indicate the placement of line feeds.
This permits the title to display as multiple lines.
Code server name - defines the name by which the code server is known to
the setup utility. It is specified as an eight (8) character
NETBIOS name by which this server will be known on the network.
If this name does not apply to a group of servers, the name
must be unique on your logical LAN network. If changed and
SRVIFS/LAN CID utility support has been loaded then the code
servers container menu bar option "SRVIFS/LAN CID utility ->
Configure" must be executed in order for the changes to be
applied to the SRVIFS Server.
Name applies to group of servers- Denotes (via checkbox) whether or not
the name applies for a group of servers or not. Selecting this
value provides for multiple servers with the same name,
allowing more than one server to provide the same service. If
changed and SRVIFS/LAN CID utility support has been loaded then
the code servers container menu bar option "SRVIFS/LAN CID
utility -> Configure" must be executed in order for the changes
to be applied to the SRVIFS server.
(2). Defaults
Default application image load alias - defines the default alias assigned
to the application image load directory, during the drag/drop
of an application object onto a code server.
Note: This default can be overridden during the application
image load processing.
Alias definitions - (push button) invokes the Client access Alias
definitions dialog. This dialog is used to define or delete
Alias definition information.
(3). NIF
Network Interface File specification - defines the fully qualified file
specification of the NIF (Network Interface File) list. This
list is used to define the valid NIF files used by the setup
utility in the user selection of and generation of Client boot
diskettes.
(4). Client - defines code server client access information.
Alias - (Log, Response, Work, DLL) defines the alias used to access the
four (4) types of directory structures used during redirected
installation processing.
o Log - defines where logging information is to be written.
o Response - defines where application response file information is
accessed during redirected installation processing.
o Work - defines where application image "work" files (i.e; exe's) are
accessed during redirected installation or during image load
processing.
o Dll - defines where application image "DLL" files are accessed
during redirected installation or during image load processing.
Directory per Client - (yes / no radio buttons) defines whether a
sub-directory for each client is to be created as a
sub-directory descendant from the "Root directory". The
sub-directory name will be the client name. If changed and
SRIFS/LAN CID utility support has been loaded then the code
servers container menu bar option "SRVIFS/LAN CID utility ->
Configure" must be executed in order for the changes to be
applied to the SRVIFS server.
Alias definitions (pushbutton) - invokes the Client access alias
definitions. This dialog is used to define or delete alias
definition information.
(5). Command
Command file Alias - provides a selection list of available Alias
definitions to establish the client access point to command
file information.
Command file path - defines the directory path from the "command file
alias" used to fully qualify the client access point to command
file information.
Alias definitions (pushbutton) - invokes the Client access alias
definitions. This dialog is used to define or delete alias
definition information.
(6). SRVIFS - defines SRVIFS configuration settings.
Maximum number of sessions - specifies maximum number of clients that are
allowed to concurrently connect to this server per adapter.
Maximum number of open files - specifies the maximum number of files that
the server may have open concurrently.
This value should be at least as large as the number of maximum
clients that are expected to attach. In some cases, a single
client may have more that one file open at a time, in which
case you may want to specify a value equivalent to 3 to 4 files
per client.
Maximum number of threads - defines the number of threads used to support
workstation requests. For large networks (20 or more concurrent
clients), a value of 12 is recommended. For small networks, a
value of 6 is recommended.
Adapter number - specifies the adapter to be used by the SRVIFS server
program.
If any of these values are changed and SRVIFS/LAN CID Utility support has been
loaded then the code servers container menu bar option "SRVIFS/LAN CID utility
-> Configure" must be executed in order for the changes to be applied to the
SRVIFS server.
ΓòÉΓòÉΓòÉ 2.3.2. Client access alias definitions ΓòÉΓòÉΓòÉ
The Client access alias definitions dialog is used to create or remove existing
alias definitions.
Alias names - a combination selection list and entry field is provided to
permit the selection of or definition of an alias name. When an
alias is selected the "Selected alias information" fields are
updated to reflect the current settings for the selected alias.
Selected alias information - these fields are used to display the current
settings for a selected alias and they are used to define settings
during alias creation.
o Drive - specifies the drive that is to be represented by the alias.
Note: The drive must be accessible by the machine on which the setup
utility is executing.
o Path - specifies the path (subdirectory) that is to be represented by
the alias.
Note: The path will be created if it does not exist.
o Read only (checkbox) - specifies whether clients can write to the
subdirectories represented by this alias. The default is "Read write"
permitting the client to both read and write information to the alias
subdirectories.
New (pushbutton) - is used to create a new alias using the alias name
entered within the "Alias name" entry field and the information
entered within the "Selected alias information" fields.
The alias specifies how the "drive" and "path" is to be accessed
by clients.
Note: The alias name must be unique.
Delete (pushbutton) - is used to delete the selected alias. Note: The alias
can not be deleted if it is selected as the alias to be used for:
(1). The code server Defaults "application image access alias".
(2). One of the code server Client "access information definition"
alias'.
(3). Referenced by an application loaded on the code server or used
during the load of SRVIFS/LAN CID utility support.
Note: If SRVIFS has been loaded, then either the New and Delete pushbuttons
will cause generation of a new SRVIFS SERVICE.INI file, containing the current
SRVIFS settings and alias definitions. The configuration updates do not take
affect until the SRVIFS server is stopped and restarted.
ΓòÉΓòÉΓòÉ 2.3.3. Code server application - settings notebook ΓòÉΓòÉΓòÉ
The code server application settings notebook contains two pages, both of which
contain information only for reference purposes (i.e; read-only), with the
exception of the Application title.
The values displayed within this notebook are obtained from the application
profile, reference Application Profile File.
The pages are:
Application
Application title - the name (i.e; title) used in the display of the
selected application.
Note: This is the only field within this notebook that is
updatable.
Profile- the fully qualified file specification of the profile
containing the logic to load the application images.
Reference Application Profile File for definition of Profiles.
Nick name - the (short) nick name of the application. This value is used
in the creation of sub-directories used by the setup utility.
Note: this field is read-only, it can only be updated via
updating the applications profile.
Load method - defines whether or not the application images were loaded
onto the code server via the setup utility or if the setup
utility user only registered that the images were previously
loaded on the server.
Load date - the date on which the Application Images were either loaded
or registered as loaded on the code server.
Paths
Application code server paths - display the alias and directory
information established for the application to be accessed by
client workstations. The following types are displayed.
o Image - defines where application images are loaded.
o Work - defines where application image "work" files (i.e; exec's)
are accessed during redirected installation or during image load
processing.
o Dll - defines where application image "DLL" files are accessed
during redirected installation or during image load processing.
o Response - defines where application response file information is
accessed during redirected installation processing.
o Log - defines where logging information is to be written.
ΓòÉΓòÉΓòÉ 2.3.4. Create client (boot) diskettes ΓòÉΓòÉΓòÉ
The create client (boot) diskette dialog permits the setup utility user to
create a set of bootable diskettes which can be used by clients to remotely
install applications from this code server.
The dialog fields are:
Target drive - defines the output drive for the Diskette generation.
Configuration - presents a selection list of the "Create Client" diskette
script files. In order for these files to appear in the list they
must be located within the setup utility directory as specified
within Code Server Setup Container settings notebook. The files
define the diskette generation execution steps for placing the
operating system, redirection support and necessary transport
mechanisms on the diskettes.
Additionally, details on the selection can be displayed by
pressing the "Display" push button, located beneath the selection
list. The details display presents additional information on the
script files.
Session timeout double - defines that the default session timeout factor 15
seconds is to be doubled to 30 seconds. This increase is useful
in cases where the LAN is bridged by slower line speeds, such as
LAN-to-LAN WAN or a remote bridge.
Client information .. ID method - specifies how this client will be
identified by this code server. A drop down selection list of
available methods for Client identification is presented:
o Automatic will allow any client to use these boot diskettes. The
client name will be determined during the connection process, and the
default response files will be used. This option should not be
selected if the default code server configuration has been modified to
include a client authorization list.
o Client - these boot diskettes will establish a remote install session
using the specified client name. If the default code server
configuration has been modified to include a client authorization list,
then the client's name must appear in the AUTHLIST file.
o Prompt - will prompt the user at the workstation for a client name
during installation.
Client information ... Name - defines the Client workstation name used when
the Client information ID method is "Client".
Client information ... Adapter selection Type - presents a drop down list of
the type of adapters known to the setup utility. The drop down
list is created from an input file CASNIF.LST. This file is
supplied at the installation of setup utility. The file contains
definition of the NIF files supplied with the IBM Multi-Protocol
Transport Support (MPTS) installation. The file format is:
<nif_file_name> <nif_file_description>
: : :
<nif_file_name> <nif_file_description>
Reference Code Server settings notebook NIF page for file
definition.
Note: NTS/2 may not support all of the adapters in the list. If
you are building boot diskettes with NTS/2, ensure that you select
an adapter type that NTS/2 supports. If you select an adapter
type that NTS/2 does not support, the boot diskettes will not be
created successfully.
Client information ... Adapter Selection Number- to be used by the Client
redirection support.
ΓòÉΓòÉΓòÉ 2.3.5. Load SRVIFS/LAN CID utility support ΓòÉΓòÉΓòÉ
The Load SRVIFS support dialog is presented when the user selects a code server
Object and via the menu-bar selection requests the load of SRVIFS.
The dialog contains three fields:
SRVIFS server target path - defines the path on the code server where the
SRVIFS support is to be loaded.
Source image path - defines the drive/path where the SRVIFS/LAN CID utility
support images reside.
SRVIFS client/LAN CID utility target - defines the target for installation the
SRVIFS client and LAN CID utility command file support software.
o Alias- provides a drop down list, permitting the user to select the Alias
to be used as the mount point to the target information.
o Path - provides an entry field to define the path, from the Alias, to the
target information. Note: A pushbutton "Alias definitions" is provided to
display Client access alias definitions dialog which permits
definition of new aliases.
The user is presented the option to cancel the SRVIFS load operation if
desired.
Note: All code server SRVIFS configuration parameters, contained within the
code server object settings notebook, are tested for valid values prior to the
load being executed.
ΓòÉΓòÉΓòÉ 2.3.6. Create Casprep/Command files ΓòÉΓòÉΓòÉ
The Create LAN CID Utility casprep/command files dialog is presented when the
user selects a code server object and via the menu-bar selection requests
Create Casprep/Command files.
The dialog contains two fields:
Select applications to include - presents a selection list of the applications
loaded on the code server. The user may select one or multiple
applications to include in the file generated. The selections display
(1). the application's icon, (2). the applications name and (3). the
target path to which the application will be loaded on the client.
Note: The user can update the "target path" prior to generating the
casprep file. The target path is updated by (1). holding down the
"Alt" key, (2). by pointing to the application records target path
entry and (3). pressing the selection key. A input entry field is
displayed permitting updates to the field. After completion of
target path update press the numeric pad enter key in order to insure
that the updates are recorded.
Generated casprep file - defines the target output file specification for the
generated casprep file.
Two pushbutton options are available:
Casprep - invokes generation of a LAN CID Utility Casprep file. When the
user presses the button the setup utility determines whether or not a second
dialog is displayed. This dialog is used to provide information for the
process to create a maintenance system to enable the installation of one of
the included applications. The determining factors on whether or not the
second dialog is displayed are:
o Do any of applications selected to be included within the casprep file
require a maintenance system, as defined by the applications profile?
o Has an operating system or Operating system fix level been chosen to be
included with the applications for which the casprep file is being
created? If so, the second dialog is displayed, but only to permit
definition of the client workstation boot drive and maintenance system
drive.
The contents of this second dialog are:
Boot drive - defines the client workstation boot drive.
Maintenance system drive - define the client workstation maintenance
system drive.
Operating system levels - provides a selection list of Operating
Systems for which images have been loaded on the code
server.
Command - displays a standard file dialog permitting the selection of a
casprep file to be converted into a LAN CID Utility command file.
ΓòÉΓòÉΓòÉ 2.3.7. Code server report ΓòÉΓòÉΓòÉ
The code server report option permits the generation of a report defining the
current settings of the code server and key characteristics of the applications
loaded or registered as existing on the code server.
A dialog is presented to the user which allows the user to:
o Define the output report name and location (path).
o Generate the output report.
o Browse an output report file.
The format of the report output is as follows:
Report Format | Report Field Description
******************************************** |
* Date: 29 Jun 1994 Time: 14:49:34 | Date & Time last updated
******************************************** |
|
Code_Server | Code Server
Title = My Code Server | Title
Name = CODESRV | Network name
Group = 0 | Group of servers ( 0=No,1=Yes)
|
Alias = READW | Alias - name
Drive = C: | Alias - drive
Path = \CID | Alias - path
RO_Flag = 0 | Alias - 0=ReadWrite
|
Alias = READONLY | Alias - name
Drive = C: | Alias - drive
Path = \CID | Alias - path
RO_Flag = 1 | Alias - 1=ReadOnly
|
Redirection_Supported = SRVIFS | Redirection Type (ref. note 2)
SRVIFS_Server_path = C:\CID\SERVICE | Server Path
LCU_Alias = READONLY | LAN CID utility alias
LCU_path = \CID | LAN CID utility Path
Maximum_Open_files = 100 | Server - Max. Open Files
Maximum_Open_sessions = 1 | Server - Max. open sessions
Maximum_threads = 10 | Server - Max. threads
Adapter_number = 0 | Server - Adapter number
Client_drive = C: | Server - Client access drive
Directory_per_client = 1 | Server - 1=Dir per Client
Work_dir_alias = READONLY | Server - Work dir Alias
DLL_dir_alias = READONLY | Server - DLL dir Alias
Log_dir_alias = READW | Server - Log file dir Alias
Response_dir_alias = READONLY | Server - Rsp file dir Alias
Command_dir_alias = READONLY | Server - Cmd file dir Alias
Command_directory = CLIENT | SRVIFS - Cmd file dir path
|
Application = LS4.0 Base | Application - title
Nick_name = LS40B | Appl - Nick name
Image_Alias = READONLY | Appl - Image dir Alias
Image_directory = IMGDIR | Appl - Image dir path
Work_directory = EXE\LS40B | Appl - Work dir path
DLL_directory = DLL\LS40B | Appl - DLL dir path
Rsp_directory = RSP\LS40B | Appl - Rsp file dir path
Log_directory = LOG\LS40B | Appl - Log file dir path
Profile = C:\CID\LS40B.PRO | Appl - Profile
Package = Application | Appl - "Application"|"Fix"
Fix_to = | Appl - Fixto (nick name)
Fix_level = | Appl - Fix Level
Progtype = other | Appl - (ref. note 3)
Maintsys_reqd = 0 | Appl - 1=Maint. system reqd, 0=No
Load_prereqs = OS211,<LCU> | Appl - Prereqs nickname(s)
Load_method = Loaded | Appl - "Loaded"|"Registered"
Load_date = June 28, 1994 | Appl - date loaded or Registered
|
Note:
1. The report generation program appends output to the end of the specified
output file.
2. The redirection supported information is only written to the report, if the
support is installed on the code server.
3. TYPE values ... "Operating System", "Transport", "Redirector" or "other".
ΓòÉΓòÉΓòÉ 2.3.8. Application image load ΓòÉΓòÉΓòÉ
When an application icon is dragged from the applications container onto a code
server object within the code servers container, this dialog is displayed in
order to permit the user to specify the characteristics of the operation.
The attributes contained on this dialog are:
Application - an entry field containing the title of the application being
dropped.
Operation - radio button selections of "Load" or "Register".
o Load - indicates that the application image load process, as defined
within the application profile, is to be executed. This execution copies
the images onto the code server image directory path.
o Register - indicates that the application images have been previously
loaded onto the code server storage and that the operation is only to
record where the images reside. The application image load process is not
executed if the operation type is "Register".
Nick name - defines a unique key for identifying the application on the code
server. This is a readonly field.
Image source .. Path - defines the location of the application source images.
Targets - defines the target Alias and Path for:
o Image - defines where application images are loaded.
o Work - defines where application image "work" files (i.e; exe's) are
accessed during redirected installation or during image load processing.
o Dll - defines where application image "DLL" files are accessed during
redirected installation or during image load processing.
o Response files - defines where application response file information is
accessed during redirected installation processing.
o Log files - defines where logging information is to be written.
Note:
1. The alias information for all, but the application image target, are
only displayed. These aliases are established in the Code Server
settings notebook on the "Client" page.
2. The application image alias is defaulted based on the default setting in
the Code Server - settings notebook within the "Server - Defaults" page.
The default selection can be changed by selecting a new alias from the
drop down list.
3. A pushbutton ("Alias definitions") is provided to display the current
aliases defined for the server and to permit creation of new or deletion
of existing alias information.
4. The target path information can be changed for all of the target types,
by typing over the defaults displayed. The default paths, if not defined
in the application profile, are generated as follows:
Type Default
----- --------------------------
image IMG\<app_nickname>
work EXE\<app_nickname>
dll DLL\<app_nickname>
response files RSP\<app_nickname>
log files LOG\<app_nickname>
The user is given the option to cancel the processing if desired.
ΓòÉΓòÉΓòÉ 2.3.8.1. Processing considerations ΓòÉΓòÉΓòÉ
o Application alias information, alias name and path, can not be changed once
an application is loaded onto the code server. You should insure the alias
is correct prior to executing the application image load processing.
o When loading an application which is defined as a "Fix" (i.e; a Corrective
Server Diskette .. CSD) the application for which the fix is to be applied
must be loaded on the code server prior to the image load of the fix
application.
ΓòÉΓòÉΓòÉ 3. Server utility - file definitions ΓòÉΓòÉΓòÉ
The setup utility uses ASCII files as both input definitions (profiles) and
output storage mechanisms. The following sections contain definitions of the
file formats and uses.
ΓòÉΓòÉΓòÉ 3.1. Code server persistent storage file ΓòÉΓòÉΓòÉ
The setup utility's persistent storage for code server attributes contains the
following:
File Format | Definition
******************************************** |
** Code Server Setup Utility |
** |
** Date last written: 29 Jun 1994 | Date last updated
** Time last written: 14:49:33 | Time last updated
******************************************** |
Server. | Server section START
srvname=CODESERVER | Server - name
srvgroup=0 | Server - 1=Group
imgalias=READONLY | Server - Default Image Alias
nifpath=c:\ibmcom\macs | Server - NIF file dir. path
srvicon=CASSETUP:#108 | Server - Display Bitmap file
srvtitle=my server | Server - title
firstflag=1 | Server - 1=Not first time execution
Alias. | Alias section START
aliasname=READW | Alias - name
aliasdrive=C: | Alias - drive letter
aliaspath=\CID | Alias - path
aliasro=0 | Alias - 1=RO/0=RW
endalias. | Alias section END
Srvifs. | SRVIFS section START
srvifsflag=1 | SRVIFS - 1=Installed,0=Not
maxfiles=100 | SRVIFS - Maximum open files
maxsessions=1 | SRVIFS - Maximum open sessions
maxthreads=10 | SRVIFS - Maximum threads
adapterno=0 | SRVIFS - Server adapter number
clientdrive=c | SRVIFS - client access drive
cidpath= | SRVIFS - client access path
diraccess= | SRVIFS -
perclient=1 | SRVIFS - 1=Dir per Client
serverpath=C:\CID\SERVICE | SRVIFS - Server path
LCUpath=\CID | SRVIFS - LAN CID utility path
LOGAlias=READW | SRVIFS - Log dir alias
RSPAlias=READONLY | SRVIFS - Response file alias
CMDAlias=READONLY | SRVIFS - Command file dir alias
WRKAlias=READONLY | SRVIFS - Work file dir alias
DLLAlias=READONLY | SRVIFS - DLL file dir alias
LCUalias=READONLY | SRVIFS - LAN CID utility alias
Cmddir=Client | SRVIFS - Command file directory
Endsrvifs. | SRVIFS section END
SrvApp. | Server Application section START
appname=LS4.0 Base | Appl - title
appicon=CASSETUP:#113 | Appl - Display Bitmap
appdir=IMGDIR | Appl - Image directory
appflag=Loaded | Appl - "Loaded"|"Registered"
appdate=June 28, 1994 | Appl - Load/Register Date
appwrkdir=EXE\LS40B | Appl - Work directory
apppro=C:\CID\LS40B.PRO | Appl - Profile
appnick=LS40B | Appl - Nick name
apppackage=1 | Appl - Package Type
appfixto= | Appl - Fix to <nick name>
appfixlvl= | Appl - Fix level
appprogtype=4 | Appl - 1=OS, 2=Trans, 3=redir, 4=other
appmaintsys=0 | Appl - 1=Maint. sys reqd, 0=No
appdlldir=DLL\LS40B | Appl - Dll directory
apprspdir=RSP\LS40B | Appl - Response file director
applogdir=LOG\LS40B | Appl - Log file directory
appalias=READONLY | Appl - Image Alias
loadprereqs= | Appl - Prerequisite applications
EndsrvApp. | Server Application section END
Endserver. | Server section END
************* end of storage file ********** | End of file Indicator
Note: The keywords may not appear in the order presented, but will appear in
the indicated sections.
ΓòÉΓòÉΓòÉ 3.2. Server utility definition file ΓòÉΓòÉΓòÉ
The setup utility maintains a definition file permitting the utility to be
invoked with the same attributes as were in affect the last time the utility
was operated. The attributes maintained in this file are:
File Format | Definition
**************************************** |
** Dated: 2 Jun 1994 Time: 09:14:15 | date and time last written
**************************************** |
* Storage / file definitions |
NISTDIR= c:\cid | Setup Utility storage path
STORFILE= cassetup.str | Code Server storage file
STORBKU= cassetup.bku | Code Server storage backup file
STORTMP= cassetup.$$$ | Temporary file
MSGFILENAME= cassetup.msg | Setup utility Message file
RPTFILE= cassetup.rpt | Code Server report file
DOCFILE= cassetup.inf | Code Server online documentation
FILESTORE= E:\CID | Server persistent storage location
PROFDIR= E:\CID | Application profile discovery path
NIFLIST= E:\CID\CASNIF.LST | NIF file list
* SRVIFS parameter Ranges & defaults |
SRVIFSF= cassetup.SRV | SRVIFS storage file
MINSESS= 1 | SRVIFS minimum sessions value
MAXSESS= 100 | SRVIFS maximum sessions value
DEFSESS= 1 | SRVIFS default sessions value
MINFILES=100 | SRVIFS minimum open files value
MAXFILES=9999 | SRVIFS maximum open files value
DEFFILES=100 | SRVIFS default open files value
MINTHRDS=2 | SRVIFS minimum threads value
MAXTHRDS=12 | SRVIFS maximum threads value
DEFTHRDS=6 | SRVIFS default threads value
MINADAP= 0 | SRVIFS minimum adapter value
MAXADAP= 1 | SRVIFS maximum adapter value
DEFADAP= 0 | SRVIFS default adapter value
* Code server setup defaults |
APPICON=CASSETUP:#102 | Default Application Icon
* Internal display attributes |
APPCNTR= nn nn nn nn | Application Container size & position
NISTCNTR= nn nn nn nn | Setup Container size & position
SERVERCNTR= nn nn nn nn | Server Container size & position
Note: The keywords may not appear in the order presented.
ΓòÉΓòÉΓòÉ 3.3. Application profile file ΓòÉΓòÉΓòÉ
The Application profiles are used to define to setup utility how specific
operation and presentation is to be handled for an application.
The file format is as follows:
Note: Blank lines or lines with the first non-blank character being an
asterisk (*) are considered comments and ignored.
APPNAME=
This is a long descriptive name. It can contain blanks. It should
be unique among all the Application profiles.
APPNICK=
This is a short nickname. It is used to identify this application in
other scripts and profiles. It must be unique among all the
Application profiles. Case is ignored for this parameter.
APPDIR=
This is the sub-directory (relative the to CID mount point) where the
applications install images will be stored. The directory will be
created if it does not exist.
WORKDIR=
This is a sub-directory (relative the to CID mount point) where
various application required programs may be placed. It is optional.
The directory will be created if it does not exist.
DLLDIR=
This is a sub-directory (relative the to CID mount point) where
application DLL files may be placed. It is optional. The directory
will be created if it does not exist.
RESPDIR=
This is a sub-directory (relative the to CID mount point) where
application response files are located.
LOGDIR=
This is a sub-directory (relative the to CID mount point) where
application log files are located.
ICON=
This is the icon to be displayed within the Graphical User Interface
(GUI) to represent the application.
Note: Due to a restriction within the case tool used to create the
GUI, this field must contain the name of a BMP file in one of two
formats. Either (1). <filename>.BMP or (2). <DLL_name>#<offset>.
NUMDSKT=
This is the number of diskettes in the package. It is optional,
unless the XCOPY method is being used.
METHOD=
Methods are 1=XCOPY-is-used, 2=Application-provides-program to move
install images onto the code server.
COPYSUBDIR=
If method=1, this says whether sub-directories should be copied. The
values are Y=yes, N=no.
XDISKETTE.<num>=
When METHOD=1, the XDISKETTE keywords specify how each diskette will
be prompted for and verified.
XDISKETTE.1.0Prompt = Diskette 1
XDISKETTE.1.0VolSer = Prod Diskette 1
XDISKETTE.2.0Prompt = Diskette 2
IMAGELOAD.<num> -
If METHOD=2, this is a template for the command line that will be
executed to move the code images from diskette or CDROM to the code
server. Templates may contain symbolic substitution parameters,
which will be replaced by actual values when the command line is
executed. The symbolic substitutions supported for COPYCMDLINE are:
o $T - is replaced by the target path (the path to which the code images are
to be moved).
o $S - is replaced by the source drive and possibly path, from which the
code images will be copied.
o $W - is replaced by the fully-qualified path of the work directory.
o $D - is replaced by the fully-qualified path of the DLL directory.
o $F - is replaced by the fully-qualified path of the work directory of the
application being fixed. Valid only for Fixes.
Example:
IMAGELOAD.0 = 1
IMAGELOAD.1 = kimage /S=$S /T=$T
OS=
This tells whether the program runs under OS/2 (1) or DOS (2).
PACKAGE=
This tells whether it is a complete application (1) or a fix (2).
FIXTO=
If it is a fix, this names the APPNICK of the application it fixes.
FIXLEVEL=
This specifies the relative fix level. It can be -1 to indicate it
is an unsequenced fix.
---------------------------------
SETUP.= this is not a real keyword. It is used as a place holder to
describe the uses of the "SETUP." keywords. These keywords are
indexed by step and are used to define how to extract the programs
and other resources that may be needed to manipulate the application
code images. The typical kinds of things that need to be unpackaged
are:
o programs needed to decompress and extract bundled files.
o programs and files used to create code server code images.
o programs and files used to create book diskettes. The file extraction is
done as a series of steps. Each step consists of an optional prompt,
followed by one or more commands.
SETUP.0=
Defines how many steps there are.
SETUP.1=
This tells what diskette to prompt for. If it is blank, then there
is no prompt.
SETUP.1.0Volser=
If there is a diskette prompt, then the diskette can be verified
either by VolSer or presence of a file.
SETUP.1.0MarkerFile=
If there is a diskette prompt, then the diskette can be verified
either by VolSer or presence of a file.
SETUP.1.0=
For each step, there can be as many commands as needed. This
parameter tells how many commands.
SETUP.1.1=
This parm gives the first command, in the form of a command line
template.
SETUP.1.0GOODRC =
If the commands do not follow normal zero-means-good return code
policy, this entry can be added to show what the good return codes
are.
SETUP.2 =
Here is the prompt for the second diskette needed.
Note: This is just an illustration that all of the keyword entries
as "STEPUP.1" can occur multiple times with different index numbers.
---------------------------------
The next section deals with the type of application being described,
and, for certain types of applications, the steps needed to build a
maintenance system (and, in particular, boot diskettes).
PROGTYPE=
This tells what kind of application this is: Operating System (1),
Transport (2), Redirector(3), or other (4).
INSTCMD= klrinst $S $T /R=$R\$C.rsp
The command used to install the package is next, the sumbolic
substitutions are $S, $T $W and $D, as well as $L (log dir)
o $B - boot drive
o $M - Maint directory
o $R - response file directory
o $V - server name
o $F - directory for the /S2 parm
o $C - client name
MAINTSYSREQ=
This tells if a maintenance system is required or not (1 is yes, 0
no)
MAINTSYSBUILD=<ordinal>
If the progtype is 1, 2 or 3, the application must provide a way to
build a maintenance system. The programs needed to do this must be
extracted in the SETUP steps above. Typically, they will be placed in
the application's WORKDIR. The value is the ordinal of the mscmd
structure(s) that defines how a maintenance system is build with this
application.
Commands that may need to be executed to install the product in a
maintenance system are identified by ordinal. Symbolic substitution
on these command lines include $T, $W, $D and $S. Further
substitutions may be specified in other files. For example, Boot
Diskette Build scripts specify may specify other substitutions.
MSCmd.0 = 1
specifies the number of steps necessary.
MSCmd.1 = dcopy something something
defines the command string to execute.
MSCmd.1.0CmdName = dcopy
defines a command to execute.
MSCmd.1.0GoodRc = 7
defines valid (Good) return code values from the command to execute.
ΓòÉΓòÉΓòÉ 4. Code server setup error messages ΓòÉΓòÉΓòÉ
The following sections define the error messages which are generated from setup
utility These messages are displayed in popup dialog boxes when encountered
during execution.
The error text in the following sections may contain indicators that "variable"
(i.e; run time) substitution of values within the error message will take
place. These substitutions are indicated by %n, were "n" is a number.
ΓòÉΓòÉΓòÉ 4.1. CAS0002E: Unable to open Code Server Setup profile (%1) return code (%2). ΓòÉΓòÉΓòÉ
Number: CAS0002E
Text: Unable to open Code Server Setup profile (%1) return code (%2).
Profile is required to continue, terminating utility.
Cause: The Code Server Setup profile cannot be located or is damaged.
Action: Insure that the path to the profile is valid and the drive is
accessible. If the profile has been damaged, then a reinstall of
CASSETUP is required. If a backup of the profile exists, rename the
damaged one, copy in the backup, and restart the utility.
ΓòÉΓòÉΓòÉ 4.2. CAS0004E: A "configuration" selection is required. ΓòÉΓòÉΓòÉ
Number: CAS0004E
Text: A "configuration" selection is required.
Cause: A "configuration" selection is required.
Action: Select a configuration.
ΓòÉΓòÉΓòÉ 4.3. CAS0005E: Server name (SRVNAME=) value missing for entry within file (%1). ΓòÉΓòÉΓòÉ
Number: CAS0005E
Text: Server name (SRVNAME=) value missing for entry within file (%1).
Cause: The server name (SRVNAME=) value is missing from the file identified
by the replacement text variable (%1).
Action: Check to insure that the Code Server storage file has not been
corrupted. If it has, a backup storage file was created the last
time the code server utility was executed. This file has an
extension of ".BKU" and is contained in the code server storage
directory.
ΓòÉΓòÉΓòÉ 4.4. CAS0006E: SRVIFS flag (SRVIFSFLAG=) value missing for entry within file (%1). ΓòÉΓòÉΓòÉ
Number: CAS0006E
Text: SRVIFS flag (SRVIFSFLAG=) value missing for entry within file (%1).
Cause: The SRVIFS flag (SRVIFSFLAG=) value is missing from the file
identified by the replacement text variable (%1).
Action: Check to insure that the code server storage file has not been
corrupted. If it has, a backup storage file was created the last
time the code server utility was executed. This file has an
extension of ".BKU" and is contained in the code server storage
directory.
ΓòÉΓòÉΓòÉ 4.5. CAS0007E: Application name (APPNAME=) value for entry within storage file, defaulted to nick name (%1). ΓòÉΓòÉΓòÉ
Number: CAS0007E
Text: Application title (APPNAME=) value missing for entry within storage
file, defaulted to nickname (%1).
Cause: The application title (APPNAME=) value is missing for entry within
storage file.
Action: Default action applied. To correct name open Code Server settings
notebook and update title.
ΓòÉΓòÉΓòÉ 4.6. CAS0009E: Application profile variable PROGTYPE= value (%1) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0009E
Text: Application profile variable PROGTYPE= value (%1) is invalid.
o Value must be 1, 2, 3 or 4.
Application profile (%2) must be corrected before this application
can be performed.
Note: the setup utility must be stopped and restarted to apply
profile changes.
Cause:
Action: Edit the profile and correct the PROGTYPE= variable. Then stop /
restart the setup utility in order to appy the changes.
ΓòÉΓòÉΓòÉ 4.7. CAS0010E: Storage file %1 can not be accessed (rc=%2). ΓòÉΓòÉΓòÉ
Number: CAS0010E
Text: Storage file %1 can not be accessed (rc=%2).
Check that the storage path (%3) is correct.
Cause: The storage file identified by the first replacement text variable
(%1) cannot be accessed. The return code has been return in the
second replacement text variable (%2).
Action: Insure that the path to the storage path is valid and the drive is
accessible.
ΓòÉΓòÉΓòÉ 4.8. CAS0015E: LAN CID utility casprep file path (%1) is invalid or can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0015E
Text: LAN CID utility casprep file path (%1) is invalid or can not be
accessed.
Cause: LAN CID utility casprep file path (%1) is invalid or can not be
accessed.
Action: Insure that the path to the path is valid and the drive is
accessible.
ΓòÉΓòÉΓòÉ 4.9. CAS0016E: No Applications selected for LAN CID utility casprep file output. ΓòÉΓòÉΓòÉ
Number: CAS0016E
Text: No Applications selected for LAN CID utility casprep file output.
Cause: At least one application must be selected before the LAN CID utility
casprep file can be built.
Action: Select an application to be included in the casprep file. If you
there are no applications in the list, then you must go back and
setup the code server with the application. This involves dragging
and dropping application icons from the applications container window
on the server icon in the code server container window.
ΓòÉΓòÉΓòÉ 4.10. CAS0017E: Generate LAN CID utility casprep file ended in error rc=(%1). ΓòÉΓòÉΓòÉ
Number: CAS0017E
Text: Generate LAN CID utility casprep file ended in error rc=(%1).
Cause: The LAN CID utility casprep file could not be generated. The failure
return code has been returned in the replacement text field (%1).
Action: Retry the operation. If the condition persists, contact IBM with the
message number and return code value.
ΓòÉΓòÉΓòÉ 4.11. CAS0018E: An error was encountered removing application (%1) images. ΓòÉΓòÉΓòÉ
Number: CAS0018E
Text: An error was encountered removing application (%1) images.
The following directories should have been deleted:
Cause: An error was encountered while removing an application's (%1) images.
Action: Retry the operation. If the condition persists, try to remove the
images manually.
ΓòÉΓòÉΓòÉ 4.12. CAS0019E: An error was encountered reading the configuration file (%1) rc=(%2). ΓòÉΓòÉΓòÉ
Number: CAS0019E
Text: An error was encountered reading the configuration file (%1) rc=(%2).
The utility is unable to display details of the configuration file.
Cause: An error was encountered reading the configuration file (%1) rc=(%2).
The first replacement text variable identifies the configuration file
and the second replacement text variable identifies the failure
return code.
Action: Retry the operation. If the condition persists, contact IBM with the
message number and return code.
ΓòÉΓòÉΓòÉ 4.13. CAS0041E: Error encountered creating Client (boot) diskettes, rc=(%1). ΓòÉΓòÉΓòÉ
Number: CAS0041E
Text: Error encountered creating Client (boot) diskettes, rc=(%1).
Cause: An error was encountered while attempting to create a set of client
boot diskettes. The failure return code is return in the replacement
text (%1).
Action: Retry the operation. If the condition persists, contact IBM with the
message number and return code.
ΓòÉΓòÉΓòÉ 4.14. CAS0042E: Error encountered loading SRVIFS support on code server, rc=(%1). ΓòÉΓòÉΓòÉ
Number: CAS0042E
Text: Error encountered loading SRVIFS support on code server, rc=(%1).
Cause: An error was encountered while trying to load the SRVIFS support on
the code server. The replacement text (%1) identifies the return
code.
This message can be ignored. There will always be a more descriptive
message preceding this one that will identify the problem more
specifically.
Action: After correcting the error condition, retry loading the SRVIFS
support again. If the condition persists, contact IBM with the all
errors that were encountered during the load prior to this message.
ΓòÉΓòÉΓòÉ 4.15. CAS0043E: Target path (%1) can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0043E
Text: Target path (%1) can not be accessed.
Cause: The target path, identified by the replacement text (%1), can not be
accessed.
Action: Insure that target path is valid and the target drive is accessible.
ΓòÉΓòÉΓòÉ 4.16. CAS0044E: Source path (%1) can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0044E
Text: Source path (%1) can not be accessed.
Cause: The source path, identified by the replacement text (%1), can not be
accessed.
Action: Insure source path is valid and the source drive is accessible.
ΓòÉΓòÉΓòÉ 4.17. CAS0045E: Target path is required. ΓòÉΓòÉΓòÉ
Number: CAS0045E
Text: Target path is required.
Cause: The target path has been omitted and is required.
Action: Enter target path.
ΓòÉΓòÉΓòÉ 4.18. CAS0046E: Source path is required. ΓòÉΓòÉΓòÉ
Number: CAS0046E
Text: Source path is required.
Cause: The source path has been omitted and is required.
Action: Enter source path.
ΓòÉΓòÉΓòÉ 4.19. CAS0047E: Code Server path (%1) can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0047E
Text: Code Server path (%1) can not be accessed.
Cause: The code server path, identified by the replacement text (%1), cannot
be accessed.
Action: Insure that code server path is valid and the drive is accessible.
ΓòÉΓòÉΓòÉ 4.20. CAS0048E: Remove SRVIFS support failed with a return code of (%1). ΓòÉΓòÉΓòÉ
Number: CAS0048E
Text: Remove SRVIFS support failed with a return code of (%1).
Cause: An error was encountered while trying to remove the SRVIFS support on
the code server. The replacement text (%1) identifies the return
code.
This message can be ignored. There will always be a more descriptive
message preceding this one that will identify the problem more
specifically.
Action: After correcting the error condition, retry removing the SRVIFS
support again. If the condition persists, try deleting the SRVIFS
support manually.
ΓòÉΓòÉΓòÉ 4.21. CAS0049E: SRVIFS removal was requested, but SRVIFS has not been loaded. ΓòÉΓòÉΓòÉ
Number: CAS0049E
Text: SRVIFS removal was requested, but SRVIFS has not been loaded.
Cause: SRVIFS removal was requested, but SRVIFS has not been loaded.
Action: Close the code server container and then reopen. If the SRVIFS
"remove" option is still enabled then the utilities storage records
may have been corrupted.
o Generate and review the Code Server report to insure that the records are
correct.
o If correct, update the code server persistent storage file by changing the
"SRVIFSFLAG=" value from 1 to 0. Zero ("0") indicates that SRVIFS has not
been loaded.
ΓòÉΓòÉΓòÉ 4.22. CAS0050E: Target drive is required input. ΓòÉΓòÉΓòÉ
Number: CAS0050E
Text: Target drive is required input.
Cause: Target drive is required input.
Action: Enter target drive letter.
ΓòÉΓòÉΓòÉ 4.23. CAS0051E: Target drive (%1) is invalid or can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0051E
Text: Target drive (%1) is invalid or can not be accessed.
Note: Target drive must be either "A:" or "B:".
Cause: Target drive (%1) is invalid or can not be accessed.
Action: Insure that target drive is valid and accessible.
ΓòÉΓòÉΓòÉ 4.24. CAS0052E: Error when Client Identification Method = "CLIENT" then Client name is required. ΓòÉΓòÉΓòÉ
Number: CAS0052E
Text: Error when Client Identification Method = "CLIENT" then Client name
is required.
Cause: This error was issued because the Client Identification Method was
selected as "CLIENT" and the Client name was not specified.
Action: Enter Client name and push "apply" button.
ΓòÉΓòÉΓòÉ 4.25. CAS0053E: Invalid Maximum Session number (%1). ΓòÉΓòÉΓòÉ
Number: CAS0053E
Text: Invalid Maximum Session number (%1).
The value must be between (%2) and (%3).
Update Code Server Settings notebook "SRVIFS" page.
Cause: Invalid Maximum Session number (%1).
The value must be between (%2) and (%3).
Action: Select a valid number of open files and push "apply" button.
ΓòÉΓòÉΓòÉ 4.26. CAS0054E: Invalid Files open number (%1). ΓòÉΓòÉΓòÉ
Number: CAS0054E
Text: Invalid Files open number (%1).
The value must be between (%2) and (%3).
Update Code Server Settings notebook "SRVIFS" page.
Cause: Invalid Files open number (%1).
The value must be between (%2) and (%3).
Action: Select a valid number of open files and push "apply" button.
ΓòÉΓòÉΓòÉ 4.27. CAS0055E: Invalid Maximum Threads number (%1). ΓòÉΓòÉΓòÉ
Number: CAS0055E
Text: Invalid Maximum Threads number (%1).
The value must be between (%2) and (%3).
Update Code Server Settings notebook "SRVIFS" page.
Cause: Invalid Maximum Threads number (%1).
The value must be between (%2) and (%3).
Action: Select a valid number of open threads and push "apply" button.
ΓòÉΓòÉΓòÉ 4.28. CAS0056E: Code server path (%1) is invalid or can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0056E
Text: Code server path (%1) is invalid or can not be accessed.
Cause: Code server path, identified by the replacement text (%1), is not
valid or can not be accessed.
Action: Insure that code server path is valid and accessible.
ΓòÉΓòÉΓòÉ 4.29. CAS0057E: Code server name is a required field. ΓòÉΓòÉΓòÉ
Number: CAS0057E
Text: Code Server name is invalid or blank.
Cause: The code server name is not valid or it has been omitted.
Action: Enter code server name and push "apply" button.
ΓòÉΓòÉΓòÉ 4.30. CAS0058E: Code server client default access drive is a required field. ΓòÉΓòÉΓòÉ
Number: CAS0058E
Text: Code server client default access drive is a required field.
Cause: Code server client default access drive is a required field.
Action: Enter default access drive and push "apply" button.
ΓòÉΓòÉΓòÉ 4.31. CAS0059E: Attempting to load "FIX" for Application (%1) which has not been loaded. ΓòÉΓòÉΓòÉ
Number: CAS0059E
Text: Attempting to load "FIX" for Application (%1) which has not been
loaded.
Primary Application must be loaded prior to "FIX".
Cause: Attempting to load "FIX" for Application (%1) which has not been
loaded.
Action: Cancel image load operation for the "FIX" and load Application
images for the Application to which the fix will be applied prior to
loading the "Fix".
ΓòÉΓòÉΓòÉ 4.32. CAS0060E: Code server setup "Persistent Storage path" is a required field. ΓòÉΓòÉΓòÉ
Number: CAS0060E
Text: Code server setup "Persistent Storage path" is a required field.
Cause: Code server setup "Persistent Storage path" is a required field.
Action: Either input a valid path specification (drive and path) or press
"Undo" button to reset value.
ΓòÉΓòÉΓòÉ 4.33. CAS0061E: Code server setup "Persistent Storage path" (%1) can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0061E
Text: Code server setup "Persistent Storage path" (%1) can not be accessed.
Cause: Code server setup "Persistent Storage path" (%1) can not be accessed.
Action: Insure storage path field is valid and that the drive is accessible.
ΓòÉΓòÉΓòÉ 4.34. CAS0062E: Adapter number is a required field. ΓòÉΓòÉΓòÉ
Number: CAS0062E
Text: Adapter number is a required field.
Update Code Server Settings notebook "SRVIFS" page.
Cause: Adapter number is a required field.
Action: Select adapter number on Code server settings notebook "SRVIFS" page.
ΓòÉΓòÉΓòÉ 4.35. CAS0063E: Application Nick name is missing from application profile. ΓòÉΓòÉΓòÉ
Number: CAS0063E
Text: Application nick name is missing from application profile. Load
process is unable to proceed.
Cause: Application nick name is missing from application profile.
Action: Correct the application profile. You must then stop and restart the
code server utility.
ΓòÉΓòÉΓòÉ 4.36. CAS0066E: Application nick name (%1) is not unique. ΓòÉΓòÉΓòÉ
Number: CAS0066E
Text: Application nick name (%1) is not unique.
Application (%2) has the same nick name.
Cause: Application nick name (%1) is not unique. Application (%2) has the
same nick name.
Action: Enter valid unique nick name.
ΓòÉΓòÉΓòÉ 4.37. CAS0067E: Application nick name (%1) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0067E
Text: Application nick name (%1) is invalid.
Nick name must not contain the following characters:
"." (. "." (period), ":" (colon),
"\" (. "\" (slash), " " (blank)
"?" (. "?" (question mark), "%" (percent sign)
Cause: Application nick name (%1) is not valid.
Action: Correct profile APPNICK= variable to reflect a valid nick name.
Note: The setup utility must be stopped and restarted in order to
appy profile changes.
ΓòÉΓòÉΓòÉ 4.38. CAS0069E: Unable to generate LAN CID utility casprep file ΓòÉΓòÉΓòÉ
Number: CAS0069E
Text: Unable to generate LAN CID utility casprep file
An Application was included which requires a maintenance system.
No Operating System was selected for maintenance system.
Cause: Unable to generate LAN CID utility casprep file. An Application was
included which requires a maintenance system. No Operating System
was selected for maintenance system.
Action: Select operating system.
ΓòÉΓòÉΓòÉ 4.39. CAS0070E: Unable to generate LAN CID utility casprep file ΓòÉΓòÉΓòÉ
Number: CAS0070E
Text: Unable to generate LAN CID utility casprep file
The Client boot drive letter (%1) is invalid.
Cause: Unable to generate LAN CID utility casprep file. The Client boot
drive letter (%1) is not valid.
Action: Enter a valid client boot drive letter.
ΓòÉΓòÉΓòÉ 4.40. CAS0071E: Unable to generate LAN CID utility casprep file ΓòÉΓòÉΓòÉ
Number: CAS0071E
Text: Unable to generate LAN CID utility casprep file
The Maintenance system drive letter (%1) is invalid.
Cause: Unable to generate LAN CID utility casprep file. The Maintenance
system drive letter (%1) is not valid.
Action: Enter valid maintenance system drive letter.
ΓòÉΓòÉΓòÉ 4.41. CAS0072E: LAN CID utility target drive is required. ΓòÉΓòÉΓòÉ
Number: CAS0072E
Text: LAN CID utility target drive is required.
Cause: LAN CID utility target drive is required.
Action: Enter target drive.
ΓòÉΓòÉΓòÉ 4.42. CAS0073E: The Code Server DRIVE (%1) defined in the Code Server Settings Notebook is invalid or blank. ΓòÉΓòÉΓòÉ
Number: CAS0073E
Text: The Code Server DRIVE (%1) defined in the Code Server Settings
Notebook is invalid or blank.
The SRVIFS/LAN CID utility load operation requires this field.
Cause: The Code Server DRIVE (%1) defined in the Code Server Settings
Notebook is invalid or blank.
Action: Enter a valid drive.
ΓòÉΓòÉΓòÉ 4.43. CAS0074E: Code Server Alias is a required field. ΓòÉΓòÉΓòÉ
Number: CAS0074E
Text: Code Server Alias is a required field.
Cause: Code Server Alias is a required field.
Action: Select a valid Code server alias.
ΓòÉΓòÉΓòÉ 4.44. CAS0075E: Alias (%1) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0075E
Text: Alias (%1) is invalid.
Alias must be composed of only characters A-Z, a-z or 0-9 and can not
be blank.
Cause: The specified Alias is not valid. The Alias must be composed of only
characters A-Z, a-z or 0-9 and can not be blank.
Action: Enter valid alias name.
ΓòÉΓòÉΓòÉ 4.45. CAS0077E: Alias drive (%1) is invalid or not accessible. ΓòÉΓòÉΓòÉ
Number: CAS0077E
Text: Alias drive (%1) is invalid or not accessible.
Cause: Alias drive (%1) is invalid or not accessible.
Action: Enter valid alias drive letter. If valid, insure that network access
to the drive is enabled.
ΓòÉΓòÉΓòÉ 4.46. CAS0078E: Alias name duplicates and existing alias name (%1). ΓòÉΓòÉΓòÉ
Number: CAS0078E
Text: Alias name duplicates and existing alias name (%1).
Cause: Alias name duplicates and existing alias name.
Action: Enter valid, unique, alias name.
ΓòÉΓòÉΓòÉ 4.47. CAS0079E: Alias name (%1) can not be deleted. ΓòÉΓòÉΓòÉ
Number: CAS0079E
Text: Alias name (%1) can not be deleted.
It is used by Application (%2).
The Alias is necessary in order to access the Applications
information.
Cause: The Alias name cannot be deleted because it is being by by an
Application. The Alias is required to access the Application
information.
Action: Cancel delete attempt.
ΓòÉΓòÉΓòÉ 4.48. CAS0080E: Alias name (%1) can not be deleted. ΓòÉΓòÉΓòÉ
Number: CAS0080E
Text: Alias name (%1) can not be deleted.
It is used within the Code Server Settings for Client (%2) access.
The Alias is necessary in order to access Application information.
Cause: The Alias name cannot be deleted. It is used within the Code Server
Settings for Client access. The Alias is required to access
Application information.
Action: Cancel delete attempt.
ΓòÉΓòÉΓòÉ 4.49. CAS0081E: Alias name (%1) can not be deleted. ΓòÉΓòÉΓòÉ
Number: CAS0081E
Text: Alias name (%1) can not be deleted or changed.
It is used within the Code Server Settings for Client (%2) access.
The Code Server Settings can be updated and then the Alias can be
deleted as no application images have been loaded.
Cause: The Alias name cannot be deleted or changed. It is used within the
Code Server Settings for Client access. The Code Server Settings can
be updated and then the Alias can be deleted as no application images
have been loaded.
Action: Cancel delete attempt.
ΓòÉΓòÉΓòÉ 4.50. CAS0082E: Alias name (%1) can not be deleted. ΓòÉΓòÉΓòÉ
Number: CAS0082E
Text: Alias name (%1) can not be deleted.
It is used within the Code Server Settings as the default image
alias.
Change the default value and then the Alias can be deleted.
Cause: The Alias name cannot be deleted. It is used within the Code Server
Settings as the default image alias. Change the default value and
then the Alias can be deleted.
Action: Cancel delete attempt.
ΓòÉΓòÉΓòÉ 4.51. CAS0083E: Application container "Profile directory path" (%1) can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0083E
Text: Application container "Application Profile directory path" (%1) can
not be accessed.
o Insure that the drive is accessible.
o Insure that the paths are valid and exist.
Cause: The application container "Application Profile directory path" that
was entered cannot be accessed.
Action: Insure that the paths are valid and exist and that the drive is
accessible.
ΓòÉΓòÉΓòÉ 4.52. CAS0085E: Unable to generate LAN CID Utility command file. ΓòÉΓòÉΓòÉ
Number: CAS0085E
Text: Unable to generate LAN CID Utility command file.
o One or both of the required files can not be located.
o The files, CASPREP.CMD and CASBASE.FIL should be located within
directory (%1).
Cause: Unknown
Action: Locate the required files and copy them to the indicated directory.
ΓòÉΓòÉΓòÉ 4.53. CAS0086E: Target path is invalid or can not be accessed. ΓòÉΓòÉΓòÉ
Number: CAS0086E
Text: Target path is invalid or can not be accessed.
o Alias (%1)
o Path (%2)
o Directory (%3)
Cause: The target path is not valid or can not be accessed.
Action: Insure that the paths are valid and exist and that the drive is
accessible.
ΓòÉΓòÉΓòÉ 4.54. CAS0089E: Unable to build SRVIFS configuration "ini" file (%1). ΓòÉΓòÉΓòÉ
Number: CAS0089E
Text: Unable to build SRVIFS configuration "ini" file (%1).
Cause: Unable to build SRVIFS configuration "ini" file (%1).
Action: Check to insure that the file is not read-only.
ΓòÉΓòÉΓòÉ 4.55. CAS0090E: Boot drive field (%1) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0090E
Text: Boot drive field (%1) is invalid.
Boot drive field is required.
Cause: Boot drive field cannot be ommitted. It is required.
Action: Enter a boot drive.
ΓòÉΓòÉΓòÉ 4.56. CAS0091E: Unable to access Code Server report (%1). ΓòÉΓòÉΓòÉ
Number: CAS0091E
Text: Unable to access Code Server report (%1).
Insure that the report file specification is valid.
Cause: The Code Server report could not be accessed.
Action: Insure that the report file specification is valid.
ΓòÉΓòÉΓòÉ 4.57. CAS0108E: Target path (%2) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0108E
Text: Target path (%2) is invalid for Application (%1).
o Path can not be for drive "A" or "B"
o Path can not contain characters: /:*"<>|,+=[];&?
Cause: The target path is not valid. Either a drive of "A" or "B" was
specified or one of the following characters was found in the target
path: slash(/), colon(:), asterisk(*), double quote("), left
angle(<), right angle(>), vertical bar (|), comma(,), plus(+),
equal(=), left bracket([), right bracket(]), semicolon(;),
ampersand(&), or question mark(?).
Action: Correct the path and proceed.
ΓòÉΓòÉΓòÉ 4.58. CAS0109E: Path (%1) is invalid, insure that it is only path information. ΓòÉΓòÉΓòÉ
Number: CAS0109E
Text: Path (%1) is invalid, insure that it is only path information.
o Path can not contain characters: /:*"<>|,+=[];?&
Cause: The target path is not valid.
Action: Correct the path and proceed.
ΓòÉΓòÉΓòÉ 4.59. CAS0110E: Failure in creating backup copy prior to updating storage file. ΓòÉΓòÉΓòÉ
Number: CAS0110E
Text: Failure in creating backup copy prior to updating storage file.
Insure that the drive and path access to (%1) are valid and that the
storage directory has storage space.
Press "YES" button to retry or "NO" button to cancel the storage
operation.
Note: If the storage operation is canceled, all records of updates
made since the utility was lasted stored will be lost.
Cause: There was a failure while creating a backup copy of the storage file.
Action: Insure that the drive and path access is valid and that the storage
directory has storage space. Press the "YES" button to retry or the
"NO" button to cancel the storage operation. Note that if the
storage operation is canceled, all records of updates made since the
utility was lasted stored will be lost.
ΓòÉΓòÉΓòÉ 4.60. CAS0112E: Unable to access or create Server directory (%1). ΓòÉΓòÉΓòÉ
Number: CAS0112E
Text: Unable to access or create Server directory (%1).
Cause: Unable to access or create Server directory.
Action: Insure path information is correct and retry.
ΓòÉΓòÉΓòÉ 4.61. CAS0113E: Field (%1) does not contain a fully qualified path. ΓòÉΓòÉΓòÉ
Number: CAS0113E
Text: Field (%1) does not contain a fully qualified path.
Cause: A fully qualified path was not specified.
Action: Insure path information is correct and retry.
ΓòÉΓòÉΓòÉ 4.62. CAS0115E: Unable to make subdirectory (%1) within path (%2). ΓòÉΓòÉΓòÉ
Number: CAS0115E
Text: Unable to make subdirectory (%1) within path (%2).
Cause: A subdirectory could not be made within the path.
Action: Insure path information is correct and retry.
ΓòÉΓòÉΓòÉ 4.63. CAS0116E: Unable to make / change to drive within target path (%1). ΓòÉΓòÉΓòÉ
Number: CAS0116E
Text: Unable to make / change to drive within target path (%1).
Cause: Unable to make / change to drive within target path.
Action: Insure path information is correct and retry.
ΓòÉΓòÉΓòÉ 4.64. CAS0117E: Unable to change to drive within target path (%1). ΓòÉΓòÉΓòÉ
Number: CAS0117E
Text: Unable to change to drive within target path (%1).
Cause: Unable to change to drive within target path.
Action: Insure drive is valid and accessible.
ΓòÉΓòÉΓòÉ 4.65. CAS0118E: Alias name (%1) can not be deleted. ΓòÉΓòÉΓòÉ
Number: CAS0118E
Text: Alias name (%1) can not be deleted.
It is used as the LAN CID utility alias established during SRVIFS/LAN
CID utility load.
The Alias can not be deleted while SRVIFS/LAN CID utility support is
loaded.
Cause: Alias name (%1) can not be deleted.
Action: You must first remove all references to the alias before it can be
deleted. Once you have done this, retry the delete.
ΓòÉΓòÉΓòÉ 4.66. CAS0119E: Adapter type selection is required. ΓòÉΓòÉΓòÉ
Number: CAS0119E
Text: Adapter type selection is required.
Cause: Adapter type selection is required.
Action: Select and adapter type and then submit.
ΓòÉΓòÉΓòÉ 4.67. CAS0120E: Drive (%1) is either not valid or not accessible. ΓòÉΓòÉΓòÉ
Number: CAS0120E
Text: Drive (%1) is either not valid or not accessible.
Cause: The specified drive is either not valid or not accessible.
Action: Insure drive is valid and accessible.
ΓòÉΓòÉΓòÉ 4.68. CAS0121E: Unable to access path (%1), insure path is valid and exists. ΓòÉΓòÉΓòÉ
Number: CAS0121E
Text: Unable to access path (%1), insure path is valid and exists.
Cause: Unable to access the specified path.
Action: Insure path is valid and exists.
ΓòÉΓòÉΓòÉ 4.69. CAS0122E: Unable to access code server report file (%1). ΓòÉΓòÉΓòÉ
Number: CAS0122E
Text: Unable to access code server report file (%1).
Cause: Unable to access code server report file.
Action: Insure path / file are valid and exist.
ΓòÉΓòÉΓòÉ 4.70. CAS0123E: Error encountered writing code server report file (%1). ΓòÉΓòÉΓòÉ
Number: CAS0123E
Text: Error encountered writing code server report file (%1).
Insure that sufficient space is available for the report file.
Cause: An error was encountered writing to the code server report file.
Action: Insure that sufficient space is available for the report file. Retry
the operation.
ΓòÉΓòÉΓòÉ 4.71. CAS0124E: Target path (%1) is invalid. ΓòÉΓòÉΓòÉ
Number: CAS0124E
Text: Target path (%1) is invalid.
o Target path can not be either drive "A" or "B".
Cause: The target path is not valid. It cannot be drive "A" or "B".
Action: Enter a valid drive and retry the operation.
ΓòÉΓòÉΓòÉ 4.72. CAS0125E: Alias (%1) can not be found, check alias definitions. ΓòÉΓòÉΓòÉ
Number: CAS0125E
Text: Alias (%1) can not be found, check alias definitions.
Cause: The Alias was not found.
Action: Verify that a valid Alias has been used and then retry the operation.
ΓòÉΓòÉΓòÉ 4.73. CAS0126E: Error encountered saving the code server setup persistent storage file. ΓòÉΓòÉΓòÉ
Number: CAS0126E
Text: Error encountered saving the code server setup persistent storage
file.
The last operation executed will not be recorded within the storage
file.
Insure that sufficient disk space is available for the storage file
(%1) prior to attempting other operations.
Cause: Error encountered saving the code server setup persistent storage
file.
Action: Insure that sufficient disk space is available for the storage file
(%1) prior to attempting other operations.
ΓòÉΓòÉΓòÉ 4.74. CAS0128E: Code server title can not be blank. ΓòÉΓòÉΓòÉ
Number: CAS0128E
Text: Code server title can not be blank.
Cause: Code server title can not be blank.
Action: Specify a code server title.
ΓòÉΓòÉΓòÉ 4.75. CAS0129E: Command line too long. ΓòÉΓòÉΓòÉ
Number: CAS0129E
Text: The combination of command line parameters is greater than the valid
length (%1).
The operating system command processor can not execute this command.
o This situation is caused by long paths derived from Aliases and
subdirectories.
Cause: The combination of command line parameters is too long.
Action: Make the combinations shorter until it can fit within the specified
limit.
ΓòÉΓòÉΓòÉ 4.76. CAS0130E: File read failure. ΓòÉΓòÉΓòÉ
Number: CAS0130E
Text: Unable to read NIF file list (%1).
NIF file list is used to define the available Network Interface Files
in order to provide "Adapter selection Types".
Cause: Unable to read NIF file list.
Action: Verify that the file has not been damaged and retry the operation.
ΓòÉΓòÉΓòÉ 4.77. CAS0134E: The program was invoked with a bad command line... ΓòÉΓòÉΓòÉ
Number: CAS0134E
Text: The program was invoked with a bad command line: caseng1 %1. Correct
invocation is CASENG1 /S=src /T=tgt /W=wkdir /P=prof /D=dlldir
/F=fixdir.
Cause: CASSETUP created an invalid command line to invoke CASENG1.
Action: Determine why an incorrect command line was created and retry.
ΓòÉΓòÉΓòÉ 4.78. CAS0136E: The file %1 is not a valid application profile ΓòÉΓòÉΓòÉ
Number: CAS0136E
Text: The file %1 is not a valid Application profile
Cause: The CASSETUP database contains an Application Profile name that is
not a valid application profile.
Action: Correct the database and retry.
ΓòÉΓòÉΓòÉ 4.79. CAS0138E: RexxUtil could not be loaded on this machine. ΓòÉΓòÉΓòÉ
Number: CAS0138E
Text: RexxUtil could not be loaded on this machine. It may not have been
installed during operating system installation, or REXXUTIL.DLL may
not be in a LIBPATH directory.
Cause: REXX was not properly installed on this workstation.
Action: Install REXX on this workstation and retry.
ΓòÉΓòÉΓòÉ 4.80. CAS0141E: An error occurred executing %1 ΓòÉΓòÉΓòÉ
Number: CAS0141E
Text: An error occurred executing %1 The return code was %2
Cause: As indicated by the return code
Action: See the recommended action for the return code from the indicated
command. Often the cause is an invalid command line. More
information about the error may appear in the window where it ran.
ΓòÉΓòÉΓòÉ 4.81. CAS0151E: The application to be applied to the diskettes, %1... ΓòÉΓòÉΓòÉ
Number: CAS0151E
Text: The application to be applied to the diskettes, %1, is not loaded on
this code server.
Cause: CASSETUP's database does not contain sufficient data about the
application.
Action: Correct the database and retry.
ΓòÉΓòÉΓòÉ 4.82. CAS0153E: The application profile %1 was not found ΓòÉΓòÉΓòÉ
Number: CAS0153E
Text: The application profile %1 was not found.
Cause: The CASSETUP database contains the name of an application profile,
but the file can not be found.
Action: Correct the database, or put the file in the expected place, and
retry.
ΓòÉΓòÉΓòÉ 4.83. CAS0155E: Could not find the images directory %1 for application %2 ΓòÉΓòÉΓòÉ
Number: CAS0155E
Text: Could not find the images directory %1 for application %2
Cause: The CASSETUP database contains the name of the image directory for
the application, but the directory was not found.
Action: Correct the database or move the images to the indicated directory.
ΓòÉΓòÉΓòÉ 4.84. CAS0162E: Data specified for the command line /S parameter was wrong ΓòÉΓòÉΓòÉ
Number: CAS0162E
Text: Data specified for the command line /S parameter was either missing
or incorrect. Data specified was %1
Cause: CASSETUP generated an invalid Script parameter for the Create client
boot diskettes command line.
Action: Make a different choice for the type of diskettes to build and retry.
ΓòÉΓòÉΓòÉ 4.85. CAS0163E: Data specified for the command line /D parameter was wrong ΓòÉΓòÉΓòÉ
Number: CAS0163E
Text: Data specified for the command line /D parameter was either missing
or incorrect. Data specified was %1
Cause: CASSETUP generated an invalid DLL Path parameter for the Create
client boot diskettes command line. This may be because the
indicated directory has been removed.
Action:. Determine why the path was not found. Reloading or registering the
install images for the version of the operating system being put on
the diskettes may help.
ΓòÉΓòÉΓòÉ 4.86. CAS0164E: No data was specified for the command line /T parameter. ΓòÉΓòÉΓòÉ
Number: CAS0164E
Text: No data was specified for the command line /T parameter.
Cause: CASSETUP generated an incorrect Target value for the Create client
boot diskettes command line.
Action: Enter another target drive and retry.
ΓòÉΓòÉΓòÉ 4.87. CAS0165E: The Boot Diskette Build script file %1 contains no commands. ΓòÉΓòÉΓòÉ
Number: CAS0165E
Text: The Boot Diskette Build script file %1 contains no commands.
Cause: The script file corresponding to your selection of type of diskette
to build has been overwritten or corrupted. It contains no
instructions on how to build the boot diskettes.
Action: Restore the correct file and retry.
ΓòÉΓòÉΓòÉ 4.88. CAS0167E: SRVIFS must be loaded on the code server before boot diskettes can be created ΓòÉΓòÉΓòÉ
Number: CAS0167E
Text: SRVIFS must be loaded on the code server before boot diskettes can be
created
Cause: An attempt was made to build boot diskettes before SRVIFS had been
loaded onto the code server.
Action: Load SRVIFS onto the code server using CASSETUP.
ΓòÉΓòÉΓòÉ 4.89. CAS0170E: Fatal Error ΓòÉΓòÉΓòÉ
Number: CAS0170E
Text: %1 failed with rc=%2 at %3 in %4.
Cause: An internal error condition has been detected that caused some
portion of load or remove to fail. The first replacement text
variable (%1) will indicate which component failed. The second
replacement text (%2) will indicate the return code from that
component. The third replacement text (%3) will indicate a source
line number where the error was detected. The fourth replacement
text (%4) will indicate which component detected the error (i.e.,
CASENG2 or CASENG4).
Action: Retry the load or remove. If the condition does not go away, then
contact an IBM representative with the information associated with
this message.
ΓòÉΓòÉΓòÉ 4.90. CAS0180E: Invalid Version ΓòÉΓòÉΓòÉ
Number: CAS0180E
Text: The operating system for the code server has to be at IBM OS/2
version 2.0 or greater.
Cause: The operating system is not at the required level.
Action: The correct version of the OS/2 operating system must be installed.
The version must be 2.0 or greater.
ΓòÉΓòÉΓòÉ 4.91. CAS0181E: Insert Diskette ΓòÉΓòÉΓòÉ
Number: CAS0181E
Text: The source path does not contain the Redirected Installation Support
programs (for example, \APPLETS\MPTSAPLT.ZIP). Please insert the one
of the following diskettes into drive source drive:
* MPTS Utilities Diskette (diskette 3)
* NTS/2 Utilities diskette (WR07060 or later)
* NTS/2 Service Pak WR07060 Bonus Pak diskette
Or, select the Cancel pushbutton and correct the source path.
Cause: The source path specified in the Load SRVIFS/LAN CID Utility Support
window did not contain the MPTS Utilities, the NTS/2 Utilities
(WR07060 or later), or the NTS/2 Service Pak WR07060 Bonus Pak
diskette image.
Action: Either locate a diskette with the MPTS Utilities (diskettes 3), the
NTS/2 Utilities diskette (WR07060 or later), or the NTS/2 Service Pak
WR07060 Bonus Pak and insert it into the source drive or cancel this
message and correct the source path.
ΓòÉΓòÉΓòÉ 4.92. CAS0183E: REXX Not Installed ΓòÉΓòÉΓòÉ
Number: CAS0183E
Text: REXX is not installed on this workstation. REXX is required for
Redirected Install Support. Before continuing, you must first
install REXX using the OS/2 installation program.
Cause: The REXX.DLL was not found on the boot drive in subdirectory OS2\DLL.
Action: REXX must be installed.
ΓòÉΓòÉΓòÉ 4.93. CAS0184E: LAPS Not Installed ΓòÉΓòÉΓòÉ
Number: CAS0184E
Text: LAPS must be installed and configured for NETBIOS for this Code
Server to be operational. Before retrying this operation use the
MPTS.EXE program on the MPTS diskette 1 or the LAPS.EXE program on
the NTS/2 LAPS diskette to install and configure LAPS.
Cause: CONFIG.SYS on the boot drive is searched for "NETBIOS.OS2". It
should be in a "DEVICE=" statement. This message is displayed if
NETBIOS.OS2 is not found.
Action: MPTS or NTS/2 must be installed and configured for NETBIOS for this
Code Server to be operational. Use the MPTS.EXE program on the MPTS
diskette 1 or the LAPS.EXE program on the NTS/2 LAPS diskette to
install and configure LAPS.
ΓòÉΓòÉΓòÉ 4.94. CAS0186E: Program Not Found ΓòÉΓòÉΓòÉ
Number: CAS0186E
Text: The PKUNZIP2.EXE program is required for the installation of
Redirected Install Support. Insert one of the following diskettes
into the source drive:
* MPTS diskette 1
* NTS/2 LAPS diskette
Cause: The PKUNZIP2.EXE program is required for the installation of the
Redirected Install Support and it was not found in the directory
where CASSETUP was installed (i.e., CASSETUP.EXE using CASINST.CMD).
It may have been deleted by mistake.
Action: Insert the MPTS diskette 1, the NTS/2 LAPS diskette, or any other
diskette which contains a copy of PKUNZIP2.EXE program into the A:
drive. If the diskette cannot be located, select the Cancel
pushbutton to cancel the load until the diskette can be located.
ΓòÉΓòÉΓòÉ 4.95. CAS0187E: Insert Diskette ΓòÉΓòÉΓòÉ
Number: CAS0187E
Text: The disk does not contain the PKUNZIP2.EXE program. Insert the
correct diskette (MPTS diskette 1 or NTS/2 LAPS diskette) into the A
drive or select the Cancel pushbutton.
Cause: The disk inserted into the A drive does not contain the PKUNZIP2.EXE
program.
Action: Insert the MPTS diskette 1, the NTS/2 LAPS diskette, or any other
diskette which contains a copy of PKUNZIP2.EXE program into the A:
drive. If the diskette cannot be located, select the Cancel
pushbutton to cancel the load until the diskette can be located.
ΓòÉΓòÉΓòÉ 4.96. CAS0188E: Insufficient Disk space ΓòÉΓòÉΓòÉ
Number: CAS0188E
Text: There are %1 bytes available on the "%2" drive. The load for this
drive requires %3 bytes. Do you want to continue with the load?
Cause: The free space on the drive where the load is to take place does not
have enough space. The first replacement text (%1) provides the
total number of bytes available on the drive. The second replacement
text (%2) provides the drive letter where the load is to occur. The
third replacement text (%3) provides the amount of space that is
required for the load to succeed.
Action: Free some space on the drive that you are trying to load on and try
the load again.
ΓòÉΓòÉΓòÉ 4.97. CAS0189E: Errors Logged ΓòÉΓòÉΓòÉ
Number: CAS0189E
Text: Refer to, %1, for an explanation of the %2 failure.
Cause: One or more errors have been detected by a program. The first
replacement text (%1) provides the path to and the name of the log
file where the errors can be found. The second replacement text (%2)
provides the name of the program that issued the errors.
Action: Look at the log file, correct the error conditions, and retry the
load.
ΓòÉΓòÉΓòÉ 4.98. CAS0194E: Maximum Path Exceeded ΓòÉΓòÉΓòÉ
Number: CAS0194E
Text: The path, %1, exceeds the maximum by %2 character(s).
Cause: The path specified is too long. The first replacement text (%1)
provides the path in error. The second replacement text (%2) provides
the number of characters by which the maximum was exceeded.
Action: Provide a shorter path.
ΓòÉΓòÉΓòÉ 4.99. CAS0196E: Incorrect Syntax ΓòÉΓòÉΓòÉ
Number: CAS0196E
Text: All of the subdirectories in path, %1, could not be created. Correct
the invalid path and retry the load.
Cause: The path specified is incorrect. The system could not create all the
subdirectories specified in the path. The replacement text (%1)
shows the path that was incorrect.
Action: Correct the path in error and retry the load.
Refer to your operating system documentation for the correct syntax
for the specific file system (e.g., FAT, HPFS) that you are using.
One possible cause might be the presence of multiple consecutive
back-slashes or periods within the path statement.
ΓòÉΓòÉΓòÉ 4.100. CAS0202E: The application needed is not on this code server ΓòÉΓòÉΓòÉ
Number: CAS0202E
Text: The application %1 which is needed for the install, is not on this
code server.
Cause: The CASSETUP database does not contain enough information about an
application selected for inclusion in the install command file.
Action: You may have to reinstall or re-register the application images with
CASSETUP.
ΓòÉΓòÉΓòÉ 4.101. CAS0204E: The input file did not specify any application profiles ΓòÉΓòÉΓòÉ
Number: CAS0204E
Text: The input file %1 did not specify any application profiles.
Cause: The applications list created by CASSETUP to tell Casprep file how to
create the install command file was empty.
Action: Select applications to be installed and retry.
ΓòÉΓòÉΓòÉ 4.102. CAS0211E: The list of programs to be installed included two operating systems ΓòÉΓòÉΓòÉ
Number: CAS0211E
Text: The list of programs to be installed included two operating systems:
%1 and %2
Cause: The applications list contains two programs which the CASSETUP
database has recorded as Operating Systems.
Action: Deselect one of the operating systems and retry.
ΓòÉΓòÉΓòÉ 4.103. CAS0214E: Incorrect or invalid information specified for cmdline ΓòÉΓòÉΓòÉ
Number: CAS0214E
Text: Incorrect or invalid information was specified for the command line
%1 parameter. Data specified was: %2
Cause: CASSETUP generated incorrect information for a portion of the CASENG6
command line
Action:. Determine the cause and retry. It may be useful to issue the command
CASENG6 /? from the command line to get some information about the
command line parameters of CASENG6.
ΓòÉΓòÉΓòÉ 4.104. CAS0218E: Drive %1 is not ready to write on. ΓòÉΓòÉΓòÉ
Number: CAS0218E
Text: Drive %1 is not ready. Press OK when it is ready.
Cause: The drive is not ready, probably because there is no diskette or
CDROM in it.
Action: Make the drive ready and press the OK button.
ΓòÉΓòÉΓòÉ 4.105. CAS0221E: Disk Full trying to write %1. ΓòÉΓòÉΓòÉ
Number: CAS0221E
Text: Disk Full trying to write %1. Free some space and press OK to
continue.
Cause: Disk full
Action: Free some space and press OK to continue or Cancel to quit.
ΓòÉΓòÉΓòÉ 4.106. CAS0222E: Unable to write %1. ΓòÉΓòÉΓòÉ
Number: CAS0222E
Text: Unable to write %1. Press OK to retry or CANCEL to end.
Cause: The disk may be write-protected, or there may be hardware trouble.
Action: Correct the problem and retry, or cancel.
ΓòÉΓòÉΓòÉ 4.107. CAS0226E: The Operating System fix level specified does not apply... ΓòÉΓòÉΓòÉ
Number: CAS0226E
Text: The Operating System fix level specified does not apply to the
version of the operating system being installed.
Cause: The user specified an operating system and an operating system fix to
be installed. The fix does not match the level of the operating
system. The FIXTO field in the Application Profile for the fix
specifies the nick name of the operating system it is for.
Action: Change selections and retry, or correct the FIXTO field in the
CASSETUP database.
ΓòÉΓòÉΓòÉ 4.108. CAS0250E: SRVIFS/LAN CID Utility Support Not Loaded ΓòÉΓòÉΓòÉ
Number: CAS0250E
Text: SRVIFS/LAN CID Utility support must be loaded prior to this
application.
Cause: The SRVIFS/LAN CID Utility support has not been loaded.
Action: Load the SRVIFS/LAN CID Utility support.
ΓòÉΓòÉΓòÉ 4.109. CAS0251E: Application Not Loaded ΓòÉΓòÉΓòÉ
Number: CAS0251E
Text: Application nick name (%1) must be loaded prior to this application.
Cause: A required application has not been loaded.
Action: Load the required application.
ΓòÉΓòÉΓòÉ 4.110. CAS0257E: LAN CID Utility command file creation ended in error (rc=%1). ΓòÉΓòÉΓòÉ
Number: CAS0257E
Text: LAN CID Utility command file creation ended in error (rc=%1).
Cause: CASPREP file contains invalid statments.
Action: Manually correct CASPREP file an retry command file creation.
ΓòÉΓòÉΓòÉ 4.111. CAS0258E: SRVIFS / LAN CID Utility must be installed prior to this operation. ΓòÉΓòÉΓòÉ
Number: CAS0258E
Text: SRVIFS / LAN CID Utility must be installed prior to this operation.
Cause: Failure to load SRVIFS / LAN CID Utility prior to current operation
Action: Load SRVIFS / LAN CID Utility support and retry operation.
ΓòÉΓòÉΓòÉ 5. Bitmaps ΓòÉΓòÉΓòÉ
The following bitmaps can be used from Application profiles by defining the
profile keyword "APPICON=" as "APPICON=CASSETUP:#<nnn>", where <nnn> is one of
the numbers defined below.
Number Bitmap
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115