HP3000 Application Note #11

Cause:	Stack overflow on the Interrupt Control Stack. One possible cause for the halt would be an underconfigured ICS. Some hardware problems might also generate an ICS overflow. These include: noisy or bad modems, turning power off and then on again on a multiplexer, or a continuously interrupting disc or tape drive.
Action:	If it is an underconfigured ICS that is causing this halt, then increase the size of the ICs.

Cause:	The User Controller Process (UCOP) Request Queue is full.
Action:	Enlarge the UCOP. This is the request queue for the User Controller Process. UCOP is responsible for creating and deleting processes, changing priorities, and expanding and contracting stacks. Recommended configuration is 2 per user. If you have process handling applications, you may need to configure more.

Cause:	Timer Request List (TRL) is full.
Action:	Increase the size of the table. This table is used by the memory logging facility, for calls to PAUSE, timed terminal I/O, and various other timings such as modem timing and logon timeouts. Recommended configuration is 2 * (number of terminals).

Cause:	Ran out of entries in the Special Request Table. This will be the cause only on a system that is running MPE IV or MPE V/P and was running on the ICS at the time of the failure.
Action:	Increase the size of the table. This table is used to temporarily buffer the parameters for segment expansion and to form the queue for devices waiting for a segment to arrive in memory. Recommended configuration is (number of PCBs) + (number of LDEVs).

Cause:	Ran out of entries in the Disc Request Table. This failure should only occur on an MPE IV system. Any system on a version later that MPE IV which runs out of DRQ table entries will get a console message.
Action:	Enlarge your Disc Request Table. Systems with disc cacheing should be configured => 255.

Cause:	Ran out of Swap Table entries. This will only be the cause if the system was running on the ICS at the time of the failure.
Action:	Increase the size of the Swap Table. This table keeps track of each process's locality list. Recommended configuration is 8 * (number of PCBs)

Cause:	Low-level message system integrity problem: 1. Corrupted MSG Harbor table 2. Bad message frames. 3. Bad message queue structure. SF620's are caused by an overflow of the Primary Message Table. One common occurance is when the I/O system is logging errors.
Action:	Make sure you have more Primary Message Table entries configured than System Buffer entries. Check if the system is logging I/O errors for some reason. Recommended configuration is 2 * (number of PCBs).

Cause:	Ran out of entries in the Disc Request Table. On systems running an MPE V based version of the operating system, you will get this message rather than a System Failure 601. This is an informational message only; the integrity of the system is not compromised.
Action:	Enlarge the configured value of the Disc Request Table. If you have Disc Cacheing, the Disc Request Table should be => 255.

Cause:	Ran out of System Buffers.
Action:	Increase the number of System Buffers. It's suggested value is 20 (or 50 if MTS is installed on the system). This problem may result from a bad magnetic tape generating numerous tape parity errors.

Cause:

One or more of three conditions are true, a) the maximum number of spoolfile kilosectors are already allocated, b) the disc drives in device class "SPOOL" are out of space, or c) the maximum number of spoolfiles are already open.

Action:

a) Print or SPOOK off some spoolfiles or reconfigure the system and answer the question "MAX # OF SPOOFLE KILOSECTORS=xxxx" with a larger value. b) Print or SPOOK off some spoolfiles, purge any un-needed user files, recover lost disc space, do a VINIT CONDENSE, or reconfigure the system and add the class "SPOOL" to more disc drives. c) Reconfigure the system and answer the question "MAX # OF OPENED SPOOLFILES = xxx" with a larger value.

Cause:	There are too many console requests for replies outstanding.
Action:	This table is a fixed size table; you must REPLY to the requests. The table is structured so it can contain 39 entries before it will begin to queue subsequent requests. There is room to queue 52 requests for a total of 91 outstanding requests before you will see the third message. At this point, you must REPLY to the outstanding requests.

Cause:	Code Segment Table is full.
Action:	Enlarge the CST or remove user segments from the system SL, account SLs or group SLs. The maximum size is 192 on systems without the expanded tables firmware. With the expanded tables firmware, the maximum is 2048.

Cause:	Data Segment Table is full.
Action:	Enlarge the DST. The maximum size on an MPE IV based system is 1024 and on an MPE V based system, it is 4096. If you are already configured at the maximum, you may want to investigate runnning a different mix of applications. Processes that use many extra data segments or open many files require more DST entries.

Cause:	a) No more virtual memory available or b) The DST table is full.
Action:	a) Configure more virtual memory. You can configure virtual memory through the Initiator dialogue on all system domain discs with the exception of LDEV 1. Changing the size of virtual memory on LDEV 1 requires a RELOAD. b) Check DST usage using OPT.

Cause:	No available entries in the Process Control Block.
Action:	Increase the size of the Process Control Block (PCB) table. The maximum on an MPE IV based system is 256. On an MPE V based system, the maximum is 1024. (Each process on the system requires one PCB entry; a typical session will require two or three entries.)

Cause:	No available entries in the Data Segment Table.
Action:	Increase the size of the Data Segment Table (DST). The maximum on an MPE IV based system is 1024. On an MPE V based system, the maximum is 4096. The recommended configuration is 8 * (number of users) + 64

Cause:	No entries available in the Data Segment Table to allocate an entry for the Job Information Table DST.
Action:	The Job Information Table (JIT) is a data segment and therefore needs an entry in the DST. There is one JIT per job or session. Increase the size of the Data Segment Table (DST). The maxiumum on an MPE IV based system is 1024. On an MPE V based system, the maximum is 4096. The recommended configuration is 8 * (number of users) + 64.

Cause:	No entries available in the Data Segment Table to allocate an entry for the Job Directory Table DST.
Action:	The Job Directory Table (JDT) is a data segment and therefore needs an entry in the DST. The is one JDT per job or session. Increase the size of the Data Segment Table (DST). The maximum on an MPE IV based system is 1024. On an MPE V based system, the maximum is 4096. The recommended configuration is 8 * (number of users) + 64.

Cause:	No available entries in the Job Process Count Table (JPCNT)
Action:	Increase the number of "MAX # OF CONCURRENT RUNNING JOBS" and "MAX # OF CONCURRENT RUNNING SESSIONS". This table is indirectly configurable and is used for locking RINs when the process does not have "MR" capability.

Cause:	No available entries in the Data Segment Table (DST)
Action:	Increase the size of the Data Segment Table. The file system will obtain a DST on behalf of a job or session and therefore needs an entry in the DST. The maximum on an MPE IV based system is 1024. On an MPE V based system, the maximum is 4096. The recommended configuration is 8 * (number of users) + 64.

Cause:

One or more of three conditions are true, a) the maximum number of spoolfile kilosectors are already allocated, b) the disc drives in device class "SPOOL" are out of space or c) the maximum number of spoolfiles are already open.

Action:

a) Print or SPOOK off some spoolfiles or reconfigure the system and answer the question 'MAX # OF SPOOFLE KILOSECTORS=xxxx" with a larger value. b) Print or SPOOK off some spoolfiles, purge any un-needed user files, recover lost disc space or reconfigure the system and add the class "SPOOL" to more disc drives. c) Reconfigure the system and answer the question "MAX # OF OPENED SPOOLFILES = xxx" with a larger value.

Cause:

One or more of three conditions are true, a) the maximum number of spoolfile kilosectors are already allocated, b) the disc drives in device class "SPOOL" are out of space or c) the maximum number of spoolfiles are already open.

Action:

a) Print or SPOOK off some spoolfiles or reconfigure the system and answer the question "MAX # OF SPOOFLE KILOSECTORSs=xxxx" with a larger value. b) Print or SPOOK off some spoolfiles, purge any unneeded user files, recover lost disc space or reconfigure the system and add the class "SPOOL" to more disc drives. c) Reconfigure the system and answer the question "MAX # OF OPENED SPOOLFILES = xxx" with a larger value.

Cause:	The stack space required to execute the command is greater than the system configured maximum stack size.
Action:	Reconfigure the system and answer the question "MAX STACK SIZE" with a larger value.

Cause:	A STORE or RESTORE command was issued without using a file equation referencing the tape drive and the device class "TAPE" or "CTAPE" does not exist on the system.
Action:	Issue a file equation for the tape drive and back reference it in the STORE/RESTORE command or re-configure the system and add the device class "TAPE" or "CTAPE".

Cause:	You are trying to obtain a RIN and the RIN Table is full.
Action:	Via SYSDUMP, check the number of RINs configured and currently being used. Say "YES" to "LIST GLOBAL RINS? to list the allocated RINs. There may be some that you can free up with the "FREERIN" command. If your RIN table is underconfigured, you must RELOAD your system to increase its size.

Cause:	PCB table is full.
Action:	Increase the size of the PCB table via SYSDUMP or the Initiator. The maximum for an MPE IV based system is 256. On an MPE V based system, the maximum is 1024.

Cause:	Data segment table is full. A stack is considered a data segment and therefore needs an entry in the Data Segment Table.
Action:	Increase the size of the DST via SYSDUMP or the Initiator. The maximum for an MPE IV based system is 1024, Onan MPE V based system, the maximum is 4096.

Cause:	Data Segment table is full. A JIT is a data segment and therefore needs an entry in the DST.
Action:	Increase the size of the DST via SYSDUMP or the Initiator. The maximum for a MPE IV based system is 1024. On an MPE V based system, the maximum is 4096.

Cause:	The Data Segment Table is full. A Job Directory Table (JDT) is a data segment and therefore needs an entry in the DST.
Action:	Increase the size of the DST via SYSDUMP or the Initiator. The maximum for a MPE IV based system is 1024. On a MPE V based system, the maximum is 4096.

Cause:	The Data Segment Table is full. The file system uses DSTs.
Action:	Increase the size of the DST via SYSDUMP or the Initiator. The maximum for a MPE IV based system is 1024. Ona MPE V based system, the maximum is 4096.

Cause:	There are no more available entries in the Job Process Count Table.
Action:	Increase the size of the Job Process Count Table. It is indirectly configured through SYSDUMP or the Initiator by answering the questions "MAX # OF CONCURRENT RUNNING SESSIONS = xxxx" and "MAX # OF CONCURRENT RUNNING JOBS = xxxx' with a higher value.

Cause:	FSERR 57 could be caused if Virtual Memory is underconfigured or by an underconfigured DST. It could also occur if the configured size of the Maximum Extra Data Segment is too small.
Action:	Check table usage with OPT to determine if the error might be caused by an underconfigured DST or VM. Also check the configured value of the Maximum Extra Data Segment to see if it is large enough to accommodate the program running.

Cause:	The program you are running needs a GLOBAL or LOCAL RIN and none is available.
Action:	Via SYSDUMP, check the number of LOCAL and GLOBAL RINS that are configured and currently being used. Say "YES" to LIST GLOBAL RINS? to list the currently allocated RINS. There may be some that are not being used that you can free up with the :FREERIN command. If your RIN table is underconfigured, you must RELOAD your system to increase its size.

Cause:	An attempt was made to "spool" input or output and the device class "SPOOL" is not configured on the system.
Action:	Reconfigure the system and add the device class "SPOOL" to at least one system domain disc drive. This can be done in the "CLASS CHANGES" section of SYSDUMP or the Initiator.

Cause:	The initial stack space required to execute the program is greater than MAXDATA.
Action:	RUN the program with the MAXDATA parameter and increase the space or PREP the program specifying a larger MAXDATA; or decrease the initial stack space required by decreasing the system default stack size and recompiling.

Cause:	A code segment within the program is larger than the system configured maximum code segment size.
Action:	Reconfigure the system and answer the question "MAX CODE SEG SIZE=xxxxx" with a larger value.

Cause:	The sum of DL space, DB space and the STACK is greater than 32K words.
Action:	One or a combination of the three parameters need to be reduced to bring the total space required below 32K words. Re-prep or re-run the program using the "DL=" and/or "STACK=" parms to reduce the space required by the data segment or reduce the program data area size.

Cause:	The sum of DL space, DB space and STACK is greater than the system configured maximum stack size.
Action:	Re-configure the system and answer the question "MAX STACK SIZE = xxxxx" with a larger value. An alternative solution is to re-prep or re-run the program using the "DL=" and/or "STACK=" parms to reduce the space required by the data segment or reduce the program data area size.

Cause:	No more available entries in the Code Segment Table (CST) or Code Segment Table Extension (CSTX).
Action:	Enlarge the CST or CSTX or remove user segments from the SL, account SLs or group SLs. The maximum size is 192 on systems without the expanded tables firmware. With the expanded tables firmware, the maximum is 2048.

Cause:	Data Segment Table is full.
Action:	Enlarge the DST. The maximum size on a MPE IV based system is 1024 and on a MPE V based system, it is 4096. If you are already at the maximum, you may want to investigate running a different mix of applications. Processes that use many extra data segments or open many files require more DST entries.

Cause:	Extended Code Segment Table is full.
Action:	Enlarge the CSTX. The CSTX is used for all programs code segments which are ALLOCATEd or RUN and is dependent on the number of users and the number of different applications they are running.

Cause:	No more available entries in the Loader Segment Table.
Action:	Increase the size of the loader segment table through SYSDUMP or the Initiator. If you are running Hewlett-Packard's Manufacturing Software, it is recommended that you configure the LST at 32760. The table expands dynamically and will not waste space if configured to the maximum.

Cause:	There is no more virtual memory available to allocate for the stack of the process that is being loaded.
Action:	An immediate work around is to terminate some processes thereby returning the virtual memory they are using. If the message comes up repeatedly, you can configure more virtual memory on all system domain disc drives through the Initiator (except LDEV 1).