HP 3000 Manuals HP 3000 Manuals
Appendix A Intrinsic Result Codes This appendix lists all the result codes that can be returned to SNA IMF intrinsics. Result codes are returned in the result parameter of most intrinsics; however, with no-wait MPE I/O, some result codes may be returned in the cstation parameter of the IOWAIT, IOWAIT3270, IODONTWAIT, and IODONTWAIT3270 intrinsics. This appendix lists the result codes by number. Each result code is followed by the message associated with it, the probable cause of the result code, and the actions you should take to resolve any errors. Messages generated by Pass Thru can appear on Pass Thru terminals and printers, and on the system console. For more information about Pass Thru messages, see appendix A of Using SNA IMF Pass Thru.
NOTE Although this appendix focuses on intrinsic result codes, you may encounter other messages while using SNA IMF. Refer to the SNA Link Services Reference Manual orUsing the Node Management Services Utilities for generic messages produced by the NMMGR, NMMAINT, and NMDUMP utilities. If you are using the HP SNA Server/Accessproducts on a LAN, some of the ACQUIRE3270 parameters are different from those described in chapter 3 of this manual. Therefore, a few of the messages in this appendix relate only to the use of SNA IMF with the HP SNA Server/Access products. Consult the HP SNA Server/Access User's Guide for more specific information.
--------------------------------------------------------------------------------------- Less than 0 MESSAGE The message that appears is an MPE V message. CAUSE This is an MPE V message, not an SNA IMF message. ACTION Look up the absolute value of the result code under "GENMESSAGE" in the MPE V Intrinsics Reference Manual. --------------------------------------------------------------------------------------- 0 MESSAGE Successful completion. CAUSE The intrinsic completed successfully. ACTION None. --------------------------------------------------------------------------------------- 1 MESSAGE Device not open. CAUSE An intrinsic other than OPEN3270 was called without first having opened the device. ACTION Call the OPEN3270 intrinsic to open the device before attempting to use it. --------------------------------------------------------------------------------------- 2 MESSAGE Could not access IMF configuration file. (MPE V only) CAUSE The OPEN3270 intrinsic could not FOPEN the specified IMF configuration file. ACTION Check that the IMF configuration file name is syntactically correct. Make sure the IMF configuration file exists as an old, permanent file. --------------------------------------------------------------------------------------- 2 MESSAGE Invalid devicenum parameter specified. (MPE XL only) CAUSE This error is returned to the OPEN3270 intrinsic, indicating that an inappropriate devicenum parameter value was specified. ACTION Check the value passed in the OPEN3270 devicenum parameter. Make sure this value is -1, -2, or -3. --------------------------------------------------------------------------------------- 9 MESSAGE Host modified screen since last receive request. (MPE V only) CAUSE The host has modified the screen since the last call to RECV3270. ACTION Because any attempt to change or send the screen at this point would be based on old information, issue a call to the RECV3270 intrinsic to clear the error and receive the latest screen. Call the READFIELD or READSCREEN intrinsic to give you the new contents of the screen. --------------------------------------------------------------------------------------- 10 MESSAGE Attempt made to update a protected field. CAUSE You cannot change the contents of a protected field. ACTION Call the SCREENATTR or FIELDATTR intrinsic to find the unprotected fields of your screen and make the changes again. --------------------------------------------------------------------------------------- 11 MESSAGE Non-existent field number specified. CAUSE The field number specified in a call to the FIELDATTR, READFIELD, or WRITEFIELD intrinsic does not exist in the screen. ACTION Call the SCREENATTR intrinsic to find the numbers of the fields. --------------------------------------------------------------------------------------- 12 MESSAGE Invalid character in field or data stream. CAUSE At least one character in the field or data stream was outside the range of allowable characters. ACTION See the descriptions of the outbuf parameter in the WRITEFIELD and STREAM3270 intrinsics. Make sure that every character is within the range specified. --------------------------------------------------------------------------------------- 13 MESSAGE Field length specified for WRITEFIELD is too long. CAUSE The field length specified in the call to the WRITEFIELD intrinsic is longer than the field length in the screen. ACTION Call the FIELDATTR intrinsic to find the current field length. Specify a field length less than or equal to the current field length. --------------------------------------------------------------------------------------- 14 MESSAGE Attempt made to update a field or transmit from an LU.T3 printer. CAUSE You have opened an LU.T3 printer. You are not allowed to change the contents of any field or to transmit from an LU.T3 printer. ACTION Open an LU.T2 or LU.T1 session. Only LU.T1 sessions support printer key entry. --------------------------------------------------------------------------------------- 15 MESSAGE Invalid AID parameter was sent. CAUSE The aid parameter specified in the TRAN3270 intrinsic is invalid. ACTION See the TRAN3270 intrinsic description for a list of valid aid codes. Note that the valid codes differ depending on the type of LU session. --------------------------------------------------------------------------------------- 16 MESSAGE Invalid cursor address was specified. CAUSE The cursorrow or cursorcolumn parameter of the TRAN3270 or STREAM3270 intrinsic is invalid. The row address must be less than the number of rows on the screen. The column address must be less than the number of columns on the screen. (SNA IMF starts with 0 when counting rows and columns.) ACTION See the TRAN3270 and STREAM3270 intrinsic descriptions for valid cursor address values. --------------------------------------------------------------------------------------- 17 MESSAGE Attempt made to write to a field where input is inhibited. CAUSE You called the WRITEFIELD, STREAM3270, or TRAN3270 intrinsic while input was inhibited by the host. ACTION Either wait for the host to reenable input by issuing another call to the RECV3270 intrinsic or call the RESET3270 or STREAM3270 intrinsic to emulate pressing the RESET key. --------------------------------------------------------------------------------------- 21 MESSAGE Field offset specified is out of range. CAUSE The specified offset value was outside the field length. ACTION Call the FIELDATTR intrinsic to find the length of the field. Be sure to specify an offset that is within the field length, and make sure that the offset for the WRITESTREAM and READSTREAM intrinsics is valid. --------------------------------------------------------------------------------------- 22 MESSAGE BASIC calling sequence error has occurred. CAUSE An error was detected in the BASIC calling sequence. ACTION Make sure the parameters of the intrinsic call from BASIC are in the correct order. --------------------------------------------------------------------------------------- 23 MESSAGE Keyboard enable timeout has occurred. CAUSE The host failed to enable the keyboard within the time limit specified in the timeout parameter of the OPEN3270 intrinsic. ACTION Use the RESET3270 intrinsic to reset the keyboard for key entry. This response may be host application specific. --------------------------------------------------------------------------------------- 24 MESSAGE Response timeout has occurred. CAUSE The host is possibly waiting for data from the user application or failed to send data to a device within the transmit/receive time limit set in the timeout parameter of the OPEN3270 intrinsic. ACTION If this message was expected, no action is required; the host may be expecting input from the user application. If the message was not expected, either the timer value given in the OPEN3270 intrinsic was not long enough to allow the host enough time to send data, or communications with the host have been disrupted. If the timer value was not long enough, use a longer timer value. If communications with the host have been disrupted, call the CLOSE3270 intrinsic to close the session. --------------------------------------------------------------------------------------- 25 MESSAGE Intrinsic call made while in split stack mode. CAUSE An intrinsic was called while in split stack mode. ACTION Make sure that DB is pointing to your own stack before you call SNA IMF intrinsics. --------------------------------------------------------------------------------------- 26 MESSAGE Intrinsic call made with the parameter value out of bounds. CAUSE A parameter address was either less than DL or greater than S when you called this intrinsic. You also could have passed an out of range parameter. A byte address may have been used instead of a word address. ACTION Check the call parameters and make sure they are being passed by reference and not by value. --------------------------------------------------------------------------------------- 27 MESSAGE Could not open device. Insufficient virtual memory was available. CAUSE There was insufficient virtual memory to allocate the extra data segment to contain the screen. ACTION Not enough virtual memory was available for system load, or too many processes are functioning at once. Have your system administrator configure more virtual memory. --------------------------------------------------------------------------------------- 28 MESSAGE Could not open device. Insufficient real memory was available. CAUSE There was not enough room in the PCBX of your process to allocate a file control entry for the device. ACTION Allocate more space for process using the MPE PREP command parameter DL = dlsize. --------------------------------------------------------------------------------------- 29 MESSAGE Called intrinsic with a request already outstanding. CAUSE You were in no-wait I/O and called the RECV3270 or TRAN3270 intrinsic while a previous request to one of these intrinsics was outstanding. ACTION Call the IOWAIT or IODONTWAIT intrinsic to complete the request before issuing any new SNA IMF intrinsic calls, or call ABORT3270 to abort the previous request. --------------------------------------------------------------------------------------- 30 MESSAGE Internal error occurred in IMF intrinsic. CAUSE An internal software error has occurred in an SNA IMF intrinsic. ACTION A file named IMFDUM xx was probably created in your group and account or in the PUB group of the SYS account. Save this file for your HP representative. Note the circumstances and report them to your HP representative. --------------------------------------------------------------------------------------- 38 MESSAGE Cannot start OUTBUF on an attribute byte. CAUSE The stream data you supplied positioned the cursor on top of an attribute byte. You may not write over an attribute character. ACTION Use the ATTRLIST intrinsic to locate the attribute bytes. --------------------------------------------------------------------------------------- 42 MESSAGE Specified MAXINBUFLEN parameter is too large. CAUSE You specified a maxinbuflen value that extends beyond the end of the screen. maxinbuflen does not wrap to the beginning of the screen. ACTION Make sure values for the offset and maxinbuflen parameters are less than the screen size. --------------------------------------------------------------------------------------- 43 MESSAGE Transparent mode not requested for LU.T1 emulation. CAUSE You specified a devicenum of -1 in your OPEN3270 intrinsic call without setting bit 14 of the OPEN3270 flags parameter to one. ACTION Set bit 14 of the OPEN3270 flags parameter to one and be sure to call only those intrinsics that are valid for transparent mode. --------------------------------------------------------------------------------------- 44 MESSAGE WRITESTREAM called during LU.T1 session. CAUSE The WRITESTREAM intrinsic was called during an LU.T1 session. ACTION The WRITESTREAM intrinsic cannot be called during an LU.T1 session. The only data that may be sent to the PLU are the printer keys, which are sent using the TRAN3270 intrinsic. --------------------------------------------------------------------------------------- 49 MESSAGE Value specified for the INBUF parameter is too small to hold the entire data stream. CAUSE The size of the data stream received from the host is larger than the size of the inbuf parameter. This result code applies to the READSTREAM intrinsic. ACTION Modify the maxinbuflen parameter of the READSTREAM intrinsic so the inbuf parameter can hold the entire data stream and issue a call to the READSTREAM intrinsic. --------------------------------------------------------------------------------------- 50 MESSAGE Called READSTREAM without calling RECV3270 first. CAUSE The RECV3270 intrinsic must be issued to receive host data before the READSTREAM intrinsic can be called. ACTION Issue a call to the RECV3270 intrinsic to accept host data. Then call the READSTREAM intrinsic to obtain the data from the extra data segment. This result code applies only to transparent mode. --------------------------------------------------------------------------------------- 51 MESSAGE Called TRAN3270 without calling WRITESTREAM first. CAUSE The buffer was not filled before trying to transmit. ACTION Put the data you want to send to the host in the extra data segment by calling the WRITESTREAM intrinsic before you call the TRAN3270 intrinsic. This result code applies only to transparent mode. --------------------------------------------------------------------------------------- 52 MESSAGE Data stream is too long. CAUSE The size of the data stream is larger than the maximum allowable size. ACTION For 480-character screens, 540 bytes is the maximum size. For 1920-character screens, 2160 bytes is the maximum size. For 3440-character screens, 3870 bytes is the maximum size. If this error occurs when the RECV3270 intrinsic is called, only the first 540, 2160, or 3870 bytes of the data stream will be buffered in the extra data segment. This result code applies only to transparent mode. --------------------------------------------------------------------------------------- 53 MESSAGE Invalid intrinsic called for data stream mode device. CAUSE An intrinsic was issued that cannot be called while in transparent mode. ACTION Do not use an intrinsic such as READFIELD or STREAM3270 in transparent mode. Because there is no internal screen image in transparent mode, do not use any intrinsic that reads from or writes to an internal screen image. --------------------------------------------------------------------------------------- 54 MESSAGE Device not opened in transparent mode. CAUSE You may not use the data stream intrinsics READSTREAM or WRITESTREAM, because you did not specify transparent mode in the flags parameter of your call to the OPEN3270 intrinsic. ACTION Request transparent mode by setting bit 14 of the OPEN3270 flags parameter to one. --------------------------------------------------------------------------------------- 60 MESSAGE Invalid spool file priority. Value must be between 1 and 13 inclusive. CAUSE A spool file priority other than a value from 1 through 13 was specified. ACTION Make sure the priority parameter of the PRINT3270 intrinsic is from 1 through 13. The priority parameter is passed on to the FOPEN intrinsic, which is described in the MPE V Intrinsics Reference Manual and the MPE XL Intrinsics Reference Manual. --------------------------------------------------------------------------------------- 61 MESSAGE Failed to open PRINT3270 spool file. CAUSE Your attempt to open the spool file for the PRINT3270 intrinsic failed when the FOPEN intrinsic was called. ACTION The PRINT3270 intrinsic leaves the fileid parameter set to zero so that you may call the file system intrinsic FCHECK to determine the specific reason for FOPEN's failure. Use FCHECK to determine the cause of the error. --------------------------------------------------------------------------------------- 62 MESSAGE Failed to write to PRINT3270 spool file. CAUSE The PRINT3270 intrinsic attempted to call the file system intrinsic FWRITE to write to the spool file identified by fileid; however, the call to FWRITE failed. ACTION Make sure the fileid value is correct. Insufficient disc space may also cause this error. Call the file system intrinsic FCHECK to determine the specific reason for FWRITE's failure. --------------------------------------------------------------------------------------- 63 MESSAGE The action parameter must be an integer from 0 through 4. CAUSE An invalid value was specified for the action parameter. ACTION Make sure the value of the action parameter in the PRINT3270 intrinsic is an integer from 0 through 4. --------------------------------------------------------------------------------------- 64 MESSAGE Wrong file type for PRINT3270 output file. CAUSE The FILE command you used to override the formal designator LOGIMF, which PRINT3270 uses, is incompatible with the requirements of PRINT3270 for a spooled output file. ACTION Exit the application and reissue the FILE command for LOGIMF. If you equate the LOGIMF file to another file, you must observe the following restrictions: the file must have a record size of 133 bytes and contain ASCII data. The equated file may not be a KSAM file. --------------------------------------------------------------------------------------- 65 MESSAGE Failed to close PRINT3270 output spooled file. CAUSE The PRINT3270 intrinsic attempted to call the file system intrinsic FCLOSE to close the file specified by fileid; this attempt failed. ACTION Make sure you supplied the proper value for fileid in your call to the PRINT3270 intrinsic. If you used a file equation for the LOGIMF file, be sure you did not equate it to an existing file. Call the file system intrinsic FCHECK to determine the specific reason for FCLOSE's failure. --------------------------------------------------------------------------------------- 66 MESSAGE Failed to open CATIMF.PUB.SYS. CAUSE The file CATIMF.PUB.SYS, which is the message catalog for SNA IMF, could not be opened. ACTION Make sure the CATIMF.PUB.SYS file is present.