| 
|  | » |  | 
 |  | This appendix describes error messages returned by the
Command Interpreter (CI) that relate to workgroups and using 
the Workload Manager.  For each message, you will see the cause or
probable cause and one or more suggestions to remedy the error. 11506
 MESSAGESHOWPROC format must be SUMMARY or DETAIL. (CIWARN 11506)
CAUSEYou entered a format name other than the two supported by the 
SHOWPROC command, SUMMARY or DETAIL.  Or, you misspelled 
one of the two format names.
ACTIONReenter the command and specify either SUMMARY or 
DETAIL as the format name.  
12201
 MESSAGEWorkgroup name already exists. (CIERR 12201)
CAUSEThe name that you specified for the new workgroup already exists.
ACTIONUse the SHOWWG command to determine whether or not 
a workgroup by that name exists. If not, check the spelling of the workgroup
name and reenter the command.  
12202
 MESSAGEWorkgroup does not exist. (CIERR 12202)
CAUSEThere is no workgroup whose name matches the name that you 
specified.
ACTIONUse the SHOWWG command to determine whether or not 
a workgroup by that name exists. If not, check the spelling of the name that 
you specified and reenter the command.
12203
 MESSAGECannot delete a system-defined workgroup. (CIERR 12203)
CAUSEYou attempted to delete one of the following workgroups,
which are defined by the system and cannot be purged:  AS_Default, 
BS_Default, CS_Default, DS_Default, and ES_Default.  
ACTIONIf you are using the Workload Manager, reenter the command and
specify the name of the user-defined workgroup that you want to delete.  If you
are not using the Workload Manager, you will always see this error message
when you issue the PURGEWG command since you cannot create user-defined
workgroups. Regardless of whether or not you are using the Workload Manager, you cannot 
create or delete the system-defined workgroups.
12204
 MESSAGELIMIT priority cannot exceed BASE. (CIERR 12204)
CAUSEThe value that you specified for the limit priority exceeds the 
value of the base priority.
ACTIONReenter the command to supply a value for limit that is 
less than or equal to the value for base.  If you do not know the
current value for base, use the SHOWWG command to display 
that information.  Remember that the value of limit must be between
150 and 255, inclusive.
12205
 MESSAGEMINQUANT and MAXQUANT values must be between 1 and 32767, inclusive. (CIERR 12205)
CAUSEThe value that you specified for the minimum quantum or the maximum 
quantum is not within the allowable limits of 1 and 32767, inclusive.
ACTIONReenter the command, specifying a value between 1 and 32767 
inclusive. Remember that the minimum quantum value must be less than or 
equal to the maximum quantum.
12206
 MESSAGEMINQUANT value cannot exceed MAXQUANT. (CIERR 12206)
CAUSEThe value that you supplied for the minimum quantum exceeds the 
value of the maximum quantum.
ACTIONReenter the command supplying a minimum quantum value that is less 
than or equal to the maximum quantum. If you do not know the current 
value of maxquant, use the SHOWWG command to display that information.
CIERR 12207
 MESSAGETIMESLICE value must be a multiple of 100 and within the 
range 100 and 32700, inclusive. (CIERR 12207)
CAUSEThe value that you specified for the timeslice is either not a 
multiple of 100 or it is not within the range of 100 and 32700, inclusive.
ACTIONReenter the command to specify a timeslice value that is a 
multiple of 100 (i.e. 200, 300, 400, ... 15100, 31900).  The smallest 
acceptable value is 100 and the largest acceptable value is 32700.
CIERR 12208
 MESSAGETotal minimum CPU percentages for all user-defined workgroups 
cannot exceed 99. (CIERR 12208)
CAUSEThe total of all the minimum CPU percentages specified for all the
user-defined workgroups exceeds 99.
ACTIONCalculate the sum of CPU percentages for all existing 
user-defined workgroups and subtract the amount from 99.  Reenter the command 
specifying a minimum CPU percentage that is equal to or less than this amount.
If the sum of the minimum CPU percentages of the existing workgroups is 
already equal 99, you cannot specify a minimum CPU percentage 
for the workgroup that you are trying to create.
CIERR 12209
 MESSAGEMAXCPUPCT value must be within 0 and 100, inclusive.
(CIERR 12209)
CAUSEThe value that you specified for maximum CPU percentage is either
less than zero, or it is greater than 100.
ACTIONReenter the command to specify a valid percentage value. Make 
sure that maxcpupct is not less than mincpupct.
CIERR 12210
 MESSAGE MINCPUPCT value must be within 0 and 99, inclusive. 
(CIERR 12210)
CAUSEThe value that you specified for minimum CPU percentage is either
less than zero, or it is greater than 99.
ACTIONReenter the command to specify a valid percentage value. Make
sure that mincpupct does not exceed maxcpupct, and that the sum of
all minimum CPU percentages is less than 100.
CIERR 12211
 MESSAGEMINCPUPCT value cannot exceed MAXCPUPCT. (CIERR 12211)
CAUSEThe value that you specified for the minimum CPU percentage is 
greater than the maximum CPU percentage.
ACTIONReenter the command to specify a minimum CPU percentage 
that is less than or equal to the maximum.  If you do not know the current
value of maxcpu, use the SHOWWG command to display
that information.
12212
 MESSAGEWorkgroup name must start with a letter or underscore and 
can contain 255 alphanumeric and underscore characters. (CIERR 12212)
CAUSEYou entered a workgroup name that is longer than 255 characters
or you entered an invalid first character.
ACTIONMake sure that the first character of the name is either a letter
or an underscore; numbers and special characters are not permitted.
Also, check the length of the workgroup name to ensure that it is less 
than or equal to 255 characters.  (The name may have
unprintable characters that are not visible on the screen but are 
included in and contribute to the length of the input.  They are 
saved as part of the command in the CI history stack; use the DO or 
REDO commands to check.)  Once you have determined the cause of the 
problem, reenter the command to specify the corrected workgroup name.
12213
 MESSAGEInvalid character in workgroup name. (CIERR 12213)
CAUSEYou entered a workgroup name that begins with a character other 
than the normal alphabet letters or underscore (_), or one that contains a
character other than a number, letter, or the underscore.
ACTIONCheck the name for illegal or unprintable characters.
(Unprintable characters are control characters that are not visible
on the screen but are included in the input.  They are saved as 
part of the command in the CI history stack use the DO or REDO 
commands to check.)  Once you have determined the cause of the problem, 
reenter the command to specify the corrected workgroup name.
12214
 MESSAGESHOWWG format must be 0, 1, 2, 3, or format name. Defaulting to 
format SUMMARY (0). (CIWARN 12214)
CAUSEYou entered a format number that is not between 0 and 3 inclusively.
ACTIONReenter the command to specify one of 0, 1, 2, 3.  Or, reenter the
command to specify one of the following format names: SUMMARY, 
WGFILE, PROCS, or DETAIL.
12215
 MESSAGENOTRUNC option is ignored for WGFILE format. (CIWARN 12215)
CAUSEYou attempted to display workgroup information in the 
WGFILE (1) format and specified the NOTRUNC option.
ACTIONReenter the command to omit the NOTRUNC option.  Or, choose
either the PROCS or DETAIL format to display 
workgroup information without truncation and specify the NOTRUNC option.
12217
 MESSAGEVALIDATE option is ignored when not specified in conjunction 
with an indirect file name. (CIWARN 12217)
CAUSEYou specified the VALIDATE option on the command line to create
or change a single workgroup.  Or, you did not enter the caret (^) 
preceding the indirect file name and the CI interpreted it as a workgroup 
name, thereby disallowing the VALIDATE option.
ACTIONEnter the command again, making sure that a caret (^) 
immediately precedes the indirect file name.  (If you do not specify this 
character, the file name will be treated as a workgroup name.)
12218
 MESSAGEOnly VALIDATE option is allowed with indirect file. Other 
parameters are ignored. (CIWARN 12218)
CAUSEYou specified the name of an indirect file on the command
line but supplied options other than VALIDATE.  Or, you preceded the
workgroup name with the caret (^), and the CI interpreted it as the
name of an indirect file.
ACTIONCheck the command line to ensure that you did not inadvertently 
enter a caret (^) with the workgroup name. Or, if you meant to supply the 
name of an indirect file, reenter the command and only specify
the VALIDATE option with that name.
12219
 MESSAGEAt least one membership criterion is required. (CIERR 12219)
CAUSEYou attempted to create a workgroup but did not specify a membership
criterion.  
ACTIONReenter the command to supply at least one of the following 
membership criteria: MEMB_LOGON, MEMB_PROGRAM, or MEMB_QUEUE.
12220
 MESSAGEPOSITION parameter is not allowed within an indirect file. 
(CIERR 12220)
CAUSEOne or more of the workgroup specifications in the indirect file 
that you supplied to the NEWWG command contain the POSITION 
parameter.
ACTIONEdit the indirect file to remove all the POSITION parameter 
specifications from the workgroup specifications. Then, reenter the 
NEWWG command.
12221
 MESSAGEVALIDATE option is not allowed within an indirect file. (CIERR 12221)
CAUSEOne or more of the workgroup specifications in the indirect file 
that you supplied to the NEWWG command contain the VALIDATE option.
ACTIONEdit the indirect file to remove all of the VALIDATE option 
entries from the workgroup specifications. Then, reenter 
the NEWWG command.
12222
 MESSAGEThe indirect file may not contain references to itself or to 
another indirect file. (CIERR 12222)
CAUSEOne or more of the workgroup specifications in the indirect file 
that you supplied to the NEWWG command contains a name that the 
CI is interpreting as indirect file instead of a workgroup.
ACTIONEdit the indirect file to remove all caret (^) characters 
that might cause a workgroup name to be interpreted as an indirect file name.
Then, reenter the NEWWG command.
12223
 MESSAGEBASE and LIMIT priorities must be specified. (CIERR 12223)
CAUSEA workgroup specification in the indirect file does not include 
values for the base priority or the limit priority, which are required.
ACTIONEdit the indirect file to add a value for base and a value for 
limit to the workgroup specification whose name appears in the text of the 
error message.
12224
 MESSAGEMPE/iX names must be fully qualified, and HFS names must be 
absolute paths. (CIERR 12224) 
CAUSEWhen specifying the MEMB_PROGRAM values, you did not fully 
qualify an MPE/iX file name or you did not enter an absolute path for an HFS
name.
ACTIONReenter the command to ensure that the MPE/iX file names contain 
both the group and account components, and that HFS names begin with a /
(denoting an absolute path.)  Remember that HFS paths which reference 
MPE/iX file names must be in all capital letters (e.g. /SYS/PUB/CI).
12225
 MESSAGENo workgroup names matched the pattern "!". (CIWARN 12225)
CAUSENone of the existing workgroup names match the pattern that you 
specified.
ACTIONCheck the order of the wildcards in the pattern to ensure that it
indicates what you intended and then reenter the command to specify the
correct wildcards.  Remember that
"#" means one numeric character, "?" means one alphanumeric 
character, and "@" means one or more alphanumeric characters.
CIERR 12226
 MESSAGEPRI and WG parameters may not be specified together.
(CIERR 12226)
CAUSEYou specified both PRI and WG parameters, and the 
ALTPROC command can accept only one of them.
ACTIONChoose which parameter you want to use and reenter the 
command to specify only that one.  Use the WG parameter to explicitly place
a process in a workgroup (where it becomes an artificial member) or to return a process to its natural workgroup.  Use the PRI parameter to alter the priority of a process. Note:  Workload Manager users should avoid using the PRI parameter, and use WG instead.
12227
 MESSAGEWG parameter requires SM capability. (CIERR 12227)
CAUSEYou cannot use the WG parameter to change the workgroup
of the specified process because you have not been assigned system manager 
(SM) capability.  
ACTIONConsult your system manager or system administrator.
12228
 MESSAGECommand does not allow wildcards in workgroup name.
(CIERR 12228)
CAUSEYou entered wildcard characters in the workgroup name specified
with the NEWWG or ALTWG commands, or with the WG= parameter of 
ALTPROC command.
ACTIONRemove any wildcards from the workgroup name and reenter the 
command.
12229
 MESSAGEPOSITION parameter does not specify a valid workgroup name. 
(CIERR 12229)
CAUSEThe workgroup name that is specified in the POSITION parameter does not exist, or it is one of the following system-defined workgroups: BS_Default, CS_Default, DS_Default, or ES_Default.
ACTIONCheck the spelling of the workgroup name to ensure that it is what
you intended.  If necessary, you can display a list of existing 
workgroup names by entering the SHOWWG command.  
Also, since you cannot place a user-defined workgroup after the system-defined
workgroups, the POSITION parameter does not accept any of the 
following workgroup names:  BS_Default, CS_Default, 
DS_Default, or ES_Default.  (You may specify the AS_Default workgroup, however,
because the workgroup you are adding will precede the workgroup you specify 
in the POSITION parameter.  So, for example, you would specify the AS_Default workgroup when you want the workgroup you are adding to be 
the last user-defined workgroup in the ordered list.)
12230
 MESSAGEThis name is reserved for a system-defined workgroup. 
(CIERR 12230)
CAUSEYou attempted to create a user-defined workgroup using one of the 
system-defined workgroup names.
ACTIONReenter the command to specify a workgroup name that 
does not match one of the system-defined workgroups: AS_Default,
BS_Default, CS_Default, DS_Default, and ES_Default or the reserved
workgroup name Natural_wg.  Although these 
workgroup names appear in mixed alphabetic case, the system reserves
these names irrespective of case.  So if you attempt to create a new workgroup
called es_default, for example, you will see this error message. 
12231
 MESSAGECannot modify the AS_Default and BS_Default workgroups. 
(CIERR 12231)
CAUSEYou attempted to redefine one or more characteristics of the 
AS_Default or the BS_Default system-defined workgroups.
ACTIONYou cannot alter the characteristics of the AS_Default and 
BS_Default workgroups. Make sure that the workgroup name is 
what you intended and reenter the command to specify the correct 
workgroup name.
12235
 MESSAGEThe Workload Manager configuration file is corrupt. Enter "HELP 
CIERR12235" for more information. (CIERR 12235)
CAUSEFor some reason, the WGCONFIG file has been corrupted.
ACTIONReboot the system and, at the ISL prompt, enter 
START NORECOVERY SINGLE-USER.  Rebooting the system in this way 
renames the corrupted WGCONFIG 
file and creates a new WGCONFIG file with the system-defined (default) 
workgroups.  Once the system is finished booting, you can use the NEWWG 
command to add user-defined workgroups to the configuration.  Once you have
done so, restart the system with your normal START command specifications.
12236
 MESSAGEIndirect file must be an ASCII file. You may use the 
WGFILE format of the NEWWG command in conjunction with I/O 
redirection to create one. (CIERR 12236) 
CAUSEThe indirect file you specified on the command line
is not an ASCII file.
ACTIONUse an editor such as EDIT/3000 to create an ASCII file that
contains the definition(s) of your user-defined workgroup(s).  You can
either create this file from scratch or, if you intend to modify the current 
configuration, you can capture the output of the SHOWWG command and
edit that.  To do so, enter SHOWWG @, WGFILE > filename. 
This creates a temporary ASCII file, of the name you specified, that contains 
the current definitions of all the workgroups that are active on your system.
12237
 MESSAGECannot rewind the indirect file for reading. (CIERR 12237)
CAUSEAn access error occured during repositioning of the record
pointer to the beginning of the indirect file.
ACTIONExamine the file to ensure that it is not corrupt, then reenter 
the command.
12238
 MESSAGEYou must purchase the Workload Manager (product # B3879AA)
before you can create any user-defined workgroups. (CIERR 12238)
CAUSEYou tried to create a user-defined workgroup without purchasing
the Workload Manager.  If you have purchased the product and you see this 
message, it is possible that one or more of its components have been corrupted.
ACTIONIf you have purchased the Workload Manager, verify that
the WLMGR.MPEXL.SYS file is intact.  If it is not, follow the steps in the installation guide to regenerate it. To purchase a copy of the Workload Manager, contact your local Hewlett-Packard
sales office.
12239
 MESSAGELogon name must be of the form "[JobSess_Name,]USER.ACCOUNT" 
where wildcards are allowed. (CIERR 12239)
CAUSEThe MEMB_LOGON parameter contains a logon name that does not 
follow the requirements of the Workload Manager logon name specification.
ACTIONInspect the logon name to ensure that each component is not more
than eight characters long and that it begins with an alphabetic character
or either the "@" or "?" wildcard characters.  (Within the logon name,
the wildcard characters "@", "?" and "#" are permitted.  
However, since names may not begin with digits, you cannot use
"#" as the first character of any of the logon components.)  Also, if the 
JobSess_Name portion of the logon is supplied, the whole name must 
be quoted so that it is treated as one entity. Otherwise, the comma separating 
JobSess_Name from USER.ACCOUNT will cause 
JobSess_Name to be treated as a logon name by itself.
12240
 MESSAGECannot change the default workgroup of a system process.
(CIERR 12240) 
CAUSEYou attempted to change the workgroup of a system
process, which is not allowed.
ACTIONUse the SHOWPROC command to make sure that
the process whose workgroup you are changing is a user process. 
If it is, verify that the PIN number that you
supplied is correct and then reenter the command. 
12241
 MESSAGECannot modify the CPU percentages of the system-defined
workgroups. (CIERR 12241) 
CAUSEYou attempted to change the CPU percentages of one of 
the AS_Default, BS_Default, CS_Default, DS_Default, or ES_Default
system-defined workgroups.  You can only change the CPU percentages 
of the user-defined workgroups.
ACTIONCheck the spelling of the workgroup name that you specified, 
keeping in mind that names are case insensitive. 
Reenter the command to supply a user-defined workgroup name.
 |