HP 3000 Manuals HP 3000 Manuals
STARTSESS
NM and CM callable.
Initiates a session on the specified terminal. Programmatic sessions
(PS) capability is required.
Syntax
_______________________________________________________
| |
| I16V CA I16 I32 I16A |
| STARTSESS(ldev,logonstring,jsid,jsnum,jsstatus);|
_______________________________________________________
Parameters
ldev 16-bit signed integer by value (required)
The logical device number of the target terminal
(the terminal on which the session is to be
created). The target terminal must be a real
physical device, free and available to the system,
job-accepting, and hardwired. In addition, the
target terminal must be configured as TYPE 16, and
SUBTYPE 0 or SUBTYPE 4.
The target terminal must be set to the configured
baud rate, since there is no baud rate sensing by
STARTSESS.
logonstring character array (required)
Passes the logon string required to initiate the
session on the terminal specified by ldev. The
first characters in the string should be the
session name, if specified, or the user name if no
session name is assigned.
Passwords must be supplied in logonstring. (There
is no prompting for passwords on the target
terminal.) If passwords are required but not
supplied in logonstring, STARTSESS fails.
You must place a carriage-return character (%15) in
the element following the last valid character of
logonstring.
The logonstring parameter is a superset of the
HELLO command syntax and includes a new option,
nowait. The nowait option allows you to override
the requirement of a Return key entered at the
target terminal.
jsid 16-bit signed integer by reference (required)
Returns the value 1, indicating that jsnum is a
session number.
jsnum 32-bit signed integer by reference (required)
Returns a number uniquely identifying the session
that was created on the target terminal.
jsstatus 16-bit signed integer array (required)
Returns a two-element array containing status
information. The second element is reserved for
the operating system. The first element returns
the status information, refer to Table 4-29 .
Table 4-29. STARTSESS Status Returns
--------------------------------------------------------------------------------------------
| | |
| Status Value | Meaning |
| | |
--------------------------------------------------------------------------------------------
| | |
| 0 | Successful |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1411 | Logon failed due to IDD overflow |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1412 | Logon failed due to JMAT overflow |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1424 | Missing or invalid user name in logonstring |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1426 | Missing or invalid account name in logonstring |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1431 | Specified session user lacks interactive access (IA) capability |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1436 | No such group in the account |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1437 | No such account in the system |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1438 | No such user in the account |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1439 | User lacks a home group, and a group was not specified in logonstring |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1444 | Password required but not specified in logonstring |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1451 | Ignored delimiter |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1452 | Unknown parameter found in logonstring; ignored |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1458 | Bad TERMTYPE specified in logonstring; default used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1459 | Invalid PRI specified in logonstring; default used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1461 | HIPRI then INPRI specified; INPRI used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1462 | INPRI too low; lowest valid INPRI used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1463 | INPRI too high; highest valid INPRI used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1464 | INPRI then HIPRI specified; HIPRI used |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1465 | OUTCLASS specified; ignored |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1473 | RESTART specified; ignored |
| | |
--------------------------------------------------------------------------------------------
| | |
| -1479 | Invalid time specified in logonstring; no time limit is used |
| | |
--------------------------------------------------------------------------------------------
Table 4-29. STARTSESS Status Returns (cont.)
--------------------------------------------------------------------------------------------
| | |
| Status Value | Meaning |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7000 | The LDEV is out of range |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7001 | The LDEV must not be virtual |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7002 | The device specified by LDEV is not a terminal |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7003 | The LDEV is not free |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7004 | The LDEV is not job-accepting |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7005 | The LDEV is in diagnostic mode |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7006 | The LDEV terminal is down |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7007 | Down pending on LDEV |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7008 | ldev specified not a real device |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7009 | Caller requires programmatic sessions (PS) capability |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7010 | Semicolon (;) delimiter is missing |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7011 | The LDEV is not a valid integer |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7012 | The LDEV cannot be a negative number |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7014 | Session was aborted before logging on |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7015 | Logon failed because system is at its session limit |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7016 | Logon failed because the session's INPRI was <= system jobfence |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7017 | Logon failed because the system was unable to obtain a PCB entry for the |
| | system process |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7018 | Logon failed because the system was unable to obtain a DST entry for the |
| | session's data stack |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7019 | Logon failed because the system was unable to obtain a DST entry for the |
| | session's JIT |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7020 | Logon failed because the system was unable to obtain a DST entry for the |
| | session's JDT |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7021 | Logon failed because the system was unable to obtain a file DST entry |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7022 | Logon failed because the system was unable to obtain an entry for the |
| | session in the JPCNT table |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7023 | Logon failed because the system was unable to obtain the XDD entry for |
| | the output device |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7024 | Logon failed because the system was unable to obtain the XDD entry for |
| | the input device |
| | |
--------------------------------------------------------------------------------------------
Table 4-29. STARTSESS Status Returns (cont.)
--------------------------------------------------------------------------------------------
| | |
| Status Value | Meaning |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7025 | Unknown error occurred. This happens only in the case of an illegal call |
| | from one internal procedure to another internal procedure when passing |
| | the error number |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7026 | Unable to allocate $STDIN, or logon failed because of a failure to open |
| | $STDIN |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7027 | Unable to allocate $STDLIST, or logon failed because of a failure to open |
| | $STDLIST |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7029 | Logon failed because the session's account is out of CPU time |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7030 | Logon failed because the session's account is out of connect time |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7032 | Logon failed because account or user lacks IA capability |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7033 | Logon failed because the session's logon group is out of CPU time |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7034 | Logon failed because the session's logon group is out of connect time |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7035 | Logon string was not terminated with a carriage-return character (%15) |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7036 | The LDEV has an invalid type and subtype for a programmatic session |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7039 | Internal programmatic session error |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7040 | Unable to allocate $STDERR, or logon failed because of a failure to open |
| | $STDERR |
| | |
--------------------------------------------------------------------------------------------
| | |
| 7042 | Group is not specified, and there is no default home group |
| | |
--------------------------------------------------------------------------------------------
NOTE Error messages with numbers in the 10000 range are generally
Command Interpreter errors and should be looked up in the MPE/iX
Error Message Manual Volumes 1, 2 and 3 (32650-90066, 32650-90152,
and 32650-90368).
Operation Notes
The terminal on which the session is to be created must be available; no
other user may be logged on. The target terminal is not speed-sensed, so
it must be set at the configured baud rate.
When the session is created, nothing is printed to the terminal until you
press the Return key on the selected terminal (unless you specify
nowait). To override the need for a Return, you can enter the NOWAIT
keyword parameter with the logon string when invoking the STARTSESS
intrinsic. For example, passing the following logon string to STARTSESS
starts a session and logon immediately without waiting for a Return:
MANAGER/password.SYS;NOWAIT
Never specify the NOWAIT option in the logon string without first
ensuring that the target terminal is turned on and set at the default
baud rate. If the target terminal is the system console and nowait is
specified, then you must have system manager (SM) capability. All other
valid terminals can be specified with only programmatic sessions (PS)
capability.
Related Information
Intrinsics None
Commands None
Manuals Process Management Programmer's Guide (32650-90023)