2. Invalid routine name in SVC 202 parameter list. If the routine named in the SVC 202 parameter list is invalid or cannot be fOURd, DMSITS handles the situation in the same way as it handles an error
return from a legitimateSVC routine. The error code is -3.
3. InvalidSVC 203 code. If an invalid code follows SVC 203 inline,
then an error message isdisplayed, and the abend routine is called
to terminate execution.SEARCH HIERARCHY FOR SVC 202 When a program issues SVC 202, passing a routine or command name in the
parameter list, thenDMSITS must be searched for the specified routine
or command. (In the case ofSVC 203 with a zero in the table entry for
the specified index, the same logic must be applied.)
1.
The search algorithm is as follows:
A check is made to see if there is a routine with
name currently occupying the system transient area.
case, then control is transferred there.
the specified
If this is the
2. The system function name table is searched, to see if a commandby this name is a nucleus-resident command. If the search is
successful, control goes to the specified nucleus routine.3. A search is then made for a disk file with the specified name as
the filename, andMODULE as the filetype. The search is made in
the standard disk search order. If this search is successful, then
the specified module is loaded (via theLOADeOD command), and
control passesto the storage location now occupied by the command.
4. If all searches so far have failed, thenDMSINA (ABBREV) is called,
to see if the specified routine name is a valid system abbreviation
for a system command or function.User-defined abbreviations and
synonyms are also checked. If this search is successful. then
steps 2 through 4 are repeated with the full function name.
5. If all searches fail, then an error code of -3 is issued.When a command is entered from the terminal, DeSINT processes the
command line, and calls the scan routine to convert it into a parameter
list consisting of eight-byte entries. The following search is
performed:
1.DMSINT searches for a disk file whose filename is the command name,
and whose filetype isEXEC. If this search is successful, EXEC is
invoked to process theEXEC file.
If not found, the command name is considered to be an abbreviation
and the appropriate tables areexamined. If found, the abbreviation
is replaced by its full equivalent and the search for anEXEC file
is repeated.Part 3. Conversational Monitor System (CMS) 259
return from a legitimate
3. Invalid
then an error message is
to terminate execution.
parameter list, then
or command. (In the case of
the specified index, the same logic must be applied.)
1.
The search algorithm is as follows:
A check is made to see if there is a routine with
name currently occupying the system transient area.
case, then control is transferred there.
the specified
If this is the
2. The system function name table is searched, to see if a command
successful, control goes to the specified nucleus routine.
the filename, and
the standard disk search order. If this search is successful, then
the specified module is loaded (via the
control passes
4. If all searches so far have failed, then
to see if the specified routine name is a valid system abbreviation
for a system command or function.
synonyms are also checked. If this search is successful. then
steps 2 through 4 are repeated with the full function name.
5. If all searches fail, then an error code of -3 is issued.
command line, and calls the scan routine to convert it into a parameter
list consisting of eight-byte entries. The following search is
performed:
1.
and whose filetype is
invoked to process the
If not found, the command name is considered to be an abbreviation
and the appropriate tables are
is replaced by its full equivalent and the search for an
is repeated.