HPlogo 900 Series HP 3000 Computer Systems: MPE/iX Intrinsics Reference Manual > Chapter 4 Command Definitions

STARTSESS

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

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-28 “STARTSESS Status Returns”.

Table 4-28 STARTSESS Status Returns

Status ValueMeaning
0Successful
1411Logon failed due to IDD overflow
1412Logon failed due to JMAT overflow
1424Missing or invalid user name in logonstring
1426Missing or invalid account name in logonstring
1431Specified session user lacks interactive access (IA) capability
1436No such group in the account
1437No such account in the system
1438No such user in the account
1439User lacks a home group, and a group was not specified in logonstring
1444Password required but not specified in logonstring
-1451Ignored delimiter
-1452Unknown parameter found in logonstring; ignored
-1458Bad TERMTYPE specified in logonstring; default used
-1459Invalid PRI specified in logonstring; default used
-1461HIPRI then INPRI specified; INPRI used
-1462INPRI too low; lowest valid INPRI used
-1463INPRI too high; highest valid INPRI used
-1464INPRI then HIPRI specified; HIPRI used
-1465OUTCLASS specified; ignored
-1473RESTART specified; ignored
-1479Invalid time specified in logonstring; no time limit is used
7000The LDEV is out of range
7001The LDEV must not be virtual
7002The device specified by LDEV is not a terminal
7003The LDEV is not free
7004The LDEV is not job-accepting
7005The LDEV is in diagnostic mode
7006The LDEV terminal is down
7007Down pending on LDEV
7008ldev specified not a real device
7009Caller requires programmatic sessions (PS) capability
7010Semicolon (;) delimiter is missing
7011The LDEV is not a valid integer
7012The LDEV cannot be a negative number
7014Session was aborted before logging on
7015Logon failed because system is at its session limit
7016Logon failed because the session's INPRI was <= system jobfence
7017Logon failed because the system was unable to obtain a PCB entry for the system process
7018Logon failed because the system was unable to obtain a DST entry for the session's data stack
7019Logon failed because the system was unable to obtain a DST entry for the session's JIT
7020Logon failed because the system was unable to obtain a DST entry for the session's JDT
7021Logon failed because the system was unable to obtain a file DST entry
7022Logon failed because the system was unable to obtain an entry for the session in the JPCNT table
7023Logon failed because the system was unable to obtain the XDD entry for the output device
7024Logon failed because the system was unable to obtain the XDD entry for the input device
7025Unknown 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
7026Unable to allocate $STDIN, or logon failed because of a failure to open $STDIN
7027Unable to allocate $STDLIST, or logon failed because of a failure to open $STDLIST
7029Logon failed because the session's account is out of CPU time
7030Logon failed because the session's account is out of connect time
7032Logon failed because account or user lacks IA capability
7033Logon failed because the session's logon group is out of CPU time
7034Logon failed because the session's logon group is out of connect time
7035Logon string was not terminated with a carriage-return character (%15)
7036The LDEV has an invalid type and subtype for a programmatic session
7039Internal programmatic session error
7040Unable to allocate $STDERR, or logon failed because of a failure to open $STDERR
7042Group 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)

Feedback to webmaster