NetView IBM

Messages and Codes

SH12-5483-07

NetView IBM

Messages and Codes

SH12-5483-07

Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page v.

Eighth Edition, December 1994

This is a major revision of, and obsoletes, SH12-5483-06.

This edition applies to Version 2 Release 2 Modification Level 1 of NetView File Transfer Program for MVS (5685-108) Version 1 Release 1 Modification Level 1 of NetView File Transfer Program for VSE (5686-013) Version 1 Release 1 Modification Level 1 of NetView File Transfer Program for VM (5684-048) and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. Make sure you are using the correct edition for the level of the product.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below.

IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you may address your comments to the following address: IBM Deutschland Entwicklung GmbH Information Development, Dept. 0446 Postfach 1380 71003 Boeblingen Germany

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

 Copyright International Business Machines Corporation 1988, 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Notices ...... v Trademarks and Service Marks ...... v

About This Book ...... vii What Is in This Book ...... vii

Chapter 1. NetView FTP Messages ...... 1 Message Format ...... 1 Special Characters in Messages ...... 1 Changing Message Text ...... 2 List of Messages ...... 2

Chapter 2. NetView FTP ABEND, Return, and Reason Codes ...... 109 NetView FTP ABEND Codes ...... 109 NetView FTP Return Codes ...... 109 NetView FTP Reason Codes ...... 112

Glossary ...... 147

Bibliography ...... 159 The NetView FTP Library ...... 159 Related Publications ...... 159

 Copyright IBM Corp. 1988, 1994 iii

iv NetView FTP Messages and Codes

Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM’s product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood NY 10594, U.S.A.

Trademarks and Service Marks The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM Corporation in the United States or other countries or both:

ACF/VTAM AIX C/370 IBM NetView OS/2 OS/400 RACF VM/ESA VM/XA VSE/ESA VTAM

 Copyright IBM Corp. 1988, 1994 v

vi NetView FTP Messages and Codes

About This Book

This book lists and describes all messages and codes issued by the NetView* File Transfer Program (abbreviated to NetView FTP in this book). This book is intended for all users of NetView FTP. The reader should be familiar with NetView FTP and the operating system it is running under.

What Is in This Book This book contains information on all messages and codes issued by NetView FTP and its components. Chapter 1, “NetView FTP Messages” Describes the type of messages issued by NetView FTP and provides a list of all messages issued, together with a description of the message, system response, and required user action. Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” Lists and describes the ABEND, return, and reason codes for all NetView FTP components. Glossary Contains a list of the terms and abbreviations used in the NetView FTP library.

A bibliography is also provided at the back of the book.

 Copyright IBM Corp. 1988, 1994 vii

viii NetView FTP Messages and Codes

Chapter 1. NetView FTP Messages

This chapter describes the messages issued by NetView File Transfer Program (abbreviated to NetView FTP in this book), and provides a list of all messages stored in the text area of the storage dump.

Message Format The message format is: DVGnnnc messagetext, where nnn is the message number and c is the message type code.

The message type code is as follows: I Information; no action is required. W Warning; action might be required depending on the situation. A Action; action must be performed to continue or restart the task.

Depending on the output device line-length and the message length, a message can occupy more than one line. If a message occupies more than one line, NetView FTP repeats the number on every line, as follows:

DVGnnnc messagetext part1 DVGnnnc messagetext part2 . . DVGnnnc messagetext partn

If a message is too long to fit on one line of the device to which it is sent, the message is split into two or more output lines. A delimiter (comma or blank) breaks each line of a message text near the (device-dependent) end of the output line. A long message, therefore, requires more lines on a terminal than on a printer, although the message text is identical.

Special Characters in Messages The following special characters, which can appear in the text of a message, indicate either incorrect message changes for national language support, or NetView FTP program errors: + Variable name was too long, no blank within 8 characters; variable has been truncated. # Variable identifier not numeric in second and third characters. ? Variable in model message not passed to generating module; this character substituted for the variable. *** Message text exceeds the maximum of 1024 characters; NetView FTP truncates the message to 1024 characters and substitutes these characters for the last three characters in the truncated message. variables NetView FTP adds variables that are passed to the message generator, but which are not in the model message, to the end of the message.

The messages that are displayed on the terminal or are printed out are, therefore, not necessarily in the form in which they appear in this book.

 Copyright IBM Corp. 1988, 1994 1 DVG001I Ÿ DVG003I

Changing Message Text You can change the text of all messages except messages DVG200I, DVG201I, DVG202I, DVG220I, DVG221I, DVG299I, DVG400I, DVG401I, DVG408A, DVG410I, and DVG670I. For further details, refer to the NetView FTP Installation, Operation, and Administration book that applies to your operating system and transfer program.

User Action: If the return code is 0, no action is List of Messages required. If the return code is not 0, refer to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109 to find out what it means. To help you find out what caused the error, DVG001I NETVIEW FTP release; look at all the messages NetView FTP issued. After SERVER srvname STARTED ON yy/mm/dd AT you find the messages that correspond to the error, hh:mm:ss; take the user actions they prescribe. MAINTENANCE LEVEL = mlevel

Explanation: A server started. DVG003I FILE TRANSFER ENDED FOR REQUEST NUMBER identifier release Release level of transfer program. ON yy/mm/dd AT hh:mm:ss; srvname Server name (MVS or VSE), or user ID or RC = retcd; resource ID of the file service component RSN = rsncd (VM). yy/mm/dd Date that the server started: yy=year, Explanation: A server issues this message at the mm=month, dd=day. end of a file transfer. hh:mm:ss Time that the server started: hh=hour, identifier Request number or name. This can be mm=minute, ss=second. zero if there is no valid file-transfer mlevel Program maintenance-level information; request when the message is issued. maintained by your system administrator. yy/mm/dd Date that the file transfer ended: yy=year, System Action: Processing continues. mm=month, dd=day. User Action: None. hh:mm:ss Time that the file transfer ended: hh=hour, mm=minute, ss=second. retcd File-transfer return code. DVG002I NETVIEW FTP release; SERVER srvname ENDED ON yy/mm/dd AT rsncd File-transfer reason code. hh:mm:ss; System Action: Processing continues. RETURN CODE = retcd User Action: If the file-transfer return code is 0, no action is required. If the return code is not 0, refer to Explanation: A server stopped running. Chapter 2, “NetView FTP ABEND, Return, and release Release level of transfer program. Reason Codes” on page 109 to find out what it means. srvname Server name (MVS or VSE), or user ID or resource ID of the file service component The return code 1000 is issued when the remote (VM). system does not issue reason codes. For example, if a request to a remote NetView FTP/400 system is yy/mm/dd Date that the server stopped: yy=year, rejected, the remote system issues return code 16; mm=month, dd=day. but no reason code. NetView FTP sets the reason hh:mm:ss Time that the server stopped: hh=hour, code in the server log to 1000. If the return code is mm=minute, ss=second. > 1nnn, an error occurred on the remote server. The local server was informed by the remote server that retcd Server return code. an error occurred at the remote system. The reason The server return code shows whether any errors code for the error at the remote system is occurred while the server was stopping. represented by the number nnn, which is one of the System Action: The server stops. reason codes listed in “NetView FTP Return Codes” on page 109. To help you find out what caused the error, look at all the messages NetView FTP issued. After you find the messages that correspond to the error, take the user actions they prescribe.

2 NetView FTP Messages and Codes DVG004I Ÿ DVG008I

04 The RUNUMCR, BYTECR, and DVG004I FILE TRANSFER STARTED ON LOCAL TIMECR parameters are mutually REQUEST HANDLER exclusive. You can specify only FOR REQUEST NUMBER reqnum one of these parameters. ON yy/mm/dd AT hh:mm:ss 05 The value specified for the AVLSESS parameter exceeded Explanation: A server obtained a file-transfer the value specified in the request from the request queue. The server MAXSESS parameter or the activates a local-request handler to carry out the file MAXSESS default parameter. transfer. 06 The value specified for the reqnum Request number. AVLLRH or AVLRRH parameter exceeded the value specified for yy/mm/dd Date that the file transfer started: yy=year, the AVLSESS parameter or the mm=month, dd=day. AVLSESS default value. hh:mm:ss Time that the file transfer started: 07 If the value specified for hh=hour, mm=minute, ss=second. SRVMODE is SINGLE, then the System Action: Processing continues. server can hold only one session User Action: None. at a time. Therefore the values specified for the AVLSESS and MAXSESS parameters must be DVG006I OPEN ON name WAS NOT SUCCESSFUL 1. 08 If ALL is specified for the Explanation: A NetView FTP component could not NVEVENT parameter, no other open one of the files necessary for its processing. NVEVENT values can be name ddname (for MVS) or file name (for VSE) specified. of the file in error. 09 Duplicate events were specified System Action: If the server group table is opened, for the NVEVENT parameter. processing continues. Otherwise, the NetView FTP 10 If you use parameters component terminates. PRETRAN, POSTTRAN, or both, User Action: Correct the error and restart the you must not use the PPEXIT NetView FTP component. Refer to the system parameter. messages in the failed component’s job log. 11 To start a partition, server initialization control statements for at least one server must be DVG008I ERROR DURING SERVER INITIALIZATION specified. PARAMETER HANDLING; ERROR CODE = error-code 12 You must specify server initialization control statements for at least those servers you Explanation: An error occurred when a server specified in the STARTSRV processed its initialization control statements during parameter of the partition startup. initialization control statement. error-code 13 Duplicate numbers were One of the following: specified for the STARTSRV 01 No server initialization control parameter. statements were specified. 14 A SRVSUF parameter must 02 No LUNAME parameter was precede other server parameters. specified; this is mandatory. 100 LRD filestore entry for the OSI 03 Duplicate class values were server is missing. specified in the CLASS System Action: The server or partition that the parameter. server runs in stops. User Action: Correct the error and restart the server or partition.

Chapter 1. NetView FTP Messages 3 DVG009I Ÿ DVG009I

13 If you specify space units to be DVG009I ERROR DURING FILE-TRANSFER REQUEST BLK, then: VALIDATION; Ÿ For non-VSAM files at MVS ERROR CODE = error-code locations, you must also specify an average length Explanation: An error occurred when NetView FTP and a primary space processed one of the parameters of a file-transfer quantity. request. Ÿ For VSAM at VSE and VM Note: If a parameter is not coded, the default used locations, you must also might be incompatible with other coded parameters. specify a primary space quantity. The average error-code length is ignored. One of the following: 14 You can specify an average 01 No file-transfer request length, a primary space quantity, parameters found. a secondary space quantity, or a 02 You must identify a remote number of directory blocks only if location by specifying either an a space unit is specified. LU name or the name of a server 15 You can specify space group, but not both. Neither was parameters only if the disposition specified. of the receiving data set is not 03 You must identify a remote OLD, MOD, or SHR. location by specifying either an 16 If you specify space units as LU name or the name of a server REC, then: group, but not both. Both were specified. Ÿ For non-VSAM files on an MVS system with SMS 04 You must specify either a active, you must also specify data-set name or a ddname for a primary space quantity and the sending data set. an average length. 05 You specified a remote LU name Ÿ For VSAM files, you must and a local LU name and both also specify a primary space had identical values. quantity. 06 Incorrect disposition found for the Ÿ For non-VSAM files at VM sending data set. and VSE systems, this 07 The disposition MOD or REG is specification is not valid. valid only for a single PDS Ÿ If a file type is not specified, member. you must specify a primary 08 Only dispositions OLD or NEW space quantity. are valid for unlabeled tapes at 17 Some of the parameters you the receiving location. specified when trying to modify a 09 A not-after date and time must request were incorrect or be greater than the missing. When modifying a corresponding not-before date submitted request, you can and time. change the server class or 10 If you specify data-set type request priority, or you can hold USER, you must also specify the or release the request. You name of a user-written file must not hold or release an handler. entire class by omitting the request number. 11 Only dispositions OLD and NEW are valid for VSAM data sets. 18 If you specify the name of a For MVS, CAT and SHR are also VSAM catalog, you must also valid. specify a VSAM password for that catalog (MVS). 12 If you specify space units to be CYL or TRK, then: 19 If a non-VSAM data set is to be transferred to a new VSAM Ÿ You must also specify a KSDS, you must specify the key primary space quantity. length for the receiving data set. Ÿ You cannot specify an 20 For new VSAM receiving data average length. sets, you must specify at least a model cluster or a volume serial number.

4 NetView FTP Messages and Codes DVG009I Ÿ DVG009I

21 The sum of the key length and Ÿ Several PDS members and key offset exceeds the maximum a file organization other than record size. PO. 22 The specification for the sending With the exception of the or receiving data set is following, these parameters must incompatible in one of the not be mixed: following ways: Ÿ VSAM cluster parameters Ÿ The receiving data-set type with SFS Directory Access is not PO and the sending parameters (sending) data set is PO, but you did Ÿ SFS Directory Access not specify a single member parameters (sending) with notation for the sending data SFS Directory Access set, for example, parameters (receiving). SFILEID='PDS.DATA.SET(MEMBER)'. 29 File Process Option MERGE is The sending data-set type is Ÿ valid only for PDS, VSAM KSDS, not PO and the receiving or VSAM RRDS. data set is PO, but you did not specify a single member 30 Either retention period or notation for the receiving expiration date is allowed, but data set, for example, not both. RFILEID='PDS.DATA.SET(MEMBER)'. 31 Record delimiter and End-of-file If more than one member of a option are valid only for PDS is to be transferred, the record-oriented files. data-set type of both the sending 32 Name of a member to be and receiving data sets must be selected or excluded is missing. PO. 33 Either selection or exclusion of If more than one member of a members is allowed, but not PDS is to be transferred, the both. data-set type of both the sending 34 Specify a VSAM catalog for a and receiving data sets must be data set at an MVS location only PO. if a new VSAM cluster is to be 23 If several members of a PDS are defined at that location. to be transferred, the data-set 35 The file type specified was type of both the sending and incorrect. receiving data sets must be PO. 36 Specify either a GDG model ID 24 Parameters for user-written file or a user catalog ID, but not handlers are valid only for data both. sets with the data-set type USER. 37 Specification of receiving SFS directory access parameters is 25 VSAM parameters are valid only only allowed for physical for VSAM data sets. sequential data set stored on a 26 If you specify record format VS DASD. or VBS for one data set, you 38 Specification of sending SFS must specify record format VS or directory access parameters is VBS for the other data set. only allowed for physical 27 The space units BLK are not sequential data set stored on a valid for VSAM data sets on DASD. MVS. 39 Incorrect tape device type 28 The parameters specified were specified for the first four incompatible. One of the characters. following combinations was 40 Incorrect tape device type suffix specified: specified (char-position 5,6). Ÿ User-written file handler 41 The specified tape device type, parameters and a file TAPEDC, is not allowed. organization other than USER 42 The Tape Device Type parameter specified an unlabeled Ÿ VSAM cluster parameters tape that requires the and a file organization other specification of the Tape Density than VSAM parameter.

Chapter 1. NetView FTP Messages 5 DVG009I Ÿ DVG009I

43 Track Number and Tape Density 60 Specify Coded Character Set for the specified tape device type Identifiers (CCSIDs) only if are inconsistent. character data conversion is requested. 44 For a receiving file to be SAM ESDS the receiving node must 61 The end-of-processing option be a VSE system. DELETE is not valid for the following: 45 For a receiving file to be SAM ESDS the data organization must Ÿ File access option SHARED be nonindexed. Ÿ Single member processing. 46 For a receiving file to be SAM 62 A file ID for the receiving file ESDS with the specified logical must be specified if the file status record size the record format option is MUSTEXIST and the must be fixed blocked. sending file ID cannot be used to generate a file ID. 47 If XMODE=FROM is specified, specify the sending data-set 63 Workstation ID is mandatory for type. remote AIX*. 48 KSDS option REPKEY is not 100 String significance and maximum valid for file status option string length incompatible. MUSTNOTEXIST. 101 Document type and universal 49 SFS subdirectories must be class incompatible. specified continuously. For 102 Access control action element example, you cannot specify value not allowed. subdirectories 1 to 3, then leave subdirectory 4 blank, and then 103 The specified access control specify subdirectory 5. action elements do not allow sufficient access rights to 50 If GENERIC is specified, SMS perform the read or read attribute Security Model must also be transfer option for COPY specified. function. 51 You cannot specify both SMS 104 The specified access control REFDD and SMS LIKE action elements do not allow parameters. sufficient access rights to 52 The following parameters are not perform the read, read attribute, valid with SMS: or delete transfer option for MOVE function. Ÿ Receiving DISP = OLD Ÿ Receiving file status option 105 Document type is not valid. MUSTEXIST (NetView FTP 106 Maximum string length is not V2.2 MVS) valid. Ÿ Receiving ddname. 107 String significance is not valid. 53 Do not specify average record multiplier if space units other 108 Universal class is not valid. than REC are specified. 109 Permitted actions do not match. 54 Specify both APPC user ID and 110 Data-set name is not valid. password parameters. 120 Data set is not available. 55 Specify both Data Encryption and 130 Data set I/O error. Encryption Label parameters. 200 User has insufficient RACF* 56 If the parameter specifies a authority. This code may also Linear Data Set (LDS), the indicate that the file does not average and maximum record exist. length, if specified, must be 4096. 210 OSI/File Services has insufficient RACF authority. This code may 57 Specify a secondary space also indicate that the file does quantity only if you also specify a not exist. primary space quantity. 300 A request that has already been 58 An OSI parameter was specified terminated cannot be canceled. for an SNA request. 310 Request temporarily returned to 59 For the CHANGEPW function, the queue handler. both the old and new passwords must be specified. 500 User filestore capability insufficient.

6 NetView FTP Messages and Codes DVG010I Ÿ DVG010I

510 Filestore access rights violated. 03 For fixed unblocked records, specify either a logical record 540 Specified document type does length and no physical block not correspond to LRD entry. size, or both a physical block 550 Maximum string length does not size and a logical record length correspond to LRD entry. that are equal to each other. 560 String significance does not 04 For variable and variable-blocked correspond to LRD entry. records, the physical block size 570 Universal class does not must be at least 4 bytes greater correspond to LRD entry. than the logical record length. The logical record length can be 580 Filestore capability is insufficient. any integer from 5 to 32 756 590 Filestore access is not allowed. (MVS and VM) or 5 to 32 763 (VSE). 600 File missing in LRD and it cannot be added. 05 Specify a logical record length and physical block size only if System Action: If this error is detected by: you specify a record format. Ÿ An interface routine, NetView FTP rejects the 06 The logical record length for VS request. or VBS records and the physical Ÿ A server, the file transfer ends and NetView FTP block size for VBS records can changes the status of the request to finished. be any integer value from 5 to User Action: Correct the error and resubmit the 32 756. request. 07 You must specify a logical record length and physical block size for VBS and VS records. DVG010I PARAMETER ERROR; RECORD FORMAT = recfm; 08 The file transfer was not BLOCK SIZE = blk; successful because: LOGICAL RECORD LENGTH = lrecl. Ÿ If the record format of the INVALID COMBINATION OF DCB PARAMETERS receiving data set is F or FB, SPECIFIED; the length of each record of PARAMETER TYPE = type; the sending data set must ERROR CODE = error-code equal that of each record of the receiving data set. Explanation: There is an error in the parameters Ÿ If the record format of the listed in this message. receiving data set is not F or blk Physical block size. FB, the logical record length of the sending data set must lrecl Logical record length. be equal to or less than that recfm Record format. of the receiving data set. type One of the following: System Action: If this error is detected by: S Parameter applies to sending Ÿ An interface routine, NetView FTP rejects the location. request. R Parameter applies to receiving Ÿ A server, the file transfer ends and NetView FTP location. changes the status of the request to finished. error-code User Action: Correct the error and resubmit the One of the following: request. 01 A record format was specified, but neither a physical block size nor a logical record length was specified. 02 For fixed-block records, physical block size and logical record length must be specified so that the physical block size is equal to or a multiple of the logical record length.

Chapter 1. NetView FTP Messages 7 DVG011I Ÿ DVG011I

23 No comma was coded after a DVG011I PARAMETER WITH KEYWORD keyword IN parameter value in a list of ERROR; values enclosed in parentheses. ERROR CODE = error-code The list of parameters is followed by a blank. Check for unpaired quotes or other errors in coding. Explanation: The keyword shown in this message corresponds to a parameter. Either that parameter 24 A blank immediately followed the or its value was in error. If NetView FTP is not able equal sign of a NetView FTP to determine which parameter is in error, it leaves control statement. keyword blank. 25 Unmatched quotes. Parameter error-code values cannot contain an odd One of the following: number of quotes. 01 Program error. 26 Number of opening parentheses not equal to number of closing 02 Program error. parenthesis. 03 More values than are allowed 27 A numeric parameter exceeds were specified for a parameter. the range of allowed values. The end-of-data delimiter may be missing from a batch job. 28 A parameter value is incorrect. 11 A program error occurred in the 29 Opening parenthesis not NetView FTP batch job interface immediately behind the operator. routine. Contact your system 30 A parameter value was coded administrator. with an incorrect length or a 12 A keyword contains a character comma was missing. that is not A to Z, or 0 to 9. Note: NetView FTP checks for Check for errors in the coding of the correct length of a value keywords, or errors that can before checking the correctness cause something to be wrongly of the value. For example, identified as a keyword. coding the keyword 13 The keyword is not followed by XMODE=RECEIVER causes any value. NetView FTP to issue a return code of 30 rather than 28. 14 The keyword is not a NetView NetView FTP also issues return FTP keyword. code 30 when a hexadecimal 15 The same keyword or its alias value is coded with an odd was already coded. number of characters. 16 The parameter has not exactly 31 A parameter value that must be one operator. coded within single quotes was 17 If more than one value is not. specified, the values must be 32 Too many values were coded for enclosed in parentheses. a parameter, or a closing 18 No keyword found before the parenthesis was missing. operator. 33 Closing parenthesis follows 19 Opening parenthesis or closing immediately after opening parenthesis or comma is parenthesis. specified before the operator. 34 A closing parenthesis was Only a keyword is allowed before missing or a blank was in the the operator. wrong place. 21 A program error occurred in the 35 At least one parameter value too NetView FTP batch job interface low. routine. Contact your system 36 At least one parameter value too administrator. high. Check for unpaired quotes or 37 At least one parameter length too other errors in coding. low. 22 A parameter value that is not 38 At least one parameter length too coded within single quotes high. contains a character that is not one of the following: A to Z, 0 to 39 Parameter length not correct (not 9, @, #, $. Check for missing part of a list of correct length). quotes or other errors in coding. 40 Closing parenthesis before opening parenthesis.

8 NetView FTP Messages and Codes DVG012I Ÿ DVG013I

41 A parameter value was coded System Action: with an opening quote but no NetView FTP V2.2 MVS closing quote. NetView FTP rejects the request. All 42 Number of value too high or low. other parameters are checked too. NetView FTP other than NetView FTP V2.2 MVS 43 Program error. If the error code is 1, 2, 3, 11, 21, 24, 44 NetView FTP stores parameter 34, 41, 43, 44, 51, 52, or 255, NetView information in tables. The size of FTP rejects the request without checking the tables is adequate for any further parameters. If the error code correctly specified parameters. is another number, NetView FTP checks An error caused the tables to be the other parameters in the request filled before NetView FTP could before it rejects the request. check all the parameters. User Action: 45 A parameter value that must be NetView FTP V2.2 MVS coded within single quotes was For error codes other than 1, correct the not. error and resubmit the request. For 46 At least one parameter value not error code 1 contact your IBM Support part of a list of valid values. Center. 47 At least one parameter value not NetView FTP other than NetView FTP V2.2 MVS numeric. For error codes other than 1, 2, 43, 51, and 255, correct the error and resubmit 50 Hexadecimal notation of a value the request. For error codes 1, 2, 43, incorrect: at least one digit not a 51, and 255, contact your IBM Support to f,A to F,0 to 9. Center. 51 Program error.

52 Syntax error. If you cannot find DVG012I KEYWORD keyword1 NOW REPLACED BY the reason for the error and if the KEYWORD keyword2; BUT STILL ACCEPTED error persists, contact your IBM* Support Center. Explanation: With NetView FTP V2.2 MVS, the 61 File ID contains both blanks and keyword indicated by keyword1 has been replaced periods. by the keyword indicated by keyword2. keyword1 is 62 The sequence of opening and still accepted. closing parentheses is incorrect. System Action: Processing continues. 63 The file ID must end with a User Action: None. You might, however, want to closing parenthesis. change your file-transfer requests accordingly. 65 A part of the file ID contains more than 8 bytes. DVG013I PARAMETER WITH KEYWORD keyword IS NOT 66 The file ID ends with a separator PERMITTED FOR THE FILE ORGANIZATION = sign. type 67 The file ID contains blanks. 68 The file ID contains a Explanation: A request specified at least one nonalphanumeric character. parameter that is incorrect for the file organization it specified. Either the parameter whose keyword is 69 The GDG number is too long. shown in the message, or the file organization 70 The GDG number is too short. specified in the request, is in error. 71 The GDG number is not numeric. Note: If a parameter is not coded, the default used 72 Invalid notation of a member or a might be incompatible with other coded parameters. GDG. keyword The batch job interface keyword. 73 The value begins with a type File organization can be one of the nonalphanumeric character. following: 75 Invalid CMS notation: one or VSAM VSAM data set more parts of a file ID contain PS Physical sequential data set more bytes than allowed. Maximum length is: PO Partitioned organized data set. 8 bytes For file name 8 bytes For file type 2 bytes For file mode. 255 Program error.

Chapter 1. NetView FTP Messages 9 DVG014I Ÿ DVG015I

System Action: If this error is detected by: 09 If you specify only a user ID and no password, NetView FTP Ÿ An interface routine, NetView FTP rejects the ignores the security parameters. request. Specify only the security Ÿ A server, the file transfer ends and NetView FTP parameter user ID without a changes the status of the request to finished. password if the remote User Action: Correct the error and resubmit the file-transfer program is FTP V2.2 request. VSE. This transfer program uses the specified user ID to notify an ICCF user at the end of a file DVG014I PARAMETER INCOMPATIBILITY; transfer. PARAMETER TYPE = type; ERROR CODE = error-code 10 NetView FTP ignores the value for the PDS option if: Explanation: A parameter for the data set indicated Ÿ A single member of a PDS by type has the incompatibility indicated by is specified error-code. Ÿ A member selection list of a type One of the following: PDS is specified. S Parameter applies to sending System Action: Processing continues. data set. User Action: Correct the error and resubmit the R Parameter applies to receiving request. data set. error-code One of the following: DVG015I PARAMETER WITH KEYWORD keyword IS NOT PERMITTED FOR THE TYPE type 01 Unless dynamic allocation is to Or, for NetView FTP V2.2 MVS: be used, NetView FTP ignores DVG015I PARAMETER WITH KEYWORD keyword IS NOT the Volume Serial Numbers PERMITTED FOR THE FILE ORGANIZATION = parameter for MVS locations. type; LABEL TYPE = lab-type 02 NetView FTP ignores the DCB parameters specified for PDS Explanation: A request specified at least one members with dispositions OLD parameter that is incorrect for the data-set type it or MOD. specified. Either the parameter whose keyword is 03 Specify DCB parameters for the shown in the message, or the data-set type specified sending data set only if it is at a in the request, is in error. VSE location or if it is stored on Note: If a parameter is not coded, the default used unlabeled tapes at an MVS might be incompatible with other coded parameters. location. Otherwise, NetView keyword The batch job interface keyword. FTP ignores the DCB parameters you specify. type Data-set type or file organization can be one of the following: 04 Unless dynamic allocation is to be used, NetView FTP ignores VSAM VSAM data set any DCB parameters you PS Physical sequential data set specified for data sets at MVS stored on DASD (other than locations. NetView FTP V2.2 MVS) 05 NetView FTP ignores any Physical sequential data set disposition specified other than stored on DASD or tape OLD or NEW for filetype VSAM (NetView FTP V2.2 MVS); the at a VSE node. label type of the tape is indicated by lab-type 06 NetView FTP ignores any key length, key offset, or KSDS PO Partitioned organized data set option you specify for non-KSDS LAB Physical sequential data set VSAM data set. stored on labeled tape 07 NetView FTP ignores the UNLAB Physical sequential data set parameters for a new VSAM file stored on unlabeled tape. unless the disposition of the receiving data set is NEW. lab-type Label type of the tape (NetView FTP V2.2 MVS) 08 NetView FTP has internally changed the server running SL Labeled tape mode value from single to NL Unlabeled tape. continuous. A VM system only recognizes continuous servers.

10 NetView FTP Messages and Codes DVG016I Ÿ DVG018I

System Action: If this error is detected by: System Action: The file-transfer request is checked, but not processed, because you specified Ÿ An interface routine, NetView FTP rejects the TESTRUN=YES in your request. request. Ÿ A server, the file transfer ends and NetView FTP User Action: To have the file-transfer request changes the status of the request to finished. processed, specify TESTRUN=NO. User Action: Correct the error and resubmit the request. DVG018I PARAMETER ERROR; PARAMETER TYPE = type; ERROR CODE = error-code DVG016I FUNCTION function IS NOT PERFORMED BECAUSE OF INCORRECT INPUT Explanation: Self-explanatory. Explanation: A queue handler command was type One of the following: issued and the Function parameter had the value S Parameter applies to the sending function. However, at least one of the NetView FTP data set. control statements in your request was in error. R Parameter applies to the function The value of the Function parameter, as receiving data set. used with the batch job interface. Possible values are: error-code One of the following: Ÿ ADD Ÿ DELETE 01 If the data-set type is PO, a Ÿ MODIFY request must specify either a Ÿ QRYADM member name or a ddname, but Ÿ QUERY not both. You did not specify Ÿ QRYALL either a member name or a Ÿ DELALL ddname. Ÿ DELFIN 02 If the data-set type is PO, a Ÿ FORCEDEL request must specify either a Ÿ RESTART member name or a ddname, but Ÿ CHANGEPW (VSE) not both. You specified both a Ÿ REBUILD (VSE). member name and a ddname. System Action: The function is not performed. 03 A request specified an incorrect User Action: This message is accompanied by combination of VM Link other messages indicating the control statement in parameters. The specification of error. When you have corrected the error, reissue the internal address and filemode the queue handler command. is only valid for FTP V2.2 for VM. 04 If a request specifies a node ID for the recipient of a file-transfer DVG017I FUNCTION function IS NOT PERFORMED report, it must also specify a user BECAUSE OF TEST RUN ID. The user ID is missing. 05 A request must specify a volume Explanation: A queue handler command was serial number for a data set that issued and the Function parameter had the value is to be dynamically allocated function. when one of the following is true: function The value of the Function parameter, as Ÿ The file to be sent is stored used with the batch job interface. on tape. Possible values are: Ÿ The file to be received on a Ÿ ADD VSE system is stored on a Ÿ DELETE labeled tape. Ÿ MODIFY Ÿ QRYADM Ÿ The file to be sent or Ÿ QUERY received on an MVS system Ÿ QRYALL is not cataloged. Ÿ DELALL Ÿ The file to be received on a Ÿ DELFIN tape on a VM system exists Ÿ FORCEDEL already (disposition = OLD). Ÿ RESTART Ÿ CHANGEPW (VSE) Ÿ The file to be received is a Ÿ REBUILD (VSE). new VSAM cluster for which no model name or SMS parameter (MVS) is specified.

Chapter 1. NetView FTP Messages 11 DVG018I Ÿ DVG018I

06 A request must specify a volume 18 If OS/400* is sending, you must serial number for a data set that specify the library name, file is to be dynamically-allocated, name, and member name. has the disposition NEW or CAT, 19 For one data set you cannot and is stored on a tape at an specify both OS/400 file MVS location. parameters and MVS data-set 07 A request specified an incorrect parameters. relative generation number for a 20 If OS/400 member name or file generation data set. type is specified, you must also 08 Record formats VS and VBS are specify library name and file not valid for the data-set type name. specified in the request. 21 If Post-Transfer Job library name 09 The relative generation number is specified, you must also or member name specified as specify the job name. part of the data-set name had an 22 If Post-Transfer Program is incorrect length. specified (APX section created), 10 The data-set name included you must specify Post-Transfer parentheses, but no relative Program Name APXPGNME. generation number or member 23 If Post-Transfer Program name. data-area length is greater than 11 You cannot specify both the zero, you must also specify the following: program name and parameter data area. Ÿ Parentheses as part of the value of the Data-Set Name 24 For non-VSAM files, only one parameter. This indicates volume serial number can be that you are specifying a specified for a VM node. relative generation number 25 Specify library name, file name, or a member name as part and member name when you of the data-set name. specify OLD for a receiving Ÿ A member name for the OS/400 file. Member Name parameter. 26 Specify the APPC user ID and 12 A relative generation number or password when you transfer a member name was specified as file to or from OS/400. part of the data-set name, but is 27 Shared file parameters are not not allowed for the data-set type allowed for VM/XA*. specified in the request. 28 If you specify a member name, 13 The data-set name included an you must also specify a file opening parenthesis but no name. closing parenthesis. 29 The end-of-processing option 14 The data-set name included a DELETE is not valid for the file closing parenthesis but no access option SHARED. opening parenthesis. 30 The end-of-processing option 15 You can specify either the name DELETE is not valid for single of a single PDS member or a list member processing. of PDS members, but not both. System Action: If this error is detected by: 16 You specified a combination of access security parameters that Ÿ An interface routine, NetView FTP rejects the is not valid. You cannot specify request. a value for one access security Ÿ A server, the file transfer ends and NetView FTP parameter (for example, user ID) changes the status of the request to finished. and have NetView FTP retrieve User Action: Correct the error and resubmit the another parameter (for example, request. password or group ID) by specifying an asterisk. Refer to the NetView FTP Parameter Reference for more information about access security parameters. 17 A model DSCB is valid only for GDGs, so the data-set type must be PS or LAB.

12 NetView FTP Messages and Codes DVG019I Ÿ DVG025I

System Action: The transfer ends. The status that DVG019I FILE TRANSFER STARTED ON REMOTE NetView FTP gives the request depends on the REQUEST HANDLER value of the Automatic Transfer Restart parameter ON yy/mm/dd AT hh:mm:ss for that request: Ÿ If the value is YES, NetView FTP gives the Explanation: A server received and accepted a request the status waiting; the request is session initiation request from a remote server. The reprocessed later. server activates one of its remote request handlers to Ÿ If the value is NO, NetView FTP gives the perform the file transfer. request the status finished; the request is not yy/mm/dd Date that the file transfer started: yy=year, reprocessed later. mm=month, dd=day. User Action: If the status of the file-transfer request hh:mm:ss Time that the file transfer started: is: hh=hour, mm=minute, ss=second. Ÿ Waiting, no action is required. System Action: Processing continues. Ÿ Finished and you want the file transfer to be User Action: None. reestablished, correct the error and resubmit the file-transfer request. Ÿ Finished and you do not want the file transfer to DVG020I text string be reestablished, no action is required.

Explanation: This message is used by NetView FTP to print text string. DVG023I REQUEST-UNIT SIZE OF oldsize IS REDUCED TO newsize text string One of the following: Explanation: The Request Unit (RU) size specified Ÿ Parameter input, read by NetView for a server is one of the following: FTP, passwords suppressed. Ÿ Not an acceptable value, but is between two Ÿ Separator lines to improve readability acceptable values. of NetView FTP message output. Ÿ Not a value that can be handled by your network System Action: Processing continues. resources. User Action: None. oldsize RU size specified for server newsize RU size used by NetView FTP. DVG021I SERVER FAILED TO RECOVER A SESSION; System Action: The server changes the value ERROR CODE = error-code specified to the next lower acceptable value. Processing continues. If the change was made due Explanation: The session with a remote server was to SNA RU size inconsistencies, the change remains interrupted by an ACF/VTAM* event. The local in force until the end of the server’s processing. If server tried to start the session again, but failed for the change was made due to network resource the reason indicated by error-code. shortages, the change applies only for the current file transfer; after the file transfer ended, NetView FTP error-code reestablishes the original value. One of the following: User Action: None. 01 The session could not be established during the time interval that allows automatic DVG025I SERVER serverid READY session recovery. 02 An ACF/VTAM event occurred Explanation: The server with the specified server which makes it impossible to ID is ready to obtain requests. recover the session. serverid One of the following: 03 The transfer was terminated, Ÿ The job name of the procedure because either the user deleted (MVS) the file-transfer request or the server was stopped. Ÿ The server prefix plus the server suffix (VSE) 04 The server tried to recover the session, but the remote server Ÿ The user ID of the distribution service was no longer active for this machine (VM). transfer. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 13 DVG026I Ÿ DVG028I

DVG026I SESSION NOT STARTED WITH luname; DVG028I SESSION NOT STARTED WITH luname; REMOTE SERVER WAITING FOR RECOVERY LOGICAL UNIT NAME IS UNUSABLE; RETURN CODE IN RPL = rcrpl; Explanation: When trying to start a new session, a FEEDBACK FIELD IN RPL = fdbk; server detected that the remote server was waiting SENSE CODE IN RPL = sensecode for recovery of an interrupted session. Explanation: The server tried to establish a session luname LU name of the remote server. with the logical unit named in the message but the System Action: If the file-transfer request specifies name was permanently not available. Possibly the the name of a server group, NetView FTP tries to LU name is not defined in ACF/VTAM. establish a session with another logical unit in the luname LU name, as specified in the file-transfer server group. If there are no more untried logical request or retrieved from the server units left in the server group or if the request group table. specified a remote LU name, NetView FTP changes the status of the file-transfer request to waiting. rcrpl ACF/VTAM return code in RPL. User Action: None. fdbk ACF/VTAM feedback code in RPL. sensecode ACF/VTAM sense code in RPL. DVG027I SESSION NOT STARTED WITH luname; For more information about the return, feedback, and RETURN CODE IN RPL = rcrpl; sense codes, see the VTAM Programming book. FEEDBACK FIELD IN RPL = fdbk; System Action: If the session was being SENSE CODE IN RPL = sensecode established for the first time and if the file-transfer request specifies the name of a server group, Explanation: When starting a session, the remote NetView FTP tries to establish a session with server is found to be temporarily not available. another logical unit in the server group. If there are Possibly, the remote server was not started. no more untried logical units left in the server group luname LU name of the server at the remote or if the request specified a remote LU name, location. NetView FTP changes the status of the file-transfer request to finished. rcrpl ACF/VTAM return code in RPL. If the session was being reestablished during fdbk ACF/VTAM feedback code in RPL. automatic session recovery, the transfer ends. The sensecode ACF/VTAM sense code in RPL. status that NetView FTP gives the request depends on the value of the Automatic Transfer Restart For more information about the return, feedback, and parameter for that request: sense codes, see the VTAM Programming book. Ÿ If the value is YES, NetView FTP gives the System Action: If the session was being request the status waiting; the request is established for the first time, and if the file-transfer reprocessed later. request specifies the name of a server group, NetView FTP tries to establish a session with Ÿ If the value is NO, NetView FTP gives the another logical unit in the server group. If there are request the status finished; the request is not no more untried logical units left in the server group reprocessed later. or if the request specified a remote LU name, User Action: If the status of the file-transfer request NetView FTP changes the status of the file-transfer is: request to waiting. Ÿ Waiting, no action is required. If the session was being reestablished during automatic session recovery, the transfer ends. The Ÿ Finished and you want the file transfer to be status that NetView FTP gives the request depends reestablished, correct the error and resubmit the on the value of the Automatic Transfer Restart file-transfer request. parameter for that request. Ÿ Finished and you do not want the file transfer to User Action: If the status of the file-transfer request be reestablished, no action is required. is: Ÿ Waiting, no action is required. Ÿ Finished and you want the file transfer to be reestablished, correct the error and resubmit the file-transfer request. Ÿ Finished and you do not want the file transfer to be reestablished, no action is required.

14 NetView FTP Messages and Codes DVG029I Ÿ DVG033I

DVG029I SESSION STARTED WITH luname AT hh:mm:ss DVG032I SESSION NOT STARTED WITH luname; USING AN LU TYPE 0 SESSION REMOTE SERVER COULD NOT ACCEPT ANOTHER SESSION Explanation: A server established an SNA session with a remote server using an LU type 0 session. Explanation: The remote server cannot accept the session because it already reached its limit for luname LU name of the remote server remotely initiated sessions. It is either busy with hh:mm:ss Time that the session started: hh=hour, other file transfers, or is already in a termination mm=minute, ss=second. state because it reached its termination time, or System Action: Processing continues. because an operator intervened. The remote server is regarded as temporarily not available. User Action: None. luname LU name of the remote server. System Action: If the session was being DVG031I SESSION NOT STARTED WITH luname; established for the first time and: NO STORAGE FOR REQUEST UNIT AVAILABLE AT REMOTE SYSTEM Ÿ If the file-transfer request specifies the name of a server group, NetView FTP tries to establish a session with another logical unit in the server Explanation: The remote server was unable to get group. virtual storage for the RU to be transferred. Ÿ If there are no more untried logical units left in luname LU name of the remote server. the server group or if the request specified a System Action: If the session was being remote LU name, NetView FTP changes the established for the first time and: status of the file-transfer request to waiting. Ÿ If the file-transfer request specifies the name of If the session was being reestablished during a server group, NetView FTP tries to establish a automatic session recovery, the transfer ends. The session with another logical unit in the server status that NetView FTP gives the request depends group. on the value of the Automatic Transfer Restart Ÿ If there are no more untried logical units left in parameter for that request: the server group or if the request specified a Ÿ If the value is YES, NetView FTP gives the remote LU name, NetView FTP changes the request the status waiting; the request is status of the file-transfer request to waiting. reprocessed later. If the session was being reestablished during Ÿ If the value is NO, NetView FTP gives the automatic session recovery, the transfer ends. The request the status finished; the request is not status that NetView FTP gives the request depends reprocessed later. on the value of the Automatic Transfer Restart User Action: If the status of the file-transfer request parameter for that request. is: User Action: If the status of the file-transfer request Ÿ Waiting, no action is required. is: Ÿ Finished and you want the file transfer to be Ÿ Waiting, no action is required. reestablished, correct the error and resubmit the Ÿ Finished and you want the file transfer to be file-transfer request. reestablished, correct the error and resubmit the Ÿ Finished and you do not want the file transfer to file-transfer request. be reestablished, no action is required. Ÿ Finished and you do not want the file transfer to be reestablished, no action is required. DVG033I SESSION NOT STARTED WITH luname; If the problem persists, ask your system REMOTE SERVER WAS RUNNING IN SINGLE administrator to check the messages at the remote MODE AND COULD NOT ACCEPT ANOTHER location. SESSION

Explanation: The remote server is running in single mode. It cannot accept the conversation because it is already in a session, or is not available for remotely initiated sessions. luname LU name of the remote server. System Action: If the session was being established for the first time and: Ÿ If the file-transfer request specifies the name of a server group, NetView FTP tries to establish a session with another logical unit in the server group.

Chapter 1. NetView FTP Messages 15 DVG035I Ÿ DVG038I

Ÿ If there are no more untried logical units left in the server group or if the request specified a DVG037I REMOTE REQUEST HANDLER IS PROCESSING remote LU name, NetView FTP changes the REQUEST NUMBER reqnum status of the file-transfer request to waiting. Or, for NetView FTP V2.2 MVS: If the session was being reestablished during DVG037I REMOTE REQUEST HANDLER IS PROCESSING automatic session recovery, the transfer ends. The REQUEST NUMBER = reqnum; REQUEST NAME status that NetView FTP gives the request depends = reqname on the value of the Automatic Transfer Restart parameter for that request: Explanation: The remote request handler subtask Ÿ If the value is YES, NetView FTP gives the of the server is processing the file-transfer request request the status waiting; the request is with the number reqnum and the request name reprocessed later. reqname. Blanks instead of reqnum or reqname indicate that the corresponding value is not available. Ÿ If the value is NO, NetView FTP gives the The request was obtained by a remote server from request the status finished; the request is not its request queue. reprocessed later. System Action: Processing continues. User Action: If the status of the file-transfer request is: User Action: None. Ÿ Waiting, no action is required. Ÿ Finished and you want the file transfer to be DVG038I THE REMOTE SERVER HAS AN INSUFFICIENT reestablished, correct the error and resubmit the FTP LEVEL; file-transfer request. ERROR CODE = error-code Ÿ Finished and you do not want the file transfer to Explanation: A server issues this message if it be reestablished, no action is required. detects that the remote server has an incompatible Note: Before the request is rescheduled, check with FTP level, or if it detects that the remote transfer your system administrator to make sure that the program is not NetView FTP or FTP V2. remote server is restarted and is ready to serve Note: A compatibility PTF must be installed for FTP sessions initiated at remote locations. V2 to be able to communicate with NetView FTP. error-code DVG035I AUTOMATIC SESSION RECOVERY IN One of the following: PROGRESS AT hh:mm:ss WITH luname 01 The remote transfer program is not NetView FTP or FTP V2. Explanation: ACF/VTAM notified the server that the session with the remote server was interrupted. The 02 The remote transfer program is local server attempts to recontact the remote server. FTP V2 for MVS and VSE. hh:mm:ss Time that session recovery started: 03 The remote transfer program is hh=hour, mm=minute, ss=second. FTP V2 for VM or a compatible release. luname LU name of the remote server. System Action: The remote transfer program either System Action: The server will try to restart the issues the FTP V2 message DVG034I with sense session with the remote server. If successful, the file code 10050000 or shows an ACF/VTAM RECEIVE transfer continues from the point at which the break error. occurred. If not successful, the file transfer ends. If the file-transfer request specifies the name of a User Action: None. server group, NetView FTP tries to establish a session with another logical unit in the server group. If there are no more untried logical units left in the DVG036I SESSION NOT STARTED WITH luname; server group or if the request specified a remote LU INCOMPATIBLE NETVIEW FTP LEVEL name, NetView FTP rejects the file-transfer request and changes the status of the request to finished. Explanation: A server issues this message if it User Action: Check that the location that was detects that the remote server has an incompatible contacted is a NetView FTP or FTP V2 location. If it NetView FTP level. is not, correct and resubmit the request. If it is, luname LU name of the remote server contact your system administrator. System Action: NetView FTP does not start the session, rejects the file-transfer request and changes the status of the request to finished. User Action: Check that the location that was contacted is at least either a NetView FTP V2 MVS, NetView FTP V1 VM, NetView FTP V1 VSE, NetView FTP/400, or NetView FTP for Workstations location. If it is not, correct and resubmit the request. If it is, contact your system administrator.

16 NetView FTP Messages and Codes DVG039I Ÿ DVG042I

Possibly there is an existing member on the DVG039I REMOTE SERVER luname COULD NOT ACCEPT receiving data set with the same name. If you A SESSION did not specify DISP=MOD, the receiving data set could have overflowed. NetView FTP changes the status of the file-transfer request to Explanation: The remote server cannot accept a finished. session initiation request. Possible reasons are: Ÿ Error occurred in queue handler; the queue Ÿ The remote FTP V2 VM is not running in remote handler stops. request server mode. User Action: Ÿ The remote FTP V2.2 MVS or FTP V2.2 VSE is not running in resident session partner mode. Ÿ For an error during a file transfer, correct the error and resubmit the request. If NetView FTP is to transfer a file to or from an FTP V2 location, the remote FTP V2 must be either a Ÿ For error in queue handler, correct the problem remote request server (VM) or a resident session and restart the queue handler. partner (VSE or MVS).

luname LU name of the remote server as DVG041I I/O ERROR FOR QSAM macro; specified in the file-transfer request or UNIT = unit; retrieved from the server group table. DEVICE = device; System Action: If the file-transfer request specifies DD-NAME = ddname; the name of a server group, NetView FTP tries to OPERATION = operation; establish a session with another logical unit in the ERROR DESCRIPTION = errordesc; server group. If there are no more untried logical PHYSICAL RECORD ADDRESS = bbcchhr units left in the server group, or if the request specified a remote LU name, NetView FTP rejects Explanation: An I/O error occurred in one of the the file-transfer request and changes the status of NetView FTP components while NetView FTP was the request to finished. processing the data set via QSAM. User Action: Check the specified LU name or, if macro QSAM macro that is in error: the name of a server group was specified, check the Ÿ CLOSE server group table for valid values. If the problem Ÿ GET persists, contact the remote location for information Ÿ OPEN about the remote servers. Ÿ PUT. unit Unit address. device Device type. DVG040I function ERROR ON ddname ddname Symbolic name of the DD statement. operation Operation attempted. Explanation: An error occurred in one of the errordesc Description of error. NetView FTP components during execution of the bbcchhr Direct access address of record in error. function specified. Probably an additional system System Action: If the error occurs independently of message was issued to the component’s job log. a file transfer, the NetView FTP component that function One of the following: issued the message stops. If the error occurs during Ÿ OPEN a file transfer, the file transfer ends and NetView FTP Ÿ CLOSE changes the status of the request to finished; the Ÿ TCLOSE (CLOSE TYPE = T). server does not stop. ddname ddname or data-set name of the file in User Action: See the SYNADAF macroinstruction error. in the Administration Macroinstruction Reference for your operating system. System Action: Ÿ Error occurred during a file transfer; the file transfer ends. DVG042I I/O ERROR FOR SAM macro; TRANSMIT INFO = trans; If the error occurred in a server and the function CSW STATUS = status; was OPEN, it is probably due to one of the TYPE CODE = code; following: CCW ADDRESS = ccw; – The data-set type in the request does not COMMAND CODE = cmdcd; match the file type of the data set. RELATIVE BLOCK NUMBER = rbn – The data set does not exist. This is usually a result of using the default data-set type. Explanation: An I/O error occurred while processing the SAM file. – Insufficient storage in the MVS region, the VM machine that the NetView FTP macro SAM macro that encountered the error. component runs on, or the VSE partition. Can be one of the following: Ÿ GET – An authorization problem. Ÿ PUT. If the function was CLOSE, check to see if you trans Transfer information from CCB. specified DISP=MOD for a PDS member. status CSW status from CCB.

Chapter 1. NetView FTP Messages 17 DVG043I Ÿ DVG044I

code Type code from CCB. ccw Address of CCW from CCB. DVG044I PHYSICAL ERROR FOR VSAM macro; ccd Command code of the current CCW. REGISTER 15 RETURN CODE = reg15; rbn Relative block number from DTF. VSAM RETURN CODE IN RPL = rcrpl; System Action: Transfer ends. FEEDBACK FIELD IN RPL = fdbk; DATE = yyddd; TIME = hhmmssth; User Action: Correct the error and resubmit the RELATIVE BYTE ADDRESS = rba; request. For an explanation of the fields from the COMPONENT TYPE = comp; CCB, see VSE/ESA Version 1 System Macros VOLUME SERIAL NUMBER = ser; Reference or VSE/AF 4.1.1 Macro Reference. If you JOB = job; cannot solve the problem, contact your IBM Support STEP = step; Center. UNIT = cuu; DEVICE = devtyp; DD-NAME = ddname; DVG043I LOGICAL ERROR FOR VSAM macro; COMMAND CODE = op-OP; REGISTER 15 RETURN CODE = reg15; ERROR MESSAGE = errmsg; FUNCTION CODE IN RPL = rcrpl; PHYSICAL RECORD ADDRESS = bbcchhr FEEDBACK FIELD IN RPL = fdbk; DD-NAME = name Explanation: During processing of a VSAM data set a physical error occurred. Explanation: During processing of a VSAM data set, a logical error occurred. macro VSAM macroinstruction that encountered the error: macro VSAM macro that encountered the error: Ÿ ERASE Ÿ ERASE Ÿ GET Ÿ GET Ÿ POINT Ÿ POINT Ÿ PUT. Ÿ PUT. reg15 Contents of register 15; returned by reg15 Contents of register 15 in hexadecimal VSAM. format; returned by VSAM. rcrpl VSAM return code in RPL. rcrpl VSAM function code in RPL for alternate index processing, in hexadecimal format. fdbk VSAM feedback code in RPL. fdbk VSAM feedback code in RPL, in yyddd Date that the error occurred: yy=year, hexadecimal format. ddd=day. name ddname of the data set in error. hhmmssth Time that the error occurred: hh=hour, System Action: If the error occurs independently of mm=minute, ss=second, th=tenth, and a file transfer, the NetView FTP component that hundredth of a second. issued the message stops. If the error occurs during a file transfer, the file transfer ends and NetView FTP rba Relative byte address. changes the status of the request to finished; the comp Component type: server does not stop. Ÿ DATA User Action: Analyze the problem using one or Ÿ INDEX. more of the following: ser Volume serial number. Ÿ MVS/DFP V3: Macro Instructions for VSAM Data Sets job Job name. Ÿ MVS/XA VSAM Administration Macro Instruction step Step name. Reference cuu Device address. Ÿ Using VSE/VSAM Commands and Macros. devtyp Direct access: DA always appears in this If a NetView FTP component stopped, fix the message. problem and restart the component. ddname Symbolic name of the DD statement. If a file transfer ended, fix the problem and resubmit the file-transfer request. op-OP Command code from CCW followed by characters -OP. errmsg VSAM error message. bbcchhr Direct access address of record in error. System Action: If the error occurs independently of a file transfer, the NetView FTP component that issued the message stops. If the error occurs during a file transfer, the file transfer ends and NetView FTP changes the status of the request to finished; the server does not stop.

18 NetView FTP Messages and Codes DVG045I Ÿ DVG048I

User Action: Analyze the problem using one or more of the following: DVG046I I/O ERROR FOR BPAM macro; Ÿ MVS/DFP V3: Macro Instructions for VSAM Data UNIT = unit; Sets DEVICE = device; Ÿ MVS/XA VSAM Administration Macro Instruction DD-NAME = ddname; Reference OPERATION = operation; Ÿ Using VSE/VSAM Commands and Macros. ERROR DESCRIPTION = description; PHYSICAL RECORD ADDRESS = bbcchhr If a NetView FTP component stopped, fix the problem and restart the component. If a file transfer ended, fix the problem and resubmit the file-transfer Explanation: An I/O error occurred while request. processing the BPAM data set. macro BPAM macro that is in error: Ÿ READ DVG045I VSAM macro ERROR; Ÿ WRITE. REGISTER 15 RETURN CODE = reg15; unit Unit address. VSAM ERROR CODE = errcode; device Device type. DD-NAME = name ddname Symbolic name of the DD statement. operation Operation attempted. Explanation: During processing of a VSAM data description Description of error. set, an error occurred. bbcchhr Direct access address of record in error. macro VSAM macro that encountered the error: System Action: The transfer ends. Ÿ CLOSE Ÿ GENCB User Action: For more information, see one or Ÿ MODCB more of the following: Ÿ OPEN Ÿ MVS/DFP V3: Macro Instructions for non-VSAM Ÿ SHOWCB Data Sets Ÿ TCLOSE (CLOSE TYPE = T) Ÿ MVS/XA Data Administration: Macro Instruction Ÿ TESTCB Reference. Ÿ SHOWCAT. reg15 Contents of register 15 returned by VSAM. DVG048I I/O ERROR DURING SEQUENTIAL FILE PROCESSING; errcode VSAM error code. THE FOLLOWING SYSTEM MESSAGE WAS name If the transfer program runs under MVS, FOUND IN THE SYNADAF MESSAGE BUFFER then this is the ddname used to allocate message the data set. Otherwise it is the file name. It is either the name specified in Explanation: This message occurs when an error the file name parameter or, if dynamic is detected during the processing of a physical allocation is used, the one generated by sequential file. the server involved in the file transfer. message The message returned by the operating System Action: If the error occurs independently of system. a file transfer, the NetView FTP component that issued the message stops. If the error occurs during For an explanation of the error condition associated a file transfer, the file transfer ends and NetView FTP with these messages, refer to the following: changes the status of the request to finished; the Ÿ MVS/ESA Messages and Codes server does not stop. Ÿ MVS/XA Messages and Codes User Action: Analyze the problem using one or Ÿ VM/ESA System Messages and Codes more of the following: Ÿ VM/XA SP System Messages and Codes Reference. Ÿ MVS/DFP V3: Macro Instructions for VSAM Data Sets System Action: If the error is detected during the Ÿ MVS/XA VSAM Administration Macro Instruction transfer of a file that is related to a source or target Reference file, the file transfer is broken off. If the error is Ÿ Using VSE/VSAM Commands and Macros. related to the FTP reader, printer, or log files, and a file transfer is in progress, NetView FTP stops after If a NetView FTP component stopped, fix the the file transfer is completed. problem and restart the component. If the file transfer ended, fix the problem and resubmit the User Action: Correct the error and resubmit the file-transfer request. request. The most common VSAM error code is 74. This means that you should perform a VSAM VERIFY on the data set, as it has not been closed since the last time it was accessed.

Chapter 1. NetView FTP Messages 19 DVG049I Ÿ DVG053I

DVG049I ERROR DURING RESTART PROCESSING FOR DVG051I nn RECORDS COULD NOT BE PROCESSED AS file; REQUIRED BY THE KSDS OPTION ERROR CODE = error-code Explanation: A request specified the VSAM KSDS Explanation: An error occurred when NetView FTP option ADDKEY or DELKEY, and one of the tried to position a data set to the recorded following was true: checkpoint. Ÿ For ADDKEY, the receiving data set contained file ddname of the data set in error. records that were identical to those in the sending data set. error-code One of the following: Ÿ For DELKEY, records to be deleted from the receiving data set were not there. 01 No buffer could be obtained for a PDS member. This message is issued for your information; the message does not necessarily indicate that an error 02 Buffer size insufficient for a PDS occurred. If a file transfer is restarted and its request member. specifies ADDKEY, this message might be issued for 04 Checkpoint not found in data set. the records that are retransferred. Possibly, the data set was nn Number of logical errors that occurred. modified after the file transfer was interrupted. System Action: Processing continues. System Action: The transfer ends and NetView User Action: Check whether you have chosen the FTP changes the status of the request to finished. correct VSAM KSDS option. User Action: Do one of the following: Ÿ For error code 01, use a server that is started in DVG052I A RECORD WITH THE SAME KEY BUT a larger address space, requesting a restart from DIFFERENT CONTENT WAS the recorded checkpoint. In this case, contact FOUND IN THE RECEIVING KSDS WHILE your system administrator. UPDATING IT USING THE KSDS OPTION "ADDKEY" Ÿ For error code 02 or 04, add a new file-transfer request to the request queue to perform the file transfer, specifying that the file transfer must be Explanation: A server found a record with the started from the beginning of the receiving data same key but different content in the receiving data set (other than NetView FTP V2.2 MVS), or set, which was a KSDS and which it was updating restart the file transfer with RSTPNT=BEGIN to with the VSAM KSDS option ADDKEY. transfer from the beginning of the data set System Action: The transfer ends and NetView (NetView FTP V2.2 MVS). FTP changes the status of the request to finished. User Action: If appropriate, choose another VSAM DVG050I RECORD TO BE REPLACED NOT FOUND KSDS option. After you have corrected the errors, resubmit the file-transfer request. Explanation: The VSAM KSDS option REPKEY was specified, but a record in the sending data set DVG053I FTP LEVEL OF REMOTE SERVER = ftplevel did not have a corresponding record in the receiving data set. Explanation: The server established a session with System Action: The transfer ends and NetView the remote server. This message gives information FTP changes the status of the request to finished. about the FTP level of the remote server. User Action: If appropriate, choose another VSAM ftplevel One of the following: KSDS option. After you have corrected the errors, resubmit the file-transfer request. 4 FTP Version 2.2 with compatibility PTF for NetView FTP 5 NetView FTP Version 1 for MVS without the AFF 6 NetView FTP Version 1 for MVS with the AFF 7 NetView FTP V2 MVS, NetView FTP VM, or NetView FTP VSE. System Action: Processing continues. User Action: None.

20 NetView FTP Messages and Codes DVG054I Ÿ DVG060I

DVG054I I/O ERROR FOR QSAM function; DVG058W RECORDS FOUND WHILE OPENING VSAM DATA SET NAME = dsname; ESDS dsname SYSTEM ABEND CODE = sac Explanation: The receiving data set is a VSAM Explanation: An I/O error occurred during a QSAM ESDS and has the name dsname. During the OPEN function. The error caused an abnormal termination, on the receiving data set, the server detected that it from which NetView FTP recovered. was not empty. The server expected the receiving data set to be empty. The server writes over any function One to the following: existing records. If there are more records in the GET QSAM GET existing data set than are being transferred to it, PUT QSAM PUT these other records remain in the data set. This can cause an integrity problem. POINT QSAM GET System Action: Processing continues; the server dsname Name of data set. writes records from the beginning of the data set. A sac System ABEND code. warning is issued in the file-transfer completion message. System Action: The transfer ends and NetView FTP changes the status of the file-transfer request to User Action: If an integrity problem exists, delete finished. and redefine the data set and, after you have corrected the errors, resubmit the file-transfer User Action: Analyze the problem using one or request. Otherwise, ignore the message. more of the following: Ÿ MVS/DFP V3: Macro Instructions for non-VSAM Data Sets DVG059I RECORDS FOUND WHILE OPENING VSAM Ÿ MVS/XA Data Administration: Macro Instruction KSDS FOR A FILE TRANSFER USING THE Reference. KSDS OPTION "ADDBEG"

Explanation: During the OPEN on the receiving DVG056I VSAM DATA SET TYPE NOT SUPPORTED data set the server detected that the receiving data set, a VSAM KSDS, was not empty. The file-transfer Explanation: During the OPEN on the data set to request specified the VSAM KSDS option ADDBEG, be accessed during the file transfer, the server which requires an empty data set. detected that the VSAM data set is of an System Action: The transfer ends and NetView unsupported VSAM type. FTP changes the status of the file-transfer request to System Action: The transfer ends and NetView finished. FTP changes the status of the file-transfer request to User Action: Check that you have chosen the finished. correct KSDS and correct any errors. Then add a User Action: If you want to transfer the data set, new file-transfer request to the request queue to copy it into a data set of a supported type and perform the file transfer. transfer that one.

DVG060I NETWORK NAME VECTOR NOT FOUND. DVG057I KSDS OPTION SPECIFIED FOR A VSAM ESDS LOCAL FTP NAME USED FOR BUILDING CHECKPOINT KEY. Explanation: During the OPEN on the receiving data set, the server detected that the VSAM data set Explanation: The server did not find the network is an entry-sequenced data set (ESDS). However, a name in the VTAM* resource identification list. The VSAM KSDS option was specified in the file-transfer local FTP name is used for building the key for the request. checkpoint record. System Action: The parameter is ignored and System Action: Processing continues. processing continues. User Action: If the problem persists contact your User Action: If the receiving data set is not a IBM Support Center. VSAM KSDS, do not specify a VSAM KSDS option.

Chapter 1. NetView FTP Messages 21 DVG061I Ÿ DVG064I

If this fails, the transfer ends and NetView FTP DVG061I ACF/VTAM macro ERROR FOR LOGICAL UNIT changes the status of the request. The status that luname; NetView FTP gives the request depends on the ACB ERROR CODE = errcd value of the Automatic Transfer Restart parameter for that request. Explanation: During processing of an ACF/VTAM User Action: If the automatic session recovery was macro, an error occurred. successful or the status of the request was changed to waiting, no action is required. If the status was macro ACF/VTAM macro that encountered the changed to finished, it is possible that the error error: occurred during the termination of the server, without Ÿ CLOSE affecting the transfer of data. Check to see if all Ÿ OPEN. records were transferred. If all records were not luname LU name of the server that issued the transferred, or if the return code is greater than 8, request. see the VTAM Programming book for descriptions of the ACF/VTAM codes in this message. errcd Error code provided by ACF/VTAM after invocation of the macroinstruction. System Action: The server stops. DVG063I DSESLIM VECTOR NOT FOUND. USE DEFAULT VALUE = ; User Action: Correct the ACF/VTAM problem and restart the server. Explanation: The VTAM application definition for For a description of this error code, see the VTAM the server LU did not specify the DSESLIM Programming book. parameter. NetView FTP uses a default value. System Action: Processing continues. DVG062I ACF/VTAM macro ERROR; User Action: Add the VTAM DSESLIM parameter REGISTER 15 RETURN CODE = reg15; to the VTAM application definition (APPL minor RETURN CODE IN RPL = rcrpl; node) for this specific server LU name. For more FEEDBACK FIELD IN RPL = fdbk; information on setting up and maintaining the SENSE CODE IN RPL = sensecode ACF/VTAM resources refer to NetView FTP V2 MVS LOGICAL UNIT NAME = luname Installation, Operation, and Administration.

Explanation: During processing of an ACF/VTAM macro, an error occurred. DVG064I SESSION NOT STARTED WITH luname ALTHOUGH POSITIVE RESPONSE RECEIVED macro ACF/VTAM macro that encountered the error: Explanation: The remote server, which has the LU Ÿ CLSDT name luname, did not start the session. This was Ÿ INQUIRE determined by checking the CON field in the Ÿ OPNDST ACF/VTAM Node Initiation Block (NIB), which Ÿ OPNSEC indicated that the session was not started although a Ÿ RECEIVE positive response was returned to the BIND. Ÿ SEND Ÿ SESSIONC System Action: If the session was being Ÿ SETLOGON established for the first time and: Ÿ TERMSESS. Ÿ If the file-transfer request specifies the name of reg15 Return code in register 15 returned by a server group, NetView FTP tries to establish a ACF/VTAM. session with another logical unit in the server group. rcrpl ACF/VTAM return code in RPL. Ÿ If there are no more untried logical units left in fdbk ACF/VTAM feedback code in RPL. the server group or if the request specified a sensecode ACF/VTAM sense code in RPL. remote LU name, NetView FTP changes the status of the file-transfer request to waiting. luname For the INQUIRE and SETLOGON macro, this is the LU name of the local If the session was being reestablished during server. In all other cases this is the LU automatic session recovery, the transfer ends. The name of the remote server. status that NetView FTP gives the request depends on the value of the Automatic Transfer Restart System Action: If the macro is not SEND or parameter for that request. RECEIVE, the file transfer ends or the server stops, depending on whether the problem is related to one transfer or the entire server. NetView FTP changes the status of the request to finished. Otherwise, if the macro is SEND or RECEIVE and no severe ACF/VTAM error occurred, the server tries to perform an automatic session recovery.

22 NetView FTP Messages and Codes DVG065I Ÿ DVG067I

User Action: If the status of the file-transfer request senserpl is: ACF/VTAM sense code in the RPL extension. Ÿ Waiting, no action is required. rcpri ACF/VTAM LU 6.2 primary return code. Ÿ Finished, and you want the file transfer to be reestablished, correct the error and resubmit the rcsec ACF/VTAM LU 6.2 secondary return code. file-transfer request. System Action: If this message is accompanied by Ÿ Finished, and you do not want the file transfer message DVG074I, DVG075I, DVG076I, DVG077I, to be reestablished, no action is required. or DVG078I, refer to that message for an explanation of the system action and user action. Otherwise, the status that NetView FTP gives the request depends DVG065I ACF/VTAM APPCCMD MACRO ERROR; on the value of the Automatic Transfer Restart OPERAND CODE = opcode; parameter for the request. RETURN CODE IN RPL = rcrpl; FEEBACK FIELD IN RPL = fdbkrpl; User Action: If the status of the request was SENSE CODE IN RPL6 = senserpl; changed to waiting, no action is required. If the APPC PRIMARY RETURN CODE = rcpri; status was changed to finished, it is possible that APPC SECONDARY RETURN CODE = rcsec the error occurred during termination of the server without affecting the data transfer. Check to see if all records were transferred. If they were not, or if Explanation: An error occurred during the the file-transfer return code was greater than 8, processing of the ACF/VTAM APPCCMD macro. manually restart the file transfer. opcode For more information about the ACF/VTAM codes in A code that corresponds to the operand for this message, refer to the VTAM Programming for which the error occurred. Possible values LU 6.2. are: Code Operand DVG066I PROCESSING OF REQUEST NUMBER reqnum DISPLAY STARTED CONTROL=OPRCNTL,QUALIFY=DISPLAY Or, for NetView FTP V2.2 MVS: CNOS CONTROL=OPRCNTL,QUALIFY=CNOS DVG066I PROCESSING STARTED FOR REQUEST NUMBER = reqnum; REQUEST NAME = reqname ALLOC CONTROL=ALLOC,QUALIFY=ALLOCD Explanation: A server obtained a file-transfer SENDCONF request from the request queue. The server has CONTROL=SEND,QUALIFY=CONFIRM activated one of its subtasks to carry out the file SENDCNFD transfer. CONTROL=SEND,QUALIFY=CONFRMD reqnum Request number. Blanks indicate that this DEALLOC value is not available. CONTROL=DEALLOC reqname Request name. Blanks indicate that this DEALABND value is not available. CONTROL=DEALLOC,QUALIFY=ABNDUSER System Action: Processing continues. PREPRCV User Action: None. CONTROL=PREPRCV RCVFMH5 CONTROL=RCVFMH5 DVG067I SERVER COULD NOT ALLOCATE A CONVERSATION USING AN LU TYPE 6.2 RECEIVE SESSION; CONTROL=RECEIVE,QUALIFY=SPEC APPC PRIMARY RETURN CODE = rcpri; REJECT APPC SECONDARY RETURN CODE = rcsec; CONTROL=REJECT THE SERVER WILL TRY TO ESTABLISH AN LU TYPE 0 SESSION SENDDATA CONTROL=SEND,QUALIFY=DATA Explanation: A server tried to allocate a SEND ERR conversation using the LU 6.2 protocol. It was not CONTROL=SEND,QUALIFY=ERROR able to do this, probably because its partner server rcrpl ACF/VTAM return code in the RPL. does not support LU 6.2 session types. fdbkrpl System Action: The server tries to establish a ACF/VTAM feedback code in the RPL. session using the LU 0 protocol. User Action: If the server succeeds in establishing an LU 0 session and NetView FTP issues message DVG029I, no action is required. If it does not succeed, NetView FTP issues another message that explains why not.

Chapter 1. NetView FTP Messages 23 DVG068I Ÿ DVG074I

For more information about the ACF/VTAM codes in this message, refer to the VTAM Programming for DVG072I PARAMETER WITH KEYWORD keyword LU 6.2 manual for your operating system. IS NOT VALID WHEN USING JOB ALLOCATION

DVG068I APPC SECURITY PARAMETERS ARE NOT Explanation: The file-transfer request specified a ACCEPTED ddname, indicating that job allocation, not dynamic allocation, was to be used. The request also specified the parameter whose keyword is shown in Explanation: The remote server rejected the this message, but this parameter is valid for dynamic allocation of a conversation, indicating that the APPC allocation only. security parameters received in the VTAM Function Management Header 5 (FMH5) are not valid. keyword Keyword of the parameter, as used with the batch job interface. System Action: The request is terminated. System Action: If this error is detected by: User Action: Correct the APPC security parameters and resubmit the request. Ÿ An interface routine, NetView FTP rejects the request. Ÿ A server, the file transfer ends and NetView FTP DVG069I CONVERSATION ALLOCATED WITH luname AT changes the status of the request to finished. hh:mm:ss USING AN LU TYPE 6.2 SESSION Or, for NetView FTP V2.2 MVS: User Action: Correct the error and resubmit the DVG069I CONVERSATION ALLOCATED WITH luname AT request. hh:mm:ss DVG073I CONVERSATION WITH luname ABNORMALLY Explanation: A server allocated an APPC DEALLOCATED BY REMOTE SERVER conversation with a remote server using an LU type 6.2 session. Explanation: A failure occurred that the remote luname LU name of the remote server. server is unable to correct. Probably the remote hh:mm:ss server terminated abnormally. This message is Time the session started: hh = hour, mm accompanied by message DVG065I. = minute, ss = second. luname LU name of the remote server. System Action: Processing continues. System Action: The status that NetView FTP gives User Action: None. the request depends on the value of the Automatic Transfer Restart parameter for that request. User Action: If the status of the request is: DVG071I PARAMETER WITH KEYWORD keyword MUST BE SPECIFIED FOR THE FUNCTION Ÿ Waiting, no action is required. function Ÿ Finished, and you want to reestablish the file transfer, correct the error at the remote site and Explanation: A queue handler command was resubmit the file-transfer request. issued and the Function parameter had the value Ÿ Finished, and you do not want to reestablish the function. file transfer, no action is required. keyword Keyword of the parameter, as used with the batch job interface. DVG074I CONVERSATION NOT ALLOCATED WITH function The value of the Function parameter, as luname; used with the batch job interface. REMOTE SERVER COULD NOT ACCEPT Possible values are: ANOTHER CONVERSATION Ÿ ADD Ÿ DELETE Explanation: The remote server cannot accept the Ÿ MODIFY conversation for one of the following reasons: Ÿ QRYADM Ÿ It reached its limit for remotely initiated Ÿ QUERY conversations. Ÿ QRYALL Ÿ DELALL Ÿ It is running in single mode and is already in Ÿ DELFIN conversation or is not available for remotely Ÿ FORCEDEL initiated conversations. Ÿ RESTART Ÿ It does not have enough virtual storage to Ÿ CHANGEPW (VSE) accept another conversation. Ÿ REBUILD (VSE). Ÿ It is running under VM, and there is no file System Action: The function is not performed. server machine available. User Action: When you have corrected the error, Ÿ It is defined as LOCAL and cannot accept a reissue the queue handler command. REMOTE request.

24 NetView FTP Messages and Codes DVG075I Ÿ DVG078I

This message is accompanied by message System Action: If the session was being DVG065I. established for the first time and if the file-transfer request specifies the name of a server group, luname LU name of the remote server. NetView FTP tries to establish a session with System Action: If the conversation was being another logical unit in the server group. If there are established for the first time and if the file-transfer no more untried logical units left in the server group request specifies the name of a server group, or if the request specified a remote LU name, NetView FTP tries to establish a conversation with NetView FTP changes the status of the file-transfer another logical unit as defined in the server group. If request to waiting. there are no more untried servers left in the server User Action: None. group or if the request specified a remote LU name, NetView FTP changes the status of the file-transfer request to waiting. DVG077I CONVERSATION WITH luname PREMATURELY If the error occurred because the server was defined DEALLOCATED as local, NetView FTP changes the status of the file-transfer request to finished. Explanation: A failure occurred that caused the User Action: None. conversation with luname to prematurely terminate. Probably, the remote server terminated abnormally. This message is accompanied by message DVG075I SESSION NOT STARTED WITH luname; DVG065I. LOGICAL UNIT IS UNUSABLE luname LU name of the remote server. System Action: The status that NetView FTP gives Explanation: The server tried to establish a session the request depends on the value of the Automatic with the logical unit named in the message but the Transfer Restart parameter for that request. name is neither available nor recognizable. Possibly, the LU name is not defined in ACF/VTAM or the User Action: If the status of the request is: logical unit belongs to an adjacent SSCP to which no Ÿ Waiting, no action is required. SSCP-SSCP session is active. This message is accompanied by message DVG065I. Ÿ Finished, and you want to reestablish the file transfer, correct the error and resubmit the luname LU name of the remote server. file-transfer request. System Action: If the session was being Ÿ Finished, and you do not want to reestablish the established for the first time and if the file-transfer file transfer, no action is required. request specifies the name of a server group, NetView FTP tries to establish a session with another logical unit as defined in the server group. If DVG078I CONVERSATION WITH luname DEALLOCATED there are no more untried logical units left in the server group or if the request specified a remote LU Explanation: The conversation with luname no name, NetView FTP changes the status of the longer exists. Possibly, a severe error occurred that file-transfer request to finished. interrupted the conversation. This message is User Action: Make sure the logical unit is available accompanied by message DVG065I. and its name is defined in the server group table. luname LU name of the remote server. Reestablish the file transfer, correct the error, and resubmit the file-transfer request. Otherwise, no System Action: The status that NetView FTP gives action is required. the request depends on the value of the Automatic Transfer Restart parameter for that request. User Action: If the status of the request is: DVG076I SESSION NOT STARTED WITH luname; REMOTE SERVER TEMPORARILY NOT Ÿ Waiting, no action is required. AVAILABLE Ÿ Finished, and you want to reestablish the file-transfer request, correct the error and Explanation: The server tried to establish a session resubmit the file-transfer request. with luname but the logical unit is temporarily Ÿ Finished, and you do not want to reestablish the inactive. Possibly, the remote server is not started. file transfer, no action is required. This message is accompanied by message DVG065I. luname LU name of the remote server.

Chapter 1. NetView FTP Messages 25 DVG079I Ÿ DVG084I

DVG079I NETVIEW FTP SUCCESSFULLY RECOVERED DVG082W DELETION OF CHECKPOINT RECORD FAILED; FROM VTAM STORAGE SHORTAGE FILE TRANSFER SUCCESSFULLY COMPLETED

Explanation: NetView FTP successfully recovered Explanation: After successfully transferring the from an ACF/VTAM storage shortage. This message data set, the receiving server tried to delete the is accompanied by message DVG065I. checkpoint record, but failed. The cause of the failure is explained in message DVG043I or System Action: Processing continues. DVG044I. These messages are written to the log file User Action: If this message occurs repeatedly, of the checkpoint manager virtual machine. check if ACF/VTAM has sufficient buffers available. System Action: The server ignores the error and continues the termination processing for the file DVG080I FILE TRANSFER RESTARTED FROM transfer. CHECKPOINT User Action: Contact your system administrator. Or, for NetView FTP V2.2 MVS: Checkpoint records that are not cleared can fill up DVG080I FILE TRANSFER RESTARTED FROM restart the checkpoint data set. In transfers with NetView point FTPs other than NetView FTP V2.2 MVS, these records can also cause problems during subsequent Explanation: The server restarted an interrupted transfers of the same data set. file transfer.

For NetView FTP V2.2 MVS, restart point can be: DVG083I RECORD/BYTE COUNTS NOT EQUAL; BEGINNING SENT = sss; One of the following occurred: RECEIVED = rrr Ÿ A server restarted an interrupted file transfer. The corresponding request Explanation: After transferring a data set, the specified that the server was not to sending server transfers the count of records or restart the file transfer from a bytes sent to the receiving server, which compares it checkpoint. to the count of the records or bytes received. The values of the two counts do not match. Ÿ A server tried to restart an interrupted file transfer from a checkpoint, but the sss Record or byte count at sending location. server could not find a checkpoint rrr Record or byte count at receiving location. record for the file transfer. System Action: The transfer ends and NetView CHECKPOINT FTP changes the status of the request to finished. A server restarted an interrupted file User Action: The transfer of the data set was not transfer using the checkpoint recorded in successful and the output data set is probably in the checkpoint data set. error. Possibly, there is a NetView FTP program System Action: Processing continues. error. Contact your IBM Support Center. User Action: None. DVG084I DATA SET NAME SPECIFIED IN REQUEST AND DVG081I FILE TRANSFER STARTED FROM BEGINNING IN SERVER JOB DD STATEMENT ARE OF DATA SET DIFFERENT; DATA SET NAME SPECIFIED IN REQUEST = name; Explanation: One of the following occurred: DATA SET NAME (DSN) SPECIFIED IN DD Ÿ A server started a new file transfer. STATEMENT = name NetView FTP other than NetView FTP V2.2 MVS: Explanation: The file-transfer request specified a Ÿ A server restarted an interrupted file transfer. ddname indicating that job allocation is to be used. The corresponding request specified that the A data-set name was also specified in the request. server was not to restart the file transfer from a These names are different. checkpoint. System Action: The transfer ends and NetView Ÿ A server tried to restart an interrupted file FTP changes the status of the request to finished. transfer from a checkpoint, but the server could not find a checkpoint record for the file transfer. User Action: Correct whichever data-set name is in error and resubmit the request. System Action: Processing continues. User Action: None.

26 NetView FTP Messages and Codes DVG085W Ÿ DVG088I

dsname Name of data set. DVG085W ERROR DURING CHECKPOINT DATA SET type Data-set type or file organization: HANDLING; FILE TRANSFER CONTINUES VSAM VSAM data set PS Physical sequential data set stored on DASD (other than Explanation: An error occurred when the server NetView FTP V2.2 MVS) accessed the checkpoint data set. Physical sequential data set System Action: Processing continues. If the stored on DASD or tape file-transfer is interrupted, NetView FTP might not be (NetView FTP V2.2 MVS): able to restart it from a checkpoint. NetView FTPs the label type of the tape is other than NetView FTP V2.2 MVS might instead indicated by lab-type restart it from the beginning of the data set. LAB Physical sequential data set stored on labeled tape (other User Action: If the error persists, contact your than NetView FTP V2.2 MVS) system administrator. Check the checkpoint data UNLAB Physical sequential data set set; you might have to redefine it. stored on unlabeled tape This message is accompanied by message DVG043I (other than NetView FTP V2.2 or DVG045I. Examine this message to find out more MVS) about the error. PO Partitioned organized data set TAPE Physical sequential data set stored on labeled or DVG086W NO CHECKPOINT RECORD FOUND unlabeled tape. lab-type Label type of the tape Explanation: Restart was requested, but no (NetView FTP V2.2 MVS) checkpoint record exists for this request. SL Labeled tape System Action: The file transfer starts from the beginning. NL Unlabeled tape. If the file status option in the initial request was System Action: The transfer ends. The status of MUSTNOTEXIST and the data set was already the request is changed to finished. allocated before the file transfer was interrupted, the User Action: Correct whichever data-set type or file restart might not be successful (NetView FTP V2.2 organization is in error and resubmit the request. MVS only). User Action: DVG088I MEMBER NAME SPECIFIED FOR RECEIVING NetView FTP V2.2 MVS: If the restart failed because DATA SET BUT NOT FOR SENDING DATA SET the receiving data set was already allocated, check if it can be deleted. If so, delete it and restart the file Explanation: A request to transfer a single member transfer manually. from one PDS to another specifies a member name Other NetView FTP: None. for the receiving data set, but does not specify one for the sending data set. Such a request must contain one of the following: DVG087I DATA SET TYPE SPECIFIED IN REQUEST AND RETRIEVED FROM SYSTEM ARE DIFFERENT; Ÿ A member name for the sending data set only DATA SET NAME = dsname Ÿ A member name for both data sets. DATA SET TYPE SPECIFIED IN REQUEST = System Action: The transfer ends and the status of type the request is changed to finished. DATA SET TYPE RETURNED FROM SERVICES User Action: Submit a new request, with a member = type name for either the sending data set or both data Or, for NetView FTP V2.2 MVS: sets. DVG087I FILE ORGANIZATION AND LABEL TYPE SPECIFIED IN REQUEST AND RETRIEVED FROM SYSTEM ARE DIFFERENT; DATA SET NAME = dsname FILE ORGANIZATION SPECIFIED IN REQUEST = type; LABEL TYPE = lab-type FILE ORGANIZATION RETURNED FROM SYSTEM SERVICES = type

Explanation: The data-set type or file organization specified in a file-transfer request does not match the data-set organization (DSORG) parameter. If the request specifies a DD name, the DSORG in the DD statement may be incorrect.

Chapter 1. NetView FTP Messages 27 DVG089I Ÿ DVG098I

DVG089I FILE ID SPECIFIED IN REQUEST AND IN DLBL DVG093I FILE STATUS OPTION CHANGED FROM OR TLBL STATEMENT ARE DIFFERENT; filstat1 TO filstat2 FILE ID SPECIFIED IN REQUEST = name; FILE ID SPECIFIED IN DLBL OR TLBL Explanation: In your file-transfer request, you either STATEMENT = name specified MAYEXIST for the file status option or you omitted this parameter. NetView FTP changed the Explanation: The file-transfer request specified a file status option to the appropriate value, that is: file name, indicating that job allocation is to be used. MUSTNOTEXIST If the file does not already exist When job allocation is used, you do not need to MUSTEXIST If the file already exists. specify a file ID in the DLBL or TLBL statements. If you do, the file ID in the DLBL or TLBL statements System Action: Processing continues. must be the same as that specified in the request. User Action: None. This message is issued when the IDs are different. System Action: The transfer ends and NetView DVG094I DCB AND SPACE PARAMETERS ARE FTP changes the status of the request to finished. IGNORED FOR FILE STATUS OPTION User Action: Correct whichever file ID is in error MUSTEXIST and resubmit the request. Explanation: You specified DCB and space DVG090I MEMBER member IN pds name MAY RESULT parameters for a file that already exists. FROM THIS INCOMPLETE FILE TRANSFER System Action: Processing continues. User Action: None. Explanation: The file transfer was interrupted. The receiving data set of the file transfer is a PDS with the name pds name. It contains a member named DVG095I FILE ACCESS OPTION CHANGED FROM member that is only partially full because of the filacc1 TO filacc2 incomplete file transfer. This member is deleted when the file transfer is restarted. Explanation: You did not specify the correct file System Action: None. access option for VSAM data sets in your file-transfer request. NetView FTP replaced the file access User Action: Either restart the file transfer, or option exclusive with the file access option shared. delete the member member. System Action: Processing continues. User Action: None. DVG091I INVALID RECORD FOUND IN CHECKPOINT DATA SET. CHECKPOINT KEY: key; CHECKPOINT AREA: area DVG096I FILE filename IS DELETED DUE TO END-OF-PROCESSING OPTION Explanation: During a transfer restart, an invalid record was found in the checkpoint data set. Explanation: In your file-transfer request, you key The first 100 bytes of the key of the specified with the end-of-processing option DELETE invalid checkpoint record. for either the sending or the receiving file that, depending on the outcome of the file transfer, this file area The contents of the checkpoint record is to be deleted after the transfer. area that contains the invalid data. System Action: Processing continues. System Action: The checkpoint record is deleted. The transfer is started from the beginning of the file. User Action: None. User Action: If the problem occurs for several times, contact your IBM Support Center. DVG098I REMOTE TRANSFER PROGRAM HAS AN INSUFFICIENT SERVICE LEVEL DVG092I END-OF-PROCESSING OPTION CHANGED FROM Explanation: The NetView FTP at your system eop1 TO eop2 detected that the transfer program at the remote system has an insufficient service level. It could be caused by one of the following: Explanation: The end-of-processing option was either not specified in the request or was changed for Ÿ The remote transfer program is FTP Version 2.2 a transfer restart. NetView FTP changed the but has installed the compatibility PTF required end-of-processing option to the appropriate value. to communicate with NetView FTP. System Action: Processing continues. Ÿ The remote transfer program is an FTP with a level lower than FTP 2.2. User Action: None. Ÿ The remote program is any other than FTP or NetView FTP.

28 NetView FTP Messages and Codes DVG100I Ÿ DVG110I

The transfer program did not start. System Action: Processing continues. DVG104I conv DATA CONVERSION FROM CCSID ccss TO CCSID ccst NOT SUPPORTED User Action: Contact your administrator and ask for the appropriate PTF to be installed at the remote system. After it has been installed, resubmit the Explanation: You specified coded character set request. identifiers to convert character data, but the specified character sets are not supported by the system. conv Conversion type DVG100I MESSAGE FROM luname; ccss Source CCSID FTP LEVEL = ftplevel; ccst Target CCSID. MESSAGE = message System Action: The file transfer ends and NetView FTP changes the status of the request to finished. Explanation: A message from the remote server was received. It shows that an error occurred at the User Action: Omit the character-data conversion remote location. The message content is not parameters or use a different CCSID combination. analyzed—it is only printed. luname LU name of the remote server. DVG105I DATA STARTING WITH char CANNOT BE ftplevel The FTP level of the remote server, CONVERTED FROM CCSID ccss TO CCSID ccst where: 4 FTP Version 2.2 with the Explanation: Part of the data could not be compatibility PTF for NetView converted with the specified coded character set FTP identifiers. 5 NetView FTP Version 1 for MVS char The first character that could not be without the AFF converted ccss Source CCSID 6 NetView FTP Version 1 for MVS ccst Target CCSID. with the AFF System Action: The file transfer ends and NetView 7 NetView FTP V2 MVS, NetView FTP changes the status of the request to finished. FTP VM, and NetView FTP VSE. User Action: Either specify the correct CCSID for message Message received from remote server. the data, or omit conversion, or erase the character System Action: The transfer ends. The that could not be converted. file-transfer request is treated as described in the message sent from the remote server. DVG106I RECORD PADDING OPTION = padchar User Action: Refer to the explanation of the message sent from the remote server and take Explanation: Record padding option was specified; whatever action it recommends. padchar identifies the padding character. System Action: If necessary, the receiving NetView DVG102I CHARACTER DATA CONVERSION = conv FTP padds the records with the specified padding character. Explanation: This message tells you whether User Action: None. Character data conversion was requested. conv One of the following: DVG110I NO MESSAGE PROVIDED BY USER-EXIT YES Character data conversion was ROUTINE routine FOR FUNCTION function; requested. RETURN CODE = retcd NO Character data conversion was not requested. Explanation: The server received a nonzero return System Action: Processing continues. code from the pre-transfer or post-transfer user-exit routines. However, no message was found in the User Action: None. message area, so this standard message was issued instead. DVG103I CCSID = ccsid routine Name of the user-exit routine. function OPEN, CLOSE, P, or C. For details, see Explanation: This message is issued, if character NetView FTP Customization. data conversion was requested. retcd Return code from exit routine. ccsid Coded character set identifier of the file. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 29 DVG111I Ÿ DVG121I

System Action: If a pre-transfer user-exit routine System Action: If the routine was the pre-transfer temporarily rejected a file-transfer request, then the or post-transfer user-exit routine, the server stops. If transfer ends. The status that NetView FTP gives the routine was a user-written file handler, the file the request depends on the value of the Automatic transfer ends. NetView FTP changes the status of Transfer Restart parameter for that request: the file-transfer request to finished. Ÿ If the value is YES, NetView FTP gives the User Action: Check the ABEND code in the request the status waiting; the request is message library system codes book for your reprocessed later. operating system. Ÿ If the value is NO, NetView FTP gives the request the status finished; the request is not DVG114I SECURITY VERIFIED BY USER-EXIT ROUTINE reprocessed later.

Otherwise, the transfer ends and NetView FTP Explanation: The security parameters specified in changes the status of the file-transfer request to the file-transfer request have been verified by the finished. pre-transfer user-exit routine. NetView FTP does no User Action: Check what caused the user-exit further security checking. routine to issue this return code and take whatever System Action: Processing continues. action is appropriate. User Action: None.

DVG111I MESSAGE FROM USER-EXIT ROUTINE routine; MESSAGE = message DVG115I POST-TRANSFER JOB SUBMISSION PREVENTED BY USER-EXIT ROUTINE

Explanation: A pre-transfer or post-transfer user-exit routine passed a message to a server for Explanation: The request specified post-transfer printing. If the message is longer than 180 job submission, but the pre-transfer or the characters, NetView FTP truncates the message and post-transfer user-exit routine at either the requesting shows the truncation with three asterisks (***) as the or the responding system prevented the submission last three characters. of post-transfer jobs. routine Name of the user-exit routine. System Action: Processing continues, but at the message Message text. system where the user-exit routine prevented the job submission no post-transfer jobs are submitted. System Action: Processing continues. User Action: None. User Action: None.

DVG121I macro ERROR; DVG112I SERVER LOADED USER-EXIT ROUTINE routine RETURN CODE = retcd; LENGTH = length; Explanation: A server successfully loaded the MODULE = modname; pre-transfer or post-transfer user-exit routine with the OFFSET = offset name routine into its address space. System Action: Processing continues. Explanation: An error occurred in a NetView FTP component when it attempted to obtain or release User Action: None. dynamic virtual storage. macro Macro that encountered the error: DVG113I SERVER FAILED TO LOAD USER-EXIT Ÿ GETMAIN or GETVIS ROUTINE routine; Ÿ FREEMAIN or FREEVIS. SYSTEM COMPLETION (ABEND) CODE OF THE LOAD MACRO = abendcd; retcd Return code from the macro. For more REGISTER 15 RETURN CODE= reg15 information about this return code, refer to the description of the supervisor services and macroinstructions for your operating Explanation: The server tried to load a user-exit system. routine from the available load libraries, but it was not successful. length Length of area to be obtained or released (value not hexadecimal). routine Name of user-exit routine. modname abendcd System completion (ABEND) code from Name of the module where the macro LOAD macroinstruction. was issued. reg15 Register 15 contains a reason code in offset Offset within the module where the macro some cases. was issued (hexadecimal value).

30 NetView FTP Messages and Codes DVG122I Ÿ DVG133I

System Action: If the error occurs independently of User Action: Analyze the return code using the a file transfer, the NetView FTP component that system data administration book for your operating issued the message stops. system. If the error occurs during a file transfer, the file If the problem was due to a user error, correct the transfer ends and NetView FTP changes the status DD Name specified in your request or contact your of the request to finished; the server does not stop. system administrator for the DD Name specified in the server JCL statements. If you solved the User Action: If the problem persists for: problem, then resubmit the request or restart the Ÿ FREEMAIN or FREEVIS, contact your IBM queue handler. Support Center. If the problem was not due to a user error and the Ÿ GETMAIN or GETVIS, increase the size of the problem persists, contact your IBM Support Center. address space or partition in which the NetView FTP component that issued the message runs. DVG125I FILE ID SPECIFIED IN STATEMENT WITH DLBL OR TLBL NAME name COULD NOT BE DVG122I macro MACRO FAILED; RETRIEVED; RETURN CODE = retcd RETURN CODE FROM macro MACRO=retcd

Explanation: A NetView FTP component issued an Explanation: A NetView FTP component attempted ESTAE or SNAP macroinstruction that failed. to retrieve the file ID from a DLBL or TLBL statement macro Macro that failed: but failed. Ÿ ESTAE name The name of the file as specified in the Ÿ SNAP. File Name parameter. retcd Return code from the macro. macro The name of the macro used but which was not successful. System Action: For: retcd The code returned by the macro. Ÿ ESTAE, the abnormal termination exit is not activated System Action: If this error occurred during the Ÿ SNAP, no storage dump is taken. processing of: NetView FTP processing continues. Ÿ A server, the transfer ends and NetView FTP changes the status of the corresponding User Action: Analyze the problem using one of the file-transfer request to finished. following: Ÿ The queue handler, the queue handler stops. Ÿ MVS/XA Macro Instruction Reference Ÿ MVS/ESA Application Development Macro User Action: Analyze the return code using the Reference. following: Ÿ VSE/AF Initial Program Load and Job Control Ÿ VSE/AF Diagnosis Reference Supervisor DVG124I DATA SET NAME SPECIFIED IN DD Ÿ VSE/ESA System Macros Reference. STATEMENT WITH NAME name COULD NOT BE RETRIEVED; If the problem was due to a user error, correct the RETURN CODE FROM macro MACRO = retcd File Name specified in your request or contact your system administrator for the name specified in the server DLBL or TLBL statements. If you solved the Explanation: A NetView FTP component attempted problem, then resubmit the request or restart the to retrieve a data-set name from a DD statement NetView FTP partition. (MVS), but failed. If the problem was not due to a user error and the name The name of the DD statement specified problem persists, contact your IBM Support Center. in the File Name parameter. macro The name of the macro used but which was not successful. DVG133I ERROR IN MACRO macro; RETURN CODE = retcd retcd The code returned by the macro. System Action: If this error occurred during the Explanation: One of the macros that NetView FTP processing of: used encountered an error. A server, the transfer ends and NetView FTP Ÿ macro The macro that encountered an error; it changes the status of the corresponding can be any of the following: file-transfer request to finished. EXTRACT Extracts information for tape The queue handler, the queue handler stops. Ÿ units. SUBSID Asks for information from operating system or notifies the operating system that a VSE subsystem is working.

Chapter 1. NetView FTP Messages 31 DVG141I Ÿ DVG144I

CPCOM Sends file-transfer completion messages to a VM user. The DVG142I RECORD recnum CONTAINS USER DATA macro return code is taken WHOSE LENGTH EXCEEDS THE MAXIMUM OF directly from the CP MSG maxlen ALLOWED FOR THE SPECIFIED DATA command. Possible values SET are 30, 45, and 57. These values usually indicate that a Explanation: NetView FTP received a record user ID is not valid or was not whose user data exceeds the maximum allowed for receiving. the record length defined for the receiving data set. LABEL Gets label information. recnum The number of the record in error. retcd Return code from macro. maxlen The maximum allowable length of user System Action: Processing continues but NetView data within one record of the receiving FTP may terminate during subsequent processing. data set. User Action: If the error did not cause NetView System Action: The file transfer ends and NetView FTP to terminate, stop the NetView FTP partition. FTP changes the status of the request to finished. For further information, see one or more of the User Action: Correct the error and resubmit the following: request. Ÿ VSE/AF Initial Program Load and Job Control Ÿ VSE/AF Diagnosis Reference Supervisor Ÿ VSE/ESA System Macros Reference DVG143I LENGTH OF RECORD recnum IS NOT EQUAL Ÿ VM CP Commands. TO THE RECORD LENGTH reclen OF THE RECEIVING FILE Correct the error before restarting the NetView FTP partition. Explanation: The length of a sending record is not equal to the length of the record at the receiving DVG141I INVALID RECORD LENGTH length location. Transfer record of variable or smaller length into a data set with fixed-length record, specify Explanation: The receiving server received a a padding character in the request. record that does not fit into its I/O buffer. The recnum The number of the record in error. following conditions can cause this error: reclen The length of a record at the receiving Ÿ The record length is zero or greater than 32 760 location. for a fixed-length record. System Action: The file transfer ends and NetView Ÿ The record length is zero or greater than 32 756 FTP changes the status of the request to finished. for a variable-length record. User Action: Correct the error and resubmit the Ÿ The length of a fixed-length or fixed-blocked request. record sent is not equal to the record length as specified at the receiving location. DVG144I INVALID RECORD LENGTH FOR RECORD Ÿ A variable, variable-blocked, or undefined record recnum exceeds the physical block size defined for the receiving data set. Explanation: The length of a record is greater than length Length of the record in error. the (maximum) length allowed for the data set. System Action: The transfer ends and NetView recnum The number of the record in error. FTP changes the status of the request to finished. System Action: The file transfer ends and NetView User Action: Correct the error that caused this FTP changes the status of the request to finished. message to be issued and resubmit the file-transfer request. User Action: Use a bigger record size for the receiving data set and resubmit the file-transfer request.

32 NetView FTP Messages and Codes DVG149I Ÿ DVG155I

DVG149I ERROR DURING VALIDATION OF USER userid; DVG153I ERROR DURING VALIDATION OF USER userid; ERROR CODE = error-code RACROUTE RETURN CODE = xx; RACROUTE RETURN CODE = yy; Explanation: The specified user ID and the RACROUTE REASON CODE = zz password could not be verified at the local system. The message contains the VSE Access Control error Explanation: The specified user ID and the code in hexadecimal format. password could not be verified at the local system. The message contains the SAF return and reason userid User ID codes, and indicates a security violation. error-code userid User ID VSE Access Control error code: xx Hexadecimal return code from RACROUTE. 02 GETVIS failure 04 Invalid password yy Hexadecimal return code from RACROUTE 08 Invalid user ID ENVIR=CREATE. 10 LOGON phase not found zz Hexadecimal reason code from RACROUTE 20 Resource table load failure ENVIR=CREATE. 40 Lock not possible. System Action: The transfer ends and NetView System Action: The transfer ends and NetView FTP changes the status of the request to finished. FTP changes the status of the request to finished. User Action: Supply the correct security User Action: Supply the correct parameters, or parameters or check whether the correct system was check whether the correct system was called, or contacted. Correct the errors and resubmit the both. Correct the errors and resubmit the file-transfer request. file-transfer request. The return codes and the RACROUTE macros are described in: DVG150I ACCESS CONTROL USER ID HAS AN Ÿ MVS/XA Macro Instruction Reference INCORRECT LENGTH; USER ID = userid Ÿ MVS/ESA Application Development Macro Reference. Explanation: The access control user ID specified in a request has an incorrect length. DVG154I REQUEST CONTAINS SECURITY PARAMETERS System Action: NetView FTP rejects the request. FOR THIS SYSTEM, User Action: Specify the correct user ID and BUT ACCESS CONTROL FACILITY IS NOT resubmit the request. ACTIVE

DVG151I ACCESS CONTROL PASSWORD HAS AN Explanation: The file-transfer request specified INCORRECT LENGTH security parameters for the system from which NetView FTP issued this message. However, the user ID and password specified could not be verified Explanation: The access control password in a because the access control facility (RACF, Access request has an incorrect length. Control, or other facility) is not installed or is not System Action: NetView FTP rejects the request. active, or no pre-queuing user-exit routine was loaded that could prevent specification of security User Action: Specify the correct password and parameters. resubmit the request. System Action: The security parameters are ignored and the server continues processing. DVG152I ACCESS CONTROL GROUP ID WILL NOT BE User Action: Check whether security parameters USED FOR A VSE NODE; GROUP ID = groupid are required. If not, omit them in subsequent file-transfer requests. Explanation: A group ID was specified in the request for a file at a VSE location. Access Control does not use group IDs, it ignores the value you DVG155I USER userid CANNOT ACCESS FILE file-id specified. System Action: Processing continues. Explanation: One of the following occurred: User Action: Do not specify a value for this Ÿ The request contained a value for the User ID parameter for files at VSE locations. security parameter. NetView FTP tried to access a file using the authorization of the user specified for this parameter, but that user was not authorized to access the file.

Chapter 1. NetView FTP Messages 33 DVG156I Ÿ DVG159I

Ÿ The request did not contain a value for the User ID security parameter. However, the JCL DVG158I ERROR DURING RETRIEVAL OF RACF statements in the startup job for the NetView PARAMETERS FOR USER userid; FTP partition at the system on which the file is RACROUTE RETURN CODE = racrretcd stored contained an ID statement. NetView FTP RACXTR RETURN CODE = racxretcd tried to access the file using the authorization of RACXTR REASON CODE = racxrsncd the user specified in this ID statement, but that user was not authorized to access the file. Explanation: A file-transfer request specified that Ÿ The request did not contain a value for the User the server was to automatically retrieve values for ID security parameter and the startup job for the access security parameters and insert them into the NetView FTP partition did not contain an ID request. When the server used the router interface statement. NetView FTP tried to access the file to call the RACXTR macro, it encountered an error using no authorization. It was not authorized to and failed to retrieve the values. access the file. userid User ID of the user whose access userid The user ID, if any, that NetView FTP security parameters were being used to try and access the file. If no user retrieved. ID was specified in the request and no ID racrretcd Return code from the RACROUTE statement was specified in the startup job macroinstruction. for the NetView FTP partition, this field is racxretcd Return code from the RACXTR blank. macroinstruction. file-id The file ID of the file that NetView FTP racxrsncd Reason code from the RACXTR used to try to access the file. macroinstruction. System Action: Program or transfer ends. System Action: The transfer ends and NetView FTP changes the status of the request to finished. User Action: Check that the correct file ID was specified in the request. If so, either specify the User Action: Either correct the RACF error or correct values for the security parameters or arrange specify the access security parameters explicitly. for the NetView FTP partition of the server that is to Refer to the RACF manual. access the file to be given the necessary authorization. DVG159I SECURITY PARAMETERS REQUIRED BUT NOT AVAILABLE DVG156I REQUEST CONTAINS SECURITY PARAMETERS BUT SERVER IS NOT LINKED TO AN Explanation: The value of the SECPAR parameter AUTHORIZED LIBRARY in the server’s initialization control statements is YES but the request did not contain values for the access Explanation: A request specified access security security parameters. parameters to be used to create a temporary RACF If the system that issued this message is an MVS environment, but the server that processed the system the server at this system tried to retrieve request was not linked to an Authorized Program values for the security parameters automatically, but Facility (APF) library. they were not available. System Action: The transfer ends and NetView If the system that issued this message is a VSE FTP changes the status of the file-transfer request to system the server at this system needed access finished. security parameters specified in your file-transfer User Action: Contact your system administrator. request. System Action: The file transfer ends and NetView FTP changes the status of the request to finished. DVG157I RACF NOT ACTIVE; RACF PARAMETERS CANNOT BE RETRIEVED User Action: If the system that issued this message is an MVS system you must either specify values for the access security parameters explicitly Explanation: A file-transfer request specified that or have your system administrator define your RACF the server was to automatically retrieve values for user ID and password at this system. access security parameters and insert them into the request. The server that processed the request If the system that issued this message is a VSE failed to retrieve the values because RACF was not system you must specify values for the access active on its system. security parameters explicitly in your file-transfer request. System Action: If the value of the SECPAR server control statement is YES, the server rejects the request. If the value is NO, the server tries to access the data set using its own authorization. User Action: If the request was rejected, either start RACF or specify the access security parameters explicitly.

34 NetView FTP Messages and Codes DVG160I Ÿ DVG164I

DVG160I DATA SET TYPE ERROR; DVG162I CHECKPOINT RECORD NOT PASSED TO THE TYPE OF ONE DATA SET WAS “USER” USER-WRITTEN FILE HANDLER AND THE OTHER WAS NOT Or, for NetView FTP V2.2 MVS: Or, for NetView FTP V2.2 MVS: DVG162I FILE TRANSFER START FROM BEGINNING OF DVG160I FILE ORGANIZATION ERROR; DATA SET SUPPORTED FOR THE THE ORGANIZATION OF ONE FILE WAS USER-WRITTEN FILE HANDLER “USER” AND THE OTHER WAS NOT Explanation: NetView FTP other than NetView FTP Explanation: If the data-set type or file organization V2.2 MVS: of one data set is USER, then the data-set type or NetView FTP did not pass a checkpoint record to a file organization of the other must also be USER. user-written file handler that was to resume an interrupted file transfer. This might be because the System Action: If this error is detected by: file-transfer request specified that, in case of an Ÿ An interface routine, NetView FTP rejects the interruption, the file transfer was not to be started request. from a checkpoint. Ÿ A server, the file transfer ends and NetView FTP NetView FTP V2.2 MVS: A server started a new file changes the status of the request to finished. transfer. User Action: Correct the error and resubmit the System Action: NetView FTP resumes transferring request. the file from the beginning. User Action: Check that the user-written file DVG161I CHECKPOINT RECORD PASSED TO handler that wrote the checkpoint record provided the USER-WRITTEN FILE HANDLER correct checkpoint key data (does not apply to Or, for NetView FTP V2.2 MVS: NetView FTP V2.2 MVS). DVG161I FILE TRANSFER RESTART FROM restart point SUPPORTED FOR USER-WRITTEN FILE HANDLER DVG163I INVALID CHECKPOINT RECORD FOUND FOR FILE TRANSFER WITH USER-WRITTEN FILE Explanation: NetView FTP passed a checkpoint HANDLERS record to a user-written file handler so that it could resume an interrupted file transfer. Explanation: When a file transfer is interrupted, the receiving server flags the checkpoint record it writes For NetView FTP V2.2 MVS, restart point can be: as belonging to a file transfer that uses either BEGINNING user-written file handlers or NetView FTP file One of the following occurred: handlers. Before restarting such a file transfer from Ÿ A server restarted an interrupted file a checkpoint, a server determined that the flag of the transfer. The corresponding request checkpoint record it retrieved was pertaining to a specified that the server was not to user-written file handler. Either the value of the restart the file transfer from a Data-Set Type parameter was changed when the checkpoint. file-transfer request was resubmitted, or the file handler supplied incorrect checkpoint key data with A server tried to restart an interrupted Ÿ the OPEN function. file transfer from a checkpoint, but the server could not find a checkpoint System Action: The transfer ends and NetView record for the file transfer. FTP changes the status of the request to finished. CHECKPOINT User Action: Correct the error and resubmit the A server restarted an interrupted file request. transfer using the checkpoint recorded in the checkpoint data set. DVG164I INVALID CHECKPOINT RECORD FOUND FOR System Action: Processing continues. TRANSFER WITH NETVIEW FTP FILE User Action: None. HANDLERS

Explanation: When a file transfer is interrupted, the receiving server flags the checkpoint record it writes as belonging to a file transfer that uses either user-written file handlers or NetView FTP file handlers. Before restarting such a file transfer from a checkpoint, a server determined that the flag of the checkpoint record it retrieved was pertaining to a user-written file handler. Either the value of the Data-Set Type parameter was changed when the file-transfer request was resubmitted, or the file handler supplied incorrect checkpoint key data with the OPEN function.

Chapter 1. NetView FTP Messages 35 DVG165I Ÿ DVG171I

System Action: The transfer ends and NetView function The function that NetView FTP called FTP changes the status of the request to finished. the user-written file handler for: User Action: Correct the error and resubmit the Ÿ CLOSE request. Ÿ GET Ÿ OPEN Ÿ POINT DVG165I MESSAGE ISSUED BY USER-WRITTEN FILE Ÿ PUT. HANDLER modulename; MESSAGE = message retcd The hexadecimal return code from the user-written file handler.

Explanation: The user-written file handler, with the System Action: The transfer ends and NetView load module name modulename, passed a message FTP changes the status of the request to finished. to NetView FTP for printing. If the message is longer User Action: Contact your system administrator. than 180 characters, NetView FTP truncates the Check if the user-written file-handler module message and shows the truncation with three observes the return code rules. The functions that asterisks (***) as the last three characters. NetView NetView FTP uses with user-written file handlers and FTP can print up to ten messages after each call of the rules for return codes are described in NetView a user-written file handler. FTP Customization. System Action: Processing continues. User Action: Check the message from the DVG169I INVALID I/O AREA LENGTH FROM user-written file handler. USER-WRITTEN FILE HANDLER modulename

DVG166I RETURN CODE ISSUED BY USER-WRITTEN Explanation: Upon return from the OPEN function FILE HANDLER modulename of the user-written file handler with the load module FOR FUNCTION function; name modulename, the server expects a positive RETURN CODE = retcd value in the field that designates the length of the I/O area. This enables the server to get storage for this area. The value found was not an allowed value. Explanation: NetView FTP received an allowed but nonzero return code from the user-written file System Action: The transfer ends and NetView handler. No message was found in the message FTP changes the status of the request to finished. area. User Action: Contact your system administrator. modulename Name of user-written file handler. Check whether the user-written file handler supplies a correct I/O area length when returning from the function The function that NetView FTP called OPEN function to NetView FTP (refer to NetView the user-written file handler for: FTP Customization). Ÿ CLOSE Ÿ GET Ÿ OPEN DVG170I INVALID RECORD LENGTH FROM Ÿ POINT USER-WRITTEN FILE HANDLER modulename Ÿ PUT. Explanation: Upon return from the GET function of retcd The hexadecimal return code from the user-written file handler, with the load module the user-written file handler. name modulename, the server expects a positive System Action: Continuation of the file transfer value in the field that designates the length of the depends on the return code. record, so that the server is able to compress and User Action: Contact your system administrator. send the record. The value found was not positive, The interface functions that NetView FTP uses with or exceeded the I/O area length. user-written file handlers are described in NetView System Action: The transfer ends and NetView FTP Customization. FTP changes the status of the request to finished. User Action: Contact your system administrator. DVG168I INVALID RETURN CODE ISSUED BY Check if the user-written file handler supplies a USER-WRITTEN FILE HANDLER modulename correct record length when returning from the GET FOR FUNCTION function; function to NetView FTP (refer to NetView FTP INVALID RETURN CODE = retcd Customization).

Explanation: The user-written file handler can DVG171I name ALREADY ALLOCATED; return only specifically defined return codes to NO DYNAMIC ALLOCATION POSSIBLE NetView FTP.

modulename Name of user-written file-handler Explanation: The server attempted to dynamically module. allocate a data set, but the ddname (MVS) or filename (VSE) was already in use in this address space.

36 NetView FTP Messages and Codes DVG175I Ÿ DVG181I

name ddname (MVS) or filename (VSE) that is User Action: If your operating system is VSE/ESA*, already in use. start the NetView FTP partition in static partitions only. If your operating system is VSE/SP, solve the The server uses the ddname (MVS) or the filename problem using the error code and the function (VSE) for dynamic allocation. Possibly, one of these routines MODGRPL, LOCGRPL, GETNXGL, was used in the server startup job (MVS) or in the CLRGRPL, or GETLBL. If the problem persists, system or partition standard label area. contact your IBM Support Center. System Action: The transfer ends and NetView FTP changes the status of the request to finished. DVG177I (un)labeled TAPE(S) FOR FILE-ID = file-id User Action: Check that the file-transfer request is SHOULD BE MOUNTED IN THE FOLLOWING not in error, for example, ddname is not used in the SEQUENCE ON DEVICE devadr IF NO server startup job. If this does not correct the error, ALTERNATE DRIVE IS ASSIGNED; contact your system administrator. The server VOLSER = volser (MVS) or the NetView FTP partition must be stopped and started again without using the ddname (MVS) or filename (VSE) that NetView FTP uses for Explanation: Job allocation for tape(s) was dynamic allocation. requested and NetView FTP found the serial numbers specified. NetView FTP writes the address of the first assigned DVG175I VSE LABEL ACCESS ROUTINE routine FAILED; tape device (normally SYS001) and the volume serial RETURN CODE = retcd; numbers in the sequence in which they were FILE NAME = filename specified in the VOLSER list, to inform the operator about mount requests. Explanation: An error occurred while NetView FTP (un)labeled Labeled or unlabeled tape was writing a file label. file-id File ID As NetView FTP VSE uses VSE system routines devadr Device address when writing or reading file labels, this is a VSE volser Volume serial number. system problem. System Action: Processing continues. routine Name of the VSE system routine. Can be User Action: Mount the correct volume(s) if one of the following: necessary. Ÿ ADDLBL Note: If an alternative drive is assigned, NetView Ÿ ADDNXL. FTP cannot determine the device address of this retcd Return code (contents of register 15). drive. Therefore, you must specify the correct filename Name of the file that NetView FTP was mounting. writing a label for. System Action: Transfer ends. DVG180I NO DATA SET NAME CAN BE CREATED FOR User Action: If the problem cannot be solved using THE RECEIVING DATA SET the error code and the function routines ADDLBL or ADDNXL, contact your IBM Support Center. Explanation: The file-transfer request did not specify a data-set name for the receiving data set. Dynamic allocation is invoked for the receiving DVG176I VSE LABEL ACCESS ROUTINE routine FAILED; location to create a new data set, but a valid name RETURN CODE = retcd cannot be created, because there is no input available from which NetView FTP can build a Explanation: An error occurred while NetView FTP data-set name. was reading a file label. System Action: The transfer ends and NetView As NetView FTP VSE uses VSE system routines FTP changes the status of the file-transfer request to when writing or reading file labels, this is a VSE finished. system problem. User Action: Specify a valid name for the data set routine Can be one of the following: and resubmit the file-transfer request. Ÿ MODGRPL Ÿ LOCGRPL DVG181I NO DATA SET NAME WAS SPECIFIED FOR Ÿ GETNXGL THE RECEIVING DATA SET; NETVIEW FTP Ÿ CLRGRPL GENERATED THE DATA SET NAME: dsname Ÿ GETLBL.

retcd Return code (contents of register 15). Explanation: The file-transfer request did not System Action: Transfer ends. specify a data-set name for the receiving data set. NetView FTP can build the data set name dsname. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 37 DVG182I Ÿ DVG188I

DVG182I DYNAMIC ALLOCATION ERROR; DVG188I DYNAMIC ALLOCATION ERROR; ERROR TYPE = type; ERROR CODE = error-code DATA SET NAME = dsname; RETURN CODE = retcd; Explanation: An error has occurred during NetView INFORMATION REASON CODE = infcode; FTP’s dynamic allocation process. ERROR REASON CODE = errcode error-code One of the following: Explanation: An error occurred during dynamic allocation. 01 INCORRECT ACCESS MODE type Error type: The disk at the receiving system was found to be read-only mode P Permanent allocation error. when WRITE access was T Temporary allocation error. requested. dsname Name of the data set for which a dynamic System Action: Transmission allocation error occurred. ends. retcd Return code. User Action: Check your infcode Information reason code. request to see whether another suitable disk can be used, or errcode Error reason code. contact your system operator to System Action: The transfer ends. link the disk again with the For a permanent allocation error, NetView FTP appropriate access mode. changes the status of the request to finished. 02 NO UNUSED VIRTUAL For a temporary allocation error, the status that ADDRESS AVAILABLE NetView FTP gives the request depends on the For the linkage of default and value of the Automatic Transfer Restart parameter specified disks NetView FTP for that request. searches for currently unused User Action: Refer to the description of the virtual addresses. It starts the dynamic allocation interface return (DAIR) errors that search with address 490 and can be found in the online ISPF tutorial. For further ends with address FFF. The information, refer to: message is issued when no unused virtual address can be MVS/ESA SPL: Application Development Guide Ÿ found. Ÿ MVS/XA System Macros and Facilities Volume 1. System Action: Program ends. If it is a temporary error, the specified data set might User Action: See if some be currently in use by another address space. devices can be detached from NetView FTP’s virtual machine. If the status of the file-transfer request was changed to waiting, no action is required. If the status of the 03 NO UNUSED FILEMODE file-transfer request was changed to finished and LETTER AVAILABLE you want to transfer the file again, correct the error, For the linking of default and and resubmit the new file-transfer request. specified disks, NetView FTP searches for currently unused file modes. It starts the search with DVG185I CONTENTS OF LABEL PARAMETER LIST file mode A and ends with file contents; mode Z. The message is issued FUNCTION REQUESTED = function; if no unused file-mode letter can CONTENTS OF LABEL BUFFER FOLLOW be found. System Action: Program ends. Explanation: This message is issued if trace class 3 is specified for module DVGEYDL at a VSE User Action: See if some location. It is used for diagnostic purposes to trace devices can be detached from errors related to dynamic allocation. NetView FTP’s virtual machine. contents LABEL parameter list. 04 NO DISK AVAILABLE FOR TRANSMISSION function Function of LABEL macro. There is no CMS or VSAM disk System Action: Processing continues. available for transmission, also User Action: Contact your IBM Support Center. no SPECIFIED DISK or DEFAULT DISK. System Action: Transmission ends.

38 NetView FTP Messages and Codes DVG190I Ÿ DVG196I

User Action: Check your User Action: Check the value in the disposition request to see whether another specification in your file transmission request and suitable disk can be used, or resubmit the request. If necessary, erase an existing contact your system operator to CMS file. link the disk again with the appropriate access mode. DVG191I DISPOSITION ERROR, DATA SET IS ALREADY 05 INVALID CMS FILENAME CATALOGED; 06 INVALID ADDRESS DATA SET NAME = dsname Or, for NetView FTP V2.2 MVS: The address of the virtual device DVG191I INCORRECT END-OF-PROCESSING OPTION, that was specified does not exist DATA SET IS ALREADY CATALOGED; or is not a DASD. DATA SET NAME = dsname System Action: Program or transmission ends. Explanation: The disposition parameter (other than User Action: Check the CMS NetView FTP V2.2 MVS) or the end-of-processing disk or VSAM disk control option (NetView FTP V2.2 MVS) for a new statement specification in the non-VSAM data set specifies that it should be initialization control statement file cataloged when it is created. A test, however, or the xVMLINK statement in the indicated that a data set with this name already transmission request for correct exists in the catalog. disk identification. Correct the System Action: Transmission ends. error and restart NetView FTP or the transmission. User Action: Do one of the following: 07 WRONG DISK MODE Ÿ For NetView FTP other than V2.2 MVS change the disposition parameter to OLD No disk was accessed under the Ÿ For NetView FTP V2.2 MVS change the file given mode letter. status option to MUSTEXIST System Action: Program or Ÿ Delete the existing data set. transmission ends. Then resubmit the request. User Action: Check the CMS disk or VSAM disk control statement specification in the DVG193I DYNAMIC ALLOCATION ERROR; DATA SET IS initialization control statement file CURRENTLY INVOLVED IN ANOTHER FILE or the xVMLINK statement in the TRANSFER; DATA SET NAME = name transmission request, for correct disk identification. Correct the Explanation: The data set is currently being error and restart NetView FTP or transferred. the transmission. name Name of data set involved in file transfer. 08 DCB INFORMATION OF THE SENDING FILE UNUSABLE System Action: Current transfer continues. The file-transfer request that caused the error is rejected. The logical record length or the block size of the sending file is User Action: Wait until the current transfer finishes bigger than the maximum and then resubmit the file-transfer request. allowed for MVS. To avoid the loss of data, dynamic allocation DVG196I IDUMP MACRO ISSUED fails.

Explanation: The IDUMP macro has been issued. DVG190I DISPOSITION ERROR FOR CMS FILE file-id; The dump is sent either to the SYSDUMP data set, ERROR CODE = error-code or to SYSLST, depending on what you specified for the VSE JCL OPTION. Explanation: The disposition parameter has been System Action: Dump processing continues even if specified for an output CMS file. When processing an error occurs during dumping. according to the parameter value, an error has User Action: None. occurred. file-id CMS file identification error-code One of the following: 723 Value OLD was specified but the CMS file does not exist. 724 Value NEW was specified but the CMS file exists already. System Action: Transmission ends.

Chapter 1. NetView FTP Messages 39 DVG197I Ÿ DVG201I

DVG197I NETVIEW FTP release; DVG199I DUMP INFORMATION; SERVER serverid MAINTASK ABNORMALLY ACTION CODE = ac; TERMINATED; RETURN CODE = retcd SYSTEM ABEND CODE = sac; USER ABEND CODE = uac Explanation: A NetView FTP component entered an ABEND exit routine. This routine issued a system Explanation: The maintask of the server terminated macroinstruction to obtain a dump of selected abnormally. storage areas. This message gives information about the invocation result. release Release level of transfer program. ac Action code: serverid Server ID of the server. 01 If the transfer program runs sac System ABEND code. under MVS then the SNAP uac ABEND code set by the server itself. macro was invoked. Otherwise System Action: The server stops. All file transfers the SDUMP macro was invoked. are interrupted. 02 The dump was obtained because no data set was specified where User Action: For an explanation of the ABEND it could be stored. codes, refer to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109. If the retcd The code returned by the invoked operator canceled the program, ignore any system macroinstruction (valid only for Action dump. Code 01). System Action: The transfer program continues its ABEND exit processing. If the Action Code is 01, DVG198I NETVIEW FTP release; then a dump is obtained. SERVER serverid SUBTASK TERMINATED ABNORMALLY; User Action: For Action Code 01 and a Return SYSTEM ABEND CODE = sac; Code greater than 0, analyze the problem using one USER ABEND CODE = uac or more of the following: Ÿ MVS/ESA Application Development Reference: Explanation: The subtask of the server terminated Services for Assembler Language Programs abnormally. Ÿ MVS/XA Macro Instruction Reference Ÿ VM/ESA Group Control System Reference for release Release level of transfer program. 370 serverid Server ID of the server. Ÿ VM/XA SP Group Control System Command sac System ABEND code. and Macro Reference Ÿ VM/SP Group Control System Macro Reference. uac ABEND code set by the server itself. System Action: The subtask ends. If a file transfer was currently being processed by the subtask, the DVG200I PATCH-AREA ENTERED; file transfer ends also, and if the value of the TRACE ACTIVE Automatic Transfer Restart parameter is: Explanation: This message is issued only when a Ÿ YES, NetView FTP changes the status of the patch-area trace is performed. file-transfer request to waiting. System Action: Trace output is written. Ÿ NO, NetView FTP changes the status of the Processing continues. file-transfer request to finished. User Action: None. The reaction of the server depends on the reason for the termination. For further details, refer to the Originating Module: Module identified in the NetView FTP Installation, Operation, and symptom record. Administration book that applies to your operating system and transfer program. DVG201I modulename ENTERED; User Action: For an explanation of the ABEND TRACE ACTIVE codes, refer to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109. If the operator canceled the program, ignore any system Explanation: NetView FTP took a trace when dump. entering the module. modulename The name of the module that is being entered. System Action: Trace output is written. Processing continues. User Action: None.

40 NetView FTP Messages and Codes DVG202I Ÿ DVG223I

DVG202I modulename EXITED; DVG221I TRACE OUTPUT FROM USER-EXIT ROUTINE TRACE ACTIVE; modulename; RETURN CODE = retcd TRACE WAS TAKEN before|after CALL FOR function; Explanation: NetView FTP took a trace when TRACE AREA = USER-DEFINED STORAGE exiting the module. AREA modulename The name of the module that is being Explanation: To test a user-exit routine, a specified exited. storage area was traced after every call of a retcd Decimal return code passed by this user-exit routine function. The user-exit routine must module to the calling module. supply the beginning address and the length of the System Action: Trace output is written. storage area. Processing continues. modulename User Action: None. Load module name of user-exit routine. before|after Can be one of the following: DVG220I TRACE OUTPUT FROM USER-EXIT ROUTINE modulename; BEFORE The trace is taken before the TRACE WAS TAKEN before|after CALL FOR named function is called. function; AFTER The trace is taken after the TRACE AREA = CONTROL BLOCK SERVING named function is called. AS INTERFACE BETWEEN function NETVIEW FTP AND USER-EXIT ROUTINE NetView FTP functions: Ÿ CLOSE (user-written file handler) Explanation: To test a user-exit routine, the main Ÿ GET (user-written file handler) interface between NetView FTP and the user-exit Ÿ OPEN (user-written file handler) routine was traced before and after every call of a Ÿ POINT (user-written file handler) user-exit routine function. Ÿ PUT (user-written file handler) modulename Ÿ P (for pre-transfer exit routine) Load module name of user-exit routine. Ÿ C (for post-transfer exit routine) Ÿ POSTCONV (for post-conversation exit before|after routine). Can be one of the following: These function calls and the user-exit routines are BEFORE The trace is taken before the described in NetView FTP Customization. named function is called. AFTER The trace is taken after the System Action: Produces trace output. named function is called. User Action: None. function NetView FTP functions: DVG223I REQUEST ORIGINATOR = orig; Ÿ CLOSE (user-written file handler) REQUEST RECEIVED ON yy/mm/dd AT Ÿ GET (user-written file handler) hh:mm:ss; Ÿ OPEN (user-written file handler) SERVER CLASS = class Ÿ POINT (user-written file handler) Ÿ PUT (user-written file handler) Explanation: This message gives information about Ÿ P (for pre-transfer exit routine) the user ID of the originator of a request. Ÿ C (for post-transfer exit routine) Ÿ POSTCONV (for post-conversation exit orig Originator of this file-transfer routine). request. These function calls and the user-exit routines are yy/mm/dd Date that the file-transfer request described in NetView FTP Customization. was received: yy=year, mm=month, dd=day. System Action: Produces trace output. hh:mm:ss Time that the file-transfer request User Action: None. was received: hh=hour, mm=minute, ss=second. class Server class as found in the file-transfer request. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 41 DVG225I Ÿ DVG234I

DVG225I INFORMATION FOR LOCAL SYSTEM; DVG230I TRANSFER PARAMETERS; LU NAME = luname LOGICAL UNIT TYPE = lutype; TRANSFER MODE = mode Explanation: This message is the header of the statistics messages and information related to the Explanation: This message lists the transfer local server. parameters that are in effect for this server. luname LU name of the local server that lutype Logical unit type: processed the file-transfer request. P Responding server initiated file System Action: Processing continues. transfer (it was the primary LU). User Action: None. S Responding server accepted a remotely-initiated file transfer (it was the secondary LU). DVG226I INFORMATION FOR REMOTE SYSTEM; LU NAME = luname; mode Transfer mode: SERVER GROUP = name S Server sent a file to a remote NETVIEW FTP NAME = ftpname location. R Server received a file from a Explanation: This message is the header of the remote location. statistics messages and information related to the System Action: Processing continues. remote server. User Action: None. luname LU name of remote server. name The value of the server group, if any. DVG233I RECORD FORMAT = recfm; ftpname Name of the NFTPNAME queue BLOCK SIZE = blk; handler initialization parameter (MVS, LOGICAL RECORD LENGTH = lrecl VM) or partition initialization parameter (VSE). Explanation: This message lists the DCB System Action: Processing continues. parameters of a physical sequential or partitioned User Action: None. organized data set. For the sending server, they are derived directly from the DCB of the data set. For the receiving server, they contain the values DVG227I OPERATOR STOPPED SERVER; specified in the file-transfer request. FILE TRANSFER INTERRUPTED recfm Record format:

Explanation: The operator stopped a server. A file U Undefined transfer that was in progress was interrupted. V Variable F Fixed System Action: The transfer ends. The receiving FB Fixed-blocked server writes a checkpoint record. VB Variable-blocked The status that NetView FTP gives the request VS Variable-spanned depends on the value of the Automatic Transfer VBS Variable-blocked-spanned. Restart parameter for that request: blk Physical block size. Ÿ If the value is YES, NetView FTP gives the lrecl Logical record length (blank if the record request the status waiting; the request is format is undefined or variable). reprocessed later. System Action: Processing continues. Ÿ If the value is NO, NetView FTP gives the request the status finished; the request is not User Action: None. reprocessed later. User Action: Ask the operator if there are servers DVG234I EMPTY DATA SET TRANSFERRED started that process requests of the class of your request. If not, ask the operator to start such a Explanation: No records were transferred, but the server. No further action is required if the status of file transfer ended normally. the file-transfer request is waiting. If the status of the file-transfer request is finished, and you still System Action: Processing continues. want to transfer the file, correct the error, and add a User Action: Check that the correct data set was new file-transfer request to the request queue. specified in the file-transfer request.

42 NetView FTP Messages and Codes DVG236I Ÿ DVG241I

DVG236I NUMBER OF RECORDS TRANSMITTED = recno DVG238I USER CATALOG ID = ucatid

Explanation: This message is for information only, Explanation: This message is issued if, for a to indicate that the file transfer has ended. If the file VSAM data set, a user catalog is dynamically transfer was interrupted, the sending location usually allocated. shows a higher number than the receiving location. ucatid Data-set name of the user catalog. This discrepancy came about because some records were lost due to the error. System Action: Processing continues. recno The number of records transmitted. User Action: None. System Action: Processing continues. User Action: None. DVG239I VOLUME SERIAL NUMBER no = volser

Explanation: This message is issued if the file DVG237I DATA SET INFORMATION: transfer involved one of the following: DATA SET NAME = dsname; DD NAME = ddname; Ÿ A physical sequential data set DATA SET TYPE = dst; Ÿ A partitioned organized data set DYNAMIC ALLOCATION REQUESTED = x; Ÿ A VSAM data set. PDS MEMBER NAME = pdsmnam The first volume serial number is retrieved by Or, for NetView FTP V2.2 MVS: NetView FTP after the file is opened. The remaining DVG237I DATA SET INFORMATION: volume serial numbers, if any, are taken from the DATA SET NAME = dsname; file-transfer request. DD NAME = ddname; no Number from 1 to 9. FILE ORGANIZATION = dst; volser Volume serial number. DYNAMIC ALLOCATION REQUESTED = x; PDS MEMBER NAME = pdsmnam System Action: Processing continues. User Action: None. Explanation: This message shows some of the main data set parameters. DVG240I EXPIRATION DATE = date dsname Data-set name.

ddname Symbolic name of the DD statement Explanation: This message is issued for a name, either as used by NetView FTP dynamically-allocated physical sequential data set or (local server) or as specified in the a partitioned organized data set. file-transfer request (remote server). date Expiration date or retention period dst One of the following: specified in a request. If it is in the form Ÿ VSAM yyddd then it is the expiry date. If it is in Ÿ PS the form dddd then it is the retention Ÿ PO period. Ÿ UNLAB (other than NetView FTP System Action: Processing continues. V2.2 MVS) Ÿ LAB (other than NetView FTP V2.2 User Action: None. MVS) x Y(ES-dynamic allocation used) or N(O-job DVG241I UNIT = unit allocation used). pdsmnam Explanation: This message is issued for a Single PDS member name; only shown if dynamically allocated physical sequential or the name of a single member is specified partitioned organized data set. in the file-transfer request. unit Device type, specified in the file-transfer System Action: Processing continues. request, of the unit on which the data set User Action: None. resides. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 43 DVG242I Ÿ DVG253I

DVG242I VSAM KSDS OPTION = option DVG245I VM DISK IDENTIFICATION = diskid, diskaddress

Explanation: This message gives information Explanation: This is the identification of the VM concerning the KSDS processing options for a VSAM disk used at the VM system from which NetView FTP key-sequenced data set (KSDS). If this message is issued this message. The values are taken from the issued by the remote server, the KSDS option is file-transfer request. shown without checking to see if the data set at the diskid The user ID of the owner of the disk. remote location is really a KSDS. diskaddress option The following KSDS options are valid: Disk address, as defined in the directory Ÿ MERGE of the disk user ID. ADDBEG Ÿ System Action: Processing continues. Ÿ ADDKEY Ÿ REPKEY User Action: None. Ÿ DELKEY. System Action: Processing continues. DVG250I REQUEST AVAILABLE FOR restart type User Action: None. TRANSFER RESTART

Explanation: The server issues this message when DVG243I DATA SET IS ALLOCATED WITH DISPOSITION a file transfer is interrupted. The restart type can be disp one of the following: Or, for NetView FTP V2.2 MVS: DVG243I DATA SET IS ALLOCATED WITH FILE STATUS AUTOMATIC OPTION statopt, FILE ACCESS OPTION accopt, The request is rescheduled and will be AND END OF PROCESSING OPTION OK eopok, automatically restarted. This is only NOT OK eopno possible if a temporary error occurred and the value of the Automatic Transfer Restart parameter specified in the Explanation: NetView FTP issues this message request is YES. when it dynamically allocates a data set. MANUAL The request can be manually restarted. disp The value of the Disposition parameter This is possible if an error occurred that that the server used to allocate the data requires manual intervention or if the set. value of the Automatic Transfer Restart statopt The value of the File Status Option that parameter specified in the request is NO. the server used to allocate the data set. System Action: The transfer ends. If the accopt The value of the File Access Option that file-transfer request is available for automatic transfer the server used to allocate the data set. restart, NetView FTP gives the file-transfer request the status waiting. It is available for rescheduling. eopok The end-of-processing option after a file was transferred successfully. If the file-transfer request is available for manual transfer restart, NetView FTP gives the file-transfer eopno The end-of-processing option after a file request the status finished. was not transferred successfully. User Action: For automatic transfer restart, none. System Action: Processing continues. For manual transfer restart, check the cause for the User Action: None. interruption, correct the error, and submit a restart request for the file transfer. DVG244I SECURITY PARAMETERS; USER ID = parm1; DVG253I FILE SEQUENCE NUMBER = fsno GROUP ID = parm3 Explanation: This message is issued if the file Explanation: The message is issued when at least transfer involved a file on a tape device. one value was specified for the access security fsno File sequence number. Identifies the parameters. relative position of a file on a tape device. parm1 First access security parameter value System Action: Processing continues. (user ID). User Action: None. parm3 Third access security parameter value (group ID). The second value, parm2, is not shown because it can be a password. System Action: Processing continues. User Action: None.

44 NetView FTP Messages and Codes DVG254I Ÿ DVG313I

DVG254I NUMBER OF BYTES TRANSMITTED = bytes DVG299I MODULE DVGCCMDn NOT FOUND

Explanation: This message tells you the number of Explanation: One of the NetView FTP components bytes that were transmitted in an initial transfer. For tried to load a message definition module, but it was data-set type PO, this number includes bytes not available. containing directory information and NetView FTP n Identifier for the message module, the first control information. If the file transfer is interrupted, letter of the specified language. the sending transfer program usually indicates a higher number than the receiving transfer program. System Action: The NetView FTP component This is because data was lost due to the error terminates. causing the interruption. User Action: Create the required message module, bytes Number of data bytes (uncompressed) or specify the correct language parameter for the transmitted. failing component. For further details, refer to the NetView FTP Installation, Operation, and System Action: Processing continues. Administration book that applies to your operating User Action: None. system and transfer program.

DVG255I TRANSFER STARTED ON yy/mm/dd AT DVG311I SERVER TERMINATION REQUESTED DUE TO hh:mm:ss; EXPIRED TERMINATION TIME TRANSFER ENDED ON yy/mm/dd AT hh:mm:ss; Explanation: A server’s termination time has Explanation: This message is issued when a expired. transfer ends. It tells you when the transfer started System Action: The server waits for the completion at the sending system and when the transfer ended of all currently running file transfers. When all at the local system. transfers are completed, the server stops. No new System Action: Processing continues. file-transfer requests are processed. User Action: None. User Action: None.

DVG256I NUMBER OF BYTES TRANSMITTED SINCE DVG312I SERVER TERMINATION REQUESTED BY LAST CHECKPOINT = bytes QUEUE HANDLER; Or, for NetView FTP V2.2 MVS: TERMINATION TYPE = ttype DVG256I NUMBER OF BYTES TRANSMITTED SINCE LAST RESTART = bytes Explanation: The queue handler requests that the server terminates. Usually this is a result of an Explanation: This message is issued when a operator command to stop a server or the queue transfer is restarted. It tells you the number of bytes handler. that were transmitted since the last restart. For ttype Can be one of the following: data-set type PO, this number includes bytes containing directory information and NetView FTP I Immediate termination control information. The server can restart an D Delayed termination. interrupted file transfer from a checkpoint recorded in System Action: If delayed termination was the checkpoint file. requested the server waits for the completion of all If the file transfer is interrupted, the sending transfer currently running file transfers. When all transfers program usually indicates a higher number than the are completed, the server stops. No new file-transfer receiving transfer program. This is because data requests are processed. If immediate termination was lost due to the error causing the interruption. was requested, the server interrupts all transfers and terminates immediately. bytes Number of data bytes (uncompressed) transmitted. User Action: None. System Action: Processing continues. User Action: None. DVG313I SERVER CANNOT ATTACH SUBTASK; RETURN CODE = retcd

Explanation: The server tried to attach one of its local or remote request handlers via the ATTACH macroinstruction, but failed. retcd Return code from ATTACH macro.

Chapter 1. NetView FTP Messages 45 DVG314I Ÿ DVG321I

System Action: The server waits for the completion of all currently running file transfers. When all DVG317I SERVER TERMINATING DUE TO AN ERROR IN transfers are completed, the server terminates. THE QUEUE HANDLER User Action: Check the return code from the ATTACH macroinstruction. Refer to: Explanation: An error occurred in the queue Ÿ MVS/ESA Application Development Reference: handler. The queue handler ordered the server to Services for Assembler Language Programs terminate immediately. Ÿ MVS/XA Supervisor Services and Macros System Action: The server interrupts all transfers Ÿ VM/ESA Group Control System Reference for and terminates immediately. 370 User Action: Save the job log and the queue Ÿ VM/XA SP Group Control System Command handler log file. and Macro Reference Ÿ VM/SP Group Control System Macro Reference. Contact your IBM Support Center.

DVG314I SERVER TERMINATING DUE TO A SEVERE DVG318I SERVER TERMINATING DUE TO AN ERROR IN ERROR IN A SUBTASK MESSAGE HANDLING

Explanation: An error occurred in the local- or Explanation: An error occurred in the message remote-request handler of a server. handling of a server. Probably an I/O error occurred while the server was writing messages. System Action: The server waits for the completion of all currently running file transfers. When all System Action: The server waits for the completion transfers are completed, the server terminates. of all currently running file transfers. When all transfers are completed, the server terminates. User Action: Check the job log and the server log file for messages that help you analyze the problem. User Action: Check the job log and the server log After you have corrected the problem, restart the file for messages that help you analyze the problem. server. After you have corrected the problem, restart the server.

DVG315I SERVER TERMINATING DUE TO AN ACF/VTAM COMMUNICATION ERROR DVG319I servername CANNOT ACCEPT ANOTHER SESSION AT PRESENT, DUE TO A SHORTAGE OF VIRTUAL STORAGE Explanation: An error occurred when a server tried to communicate with ACF/VTAM. Possibly, a logical unit was deactivated or ACF/VTAM terminated. Explanation: The server with the name servername cannot allocate enough virtual storage to allow it to System Action: The server waits for the completion accept another conversation. of all currently running file transfers. When all transfers are completed, the server terminates. System Action: The server that processed the request changes the request’s not-before time to the User Action: Solve the ACF/VTAM problem. current time plus the server’s delay time. The server Check the job log and the server log file for then puts the request back into the queue and messages that help you analyze the problem. After changes the request’s status back to waiting. The you have corrected the problem, restart the server. request is reprocessed later. User Action: None. DVG316I SERVER TERMINATING DUE TO A LOGIC ERROR IN A SUBTASK DVG321I SINGLE MODE SERVER IS TERMINATING Explanation: An error occurred in the local- or remote-request handler. Explanation: A server running in single mode finished transferring a file and is now terminating, System Action: The server waits for the completion regardless of whether the file transfer ended of all currently running file transfers. When all successfully or not. transfers are completed, the server terminates. System Action: The server terminates. User Action: Save the job log and the server log file. User Action: Check the server return code for single servers. Refer to Figure 2 on page 109. Contact your IBM Support Center.

46 NetView FTP Messages and Codes DVG325I Ÿ DVG331I

DVG325I SPECIFIED NOT-AFTER TIME HAS ALREADY DVG329I ERROR IN QUEUE HANDLER; PASSED FILE TRANSFER INTERRUPTED

Explanation: NetView FTP attempted to process a Explanation: An error occurred in the queue file-transfer request where the specified not-after time handler. All running transfers on all servers are had already passed. interrupted. All servers are stopped immediately. System Action: No file transfer was performed. System Action: The transfer ends. The server The request is regarded as finished. takes a checkpoint for each of the file transfers in progress. User Action: Add a new request with a later not-before time to the request queue. User Action: Ask the operator to restart the queue handler and the servers when the problem is solved. Note: This message is accompanied by reason code 136 (RSSTIMEX). DVG330I XMIT COMMAND CARRIED OUT FOR USER userid; DVG327I FILE TRANSFER INTERRUPTED BY USER ERROR CODE = error-code

Explanation: A user of one of the user interface Explanation: A server sent the file-transfer report to routines issued a DELETE queue handler command the user specified in the file-transfer request. while the file-transfer request was active. userid User ID. System Action: The file transfer ends. The server takes a checkpoint, so, if there is a manual restart, error-code the interrupted file transfer can be resumed from the One of the following: checkpoint. If the transfer program is not NetView 0 Report file could be sent. FTP V2.2 MVS, the file-transfer request is deleted 20 Dynamic allocation of SYSOUT from the request queue. file failed. User Action: None. 22 OPEN error on SYSOUT file. 24 OPEN error on input file. 28 I/O error on input file. DVG328I ERROR IN SERVER MAINTASK; 32 I/O error on SYSOUT file. FILE TRANSFER INTERRUPTED 36 CLOSE error on SYSOUT file. 38 CLOSE error on input file. Explanation: An error occurred in a server System Action: Processing continues. maintask. All running transfers on the server are interrupted, and the server is terminated. User Action: If the return code is zero, then no action is required. If the return code is not zero, System Action: The file transfer ends. The server check the respective file. takes a checkpoint. The status that NetView FTP gives the request depends on the value of the Automatic Transfer Restart parameter for that DVG331I ERROR DURING ATTACH OF TSO COMMAND request. cmd; User Action: If the status of the file-transfer request RETURN CODE = retcd is: Explanation: An error occurred during the Ÿ Waiting, ask the operator if there is a server processing of the ATTACH macroinstruction for the started that processes the class of the request TSO commands XMIT or SEND. that was interrupted. If not, ask the operator to start one. cmd XMIT or SEND. Ÿ Finished, and you want the file transfer to be retcd Return code from ATTACH macro. reestablished, ask the operator if there is a The user specified in the request cannot be notified. server started that processes the class of the interrupted request. If not, ask the operator to System Action: Processing continues. start one. After one is started, resubmit the User Action: Analyze the problem using the return request. code description in: Ÿ Finished, and you do not want the file transfer Ÿ MVS/ESA Application Development Reference: to be reestablished, no action is required. Services for Assembler Language Programs Ÿ MVS/XA Supervisor Services and Macros. Correct the error for subsequent runs.

Chapter 1. NetView FTP Messages 47 DVG332I Ÿ DVG334I

User Action: Check the job log or the server log DVG332I ERROR FROM macname MACRO; file for messages that might help you analyze the RETURN CODE = retcd problem. This error might be the result of a previous error. If this is the only error, the file transfer was successful. Explanation: An error occurred during processing of one of the following macros: Refer to the description of the dynamic allocation interface return (DAIR) errors, which can be found in retcd The hexadecimal return code, passed to the online ISPF tutorial. For further information, refer register 15 by the macroinstruction. to: macname Ÿ MVS/ESA SPL: Application Development Guide OBTAIN, DEVTYPE, TRKCALC macro, or Ÿ MVS/XA System Macros and Facilities LOCATE-C Volume 1. Locate of VSAM Cluster failed LOCATE-D DVG334I SERVER ON THIS NODE HAS INSUFFICIENT Retrieve of Data part FTP LEVEL; parameters failed (expiration REQUIRED FTP LEVEL = ftplevel date format YYDDD) LOCATED2 Explanation: The file-transfer request for this Retrieve of Data part server contains parameters that are valid only for a parameters failed (expiration higher version or release of NetView FTP. date format YYYYDDD) ftplevel The FTP level of the remote server: LOCATEDV Retrieve of Data Volume 4 FTP Version 2.2 with one of the parameters failed following compatibility PTFs: LOCATE-I Retrieve of Index part Ÿ For communication with parameters failed FTP V2.2 and NetView FTP V1 MVS only: LOCATEIV FTP V2.2 MVS, UL29109 Retrieve of Index Volume FTP V2.2 VM, UL59949 parameters failed FTP V2.2 VSE, UL32626. System Action: Processing continues, but not all Ÿ For communication with FTP characteristics of the sending data set could be V2.2 and NetView FTP: retrieved. The receiving data set is allocated using FTP V2.2 MVS, UN03941 default values for Space and DCB parameters. FTP V2.2 VM, UN02876 User Action: Analyze the problem using the system FTP V2.2 VSE, UN03942. administration reference for your operating system. 5 NetView FTP Version 1 for MVS without the AFF DVG333I DEALLOCATION ERROR; 6 NetView FTP Version 1 for MVS DATA SET NAME = dsname; with the AFF RETURN CODE = retcd; 7 NetView FTP V2 MVS, NetView INFORMATION REASON CODE = irsncd; FTP VM, and NetView FTP VSE. ERROR REASON CODE = ersncd System Action: The transfer ends. NetView FTP changes the status of the request to finished. Explanation: An error occurred when the server User Action: After you have corrected the errors, tried to deallocate a previously allocated data set. resubmit the file-transfer request. dsname Name of the data set. retcd Return code. irsncd Information reason code. ersncd Error reason code. System Action: The transfer ends. NetView FTP changes the status of the request to finished. The server stops after all file transfers in progress, if any, have ended.

48 NetView FTP Messages and Codes DVG336I Ÿ DVG337I

08 Specifying a 4-digit DVG336I REMOTE TRANSFER PROGRAM HAS External/Internal Disk Address is INSUFFICIENT FTP LEVEL; not supported by the remote FTP LEVEL CODE = code; transfer program. ERROR CODE = error-code 09 Data encryption is not supported by the remote transfer program. Explanation: During request checking, it was 10 Remote checking of the request detected that the transfer program on the remote parameters is not supported by location could not perform all the functions the remote transfer program. requested. 11 Transferring VSAM linear data code Version of transfer program at the remote sets is not supported by the location, as identified in the server group remote transfer program. table, or as the remote server identifies itself at transfer initialization time. The 12 SMS parameters are not codes for the FTP levels are: supported by the remote transfer program. 31C FTP level 4, V2.2 with one of the following compatibility PTFs: 13 APPC parameters are not supported by the remote transfer Ÿ For communication with program. FTP V2.2 and NetView FTP V1 MVS only: 14 OS/400 parameters are not FTP V2.2 MVS, UL29109 supported by the remote transfer FTP V2.2 VM, UL59949 program. FTP V2.2 VSE, UL32626. 15 Post-Transfer Job Submission Ÿ For communication with FTP parameters are not supported by V2.2 and NetView FTP: the remote transfer program. FTP V2.2 MVS, UN03941 16 Post-Transfer Program Call FTP V2.2 VM, UN02876 parameters are not supported by FTP V2.2 VSE, UN03942. the remote transfer program. 11B FTP level 5 17 Internal address and filemode (NetView FTP V1 MVS) specification is only valid for FTP 11A FTP level 6 V2.2 for VM. (NetView FTP V1 MVS AFF) 18 DISP=REG is not valid for FTP error-code V2.2 for VM. Up to eight of the following: System Action: If this error is detected by: 01 Omitting receiving data-set name Ÿ An interface routine, NetView FTP rejects the and receiving ddname is not request. supported by the remote transfer Ÿ A server, the file transfer ends and NetView FTP program. changes the status of the request to finished. 02 Specifying space parameters for User Action: Correct the error and resubmit the the receiving data set is not request. supported by the remote transfer program. Note: A wrong value in the server group table can cause this message to be issued. If you suspect this 03 The PO data-set type is not is the case, contact your system administrator. supported by the remote transfer program. 04 The VSAM data-set type with DVG337I DIRECTORY INFORMATION WILL NOT BE NEW disposition is not supported TRANSMITTED DUE TO INSUFFICIENT FTP by the remote transfer program. LEVEL OF TRANSFER PROGRAM AT THE REMOTE SYSTEM 05 VS and VBS record formats are not supported by the remote transfer program. Explanation: A single PDS member was specified in a list. 06 Transmission of a GDG data set with relative generation number During request checking, it is detected that the specified is not supported by the remote transfer program cannot use BPAM/BSAM remote transfer program. buffers for file handling, so it uses QSAM. This results in no directory information being transferred 07 Specifying SFS directory access to the partner. parameters is not supported by the remote transfer program. System Action: NetView FTP transfers the affected member without any directory information.

Chapter 1. NetView FTP Messages 49 DVG338I Ÿ DVG353I

User Action: If the directory information is either not available or not required, no action is necessary. DVG348I SPACE PARAMETERS; If vital directory information is missing, the NUMBER OF DIRECTORY BLOCKS = nnn transmitted member might be unusable at the receiving location. Explanation: This message is issued at the end of the file transfer if space parameters were specified in DVG338I FILE-TRANSFER COMPLETION MESSAGE the file-transfer request for the receiving data set SENT TO USER userid and, if the receiving data set is a PDS. nnn Number of directory blocks. Explanation: A server sent the file-transfer System Action: Processing continues. completion message to the user specified in the User Action: None. file-transfer request. userid User ID of the originator of the request. DVG350I INFORMATION ABOUT KEY IS MISSING; System Action: Processing continues. UNABLE TO DEFINE CLUSTER User Action: None. Explanation: A server attempted to define a KSDS DVG346I SPACE PARAMETERS; cluster, but the request did not specify the key length SPACE UNITS = units; and offset. This situation only occurs if the sending PRIMARY SPACE QUANTITY = nnn; data set is not a VSAM KSDS cluster, and the SECONDARY SPACE QUANTITY = mmm request did not specify key length and key offset, or if the sending FTP V2 did not specify these parameters. Explanation: This message is issued at the end of the file transfer if space parameters were specified in System Action: The transfer ends. the file-transfer request for the receiving data set. User Action: Provide key length and key offset units One of the following: when resubmitting this request. BLK Blocks TRK Tracks DVG351I CLUSTER DEFINED CYL Cylinders REC Records. Explanation: The receiving VSAM cluster was nnn Primary space quantity of space units. defined successfully. mmm Secondary space quantity of space units. System Action: Processing continues. System Action: Processing continues. User Action: None. User Action: None. DVG352I CLUSTER DEFINED BUT MINOR PROBLEMS DVG347I SPACE PARAMETERS; OCCURRED AVERAGE LENGTH = nnn Explanation: The receiving VSAM cluster was Explanation: This message is issued at the end of defined, but AMS issued warning messages. the file transfer if space parameters were specified in System Action: Processing continues. the file-transfer request for the receiving data set, User Action: Check the log file for DVG357I and if the space units are blocks. messages that contain information about the nnn Average length. parameters used to define the cluster, and the If space units are specified as blocks, the value is messages issued by AMS. interpreted as block length. If space units are specified as records, the value is interpreted as a DVG353I CLUSTER COULD NOT BE DEFINED record length.

System Action: Processing continues. Explanation: The receiving VSAM cluster could not User Action: None. be defined. System Action: The transfer ends. User Action: Check the log file for DVG357I messages that contain information about the parameters used to define the cluster, and the messages issued by AMS. If DFP Version 3.1 or older is installed, you may receive the message IDC3226I. If this occurs, specify the space units to be cylinders or tracks. Earlier versions do not support space units to be records for a linear data set.

50 NetView FTP Messages and Codes DVG354I Ÿ DVG360I

User Action: If a problem occurs during cluster DVG354I CLUSTER DELETED definition, use the information in the message to solve the problem. Several DVG357I messages are issued, which list the control statements passed to Explanation: NetView FTP could not allocate the AMS, and thereby give the information about the way receiving VSAM cluster it just defined, so it deletes it. the cluster was defined. Probably, there was a catalog specified for cluster definition that is either not allocated to the job, or is inaccessible because of system defaults. DVG359I COMPRESSION METHOD = method; System Action: The transfer ends. TRANSMISSION RATE = rate; COMPRESSION PERCENTAGE = perc User Action: The cluster should be defined in another catalog. Explanation: Check the log file for DVG357I messages that contain information about the parameters used to method Identifies the type of compression used, if define the cluster, and the messages issued by AMS. any. Can be one of the following: NONE No compression used. SNA SNA-type compression with DVG355I CLUSTER DELETED BUT MINOR PROBLEMS number compaction used. OCCURRED ADAPT Adaptive data compression used. Explanation: NetView FTP could not allocate the rate Number of uncompressed data bytes receiving VSAM cluster it just defined, so it deletes it. transferred divided by the time between AMS issued warning messages. Probably, there was the start and the end of the file-data a catalog specified for cluster definition that is either transfer (in seconds). If the file transfer is not allocated to the job, or is inaccessible because of interrupted, the start time becomes that the system defaults. time from when the transfer is restarted. System Action: The transfer ends. perc Number of compressed data bytes divided User Action: The cluster should be defined in by the number of decompressed data another catalog. bytes, multiplied by 100. Check the log file for DVG357I messages that System Action: Processing continues. contain information about the parameters used to User Action: None. delete the cluster, and the messages issued by AMS.

DVG360I DATA SET INFORMATION; DVG356I CLUSTER COULD NOT BE DELETED DATA SET NAME = dsname; DD NAME = ddname; Explanation: The receiving VSAM cluster could not DATA SET TYPE = type; be deleted. Probably, there was a catalog specified DYNAMIC ALLOCATION REQUESTED = x for cluster definition that is either not allocated to the Or, for NetView FTP V2.2 MVS: job, or is inaccessible due to system defaults. DVG360I DATA SET INFORMATION; System Action: The transfer ends. DATA SET NAME = dsname; DD NAME = ddname; User Action: The cluster should be defined in FILE ORGANIZATION = type; another catalog. LABEL TYPE = lab-type; Check the log file for DVG357I messages that DYNAMIC ALLOCATION REQUESTED = x contain information about the parameters used to delete the cluster, and the messages issued by AMS. Explanation: Check the cluster definition and cluster deletion messages. If a cluster was defined and still exists, dsname Data-set name. delete it manually, if appropriate. ddname For the requesting server, the ddname it used to allocate the data set. For the responding server, the ddname specified DVG357I message in the file-transfer request. type Data-set type: Explanation: The message is output from AMS and forwarded to the log file. Ÿ VSAM Ÿ PS message The text of the message. Ÿ PO System Action: Processing continues. Ÿ UNLAB (other than NetView FTP V2.2 MVS) Ÿ LAB (other than NetView FTP V2.2 MVS) Ÿ USER.

Chapter 1. NetView FTP Messages 51 DVG362I Ÿ DVG366I

lab-type Label type of the tape (NetView FTP V2.2 MVS) DVG363I DATA SET INFORMATION; SL Labeled tape DATA SET NAME = name; DATA SET TYPE = type NL Unlabeled tape. Or, for NetView FTP V2.2 MVS: x Y(ES-dynamic allocation used) or N(O-job DVG363I DATA SET INFORMATION; allocation used). DATA SET NAME = name; FILE ORGANIZATION = type System Action: Processing continues. LABEL TYPE = lab-type User Action: None. Explanation: This message gives information about DVG362I DATA SET INFORMATION; a data set being sent or received. DATA SET NAME = name; name Name of the data set. DATA SET TYPE = type; type Type of the data set. Valid types are: PDS MEMBER NAME = member-name Or, for NetView FTP V2.2 MVS: Ÿ VSAM DVG362I DATA SET INFORMATION; Ÿ PS DATA SET NAME = name; Ÿ PO FILE ORGANIZATION = type; Ÿ LAB (other than NetView FTP V2.2 LABEL TYPE = lab-type; MVS) PDS MEMBER NAME = member-name Ÿ UNLAB (other than NetView FTP V2.2 MVS) Ÿ USER. Explanation: This message gives information about a data set being sent or received. lab-type Label type of the tape (NetView FTP V2.2 MVS) name Name of the data set. SL Labeled tape type Type of the data set. Valid types are: NL Unlabeled tape. Ÿ VSAM Ÿ PS System Action: Processing continues. Ÿ PO User Action: None. Ÿ LAB (other than NetView FTP V2.2 MVS) Ÿ UNLAB (other than NetView FTP DVG364I CHECKPOINTING INTERVAL = mmm unit V2.2 MVS) Ÿ USER. Explanation: This message tells you the current lab-type Label type of the tape (NetView FTP V2.2 value for the checkpoint interval. MVS) mmm Either number of RUs or time interval SL Labeled tape between checkpoints. NL Unlabeled tape. unit Unit in which checkpointing interval is member-name measured; can be one of the following: Name of the data-set member. SEC Number of seconds System Action: Processing continues. RU Number of RUs KB Number of kilobytes. User Action: None. System Action: Processing continues. User Action: None.

DVG366I CURRENTLY ONLY number MEMBERS CAN BE option

Explanation: Not enough space is available to store the complete member selection or exclusion list. The problem might be: Ÿ Temporary, because it is due to a temporary CSA shortage Ÿ Permanent, because it is due to a redefinition of the request queue or of the amount of CSA available to NetView FTP. number The maximum number of members that can be currently processed.

52 NetView FTP Messages and Codes DVG367I Ÿ DVG371I

option Can be one of the following: SELECTED DVG369I DUPLICATE MEMBER NAME member FOUND; A member selection list is specified. ERROR CODE = error-code EXCLUDED A member exclusion list is specified. Explanation: System Action: NetView FTP rejects the request. member A member that was specified more than once in a member selection or exclusion User Action: Query your request. If the status is list. deferred (D) then try again later. If the status is blocked (B) then contact your system administrator. error-code One of the following: 01 Duplicate name specified for one DVG367I number MEMBERS COMPLETELY of the following: TRANSMITTED Ÿ A single member Ÿ A member to be sent, Explanation: This message tells you how many specified in a member PDS members were completely transmitted to the selection list. receiving server (that is, end-of-member was encountered for this number of members). If the 02 Duplicate new name specified for transmission could not be completed, a subsequent a member to be received, member might already be partially transmitted. specified in a member selection list. System Action: Processing continues. 03 Duplicate name specified for a User Action: None. member specified in a member exclusion list. DVG368I INVALID MEMBER NAME member FOUND; System Action: If this error is detected by: ERROR CODE = error-code Ÿ An interface routine, NetView FTP rejects the request. Explanation: One of the PDS member names Ÿ A server, the file transfer ends and NetView FTP specified in the file-transfer request does not follow changes the status of the request to finished. the naming conventions for PDS members. User Action: Correct the error and resubmit the member Member that does not follow the naming request. conventions for PDS members. error-code One of the following: DVG370I number MEMBERS SUCCESSFULLY STOWED 01 Incorrect name specified for one of the following: Explanation: This message tells you how many PDS members were successfully stowed in the Ÿ A single member receiving PDS. Ÿ A member to be sent, specified in a member number Number of PDS members stowed. selection list. System Action: Processing continues. 02 Incorrect new name specified for User Action: None. a member to be received, specified in a member selection list. DVG371I MEMBER member1 STOWED AS member2 IN RECEIVING PDS 03 Incorrect name specified for a member specified in a member exclusion list. Explanation: A member of the sending PDS was successfully stowed in the receiving PDS. System Action: If this error is detected by: member1 The name of the member in the sending Ÿ An interface routine, NetView FTP rejects the PDS. request. member2 The name under which the member is to Ÿ A server, the file transfer ends and NetView FTP be stowed in the receiving PDS. changes the status of the request to finished. System Action: Processing continues. User Action: Correct the error and resubmit the request. User Action: None.

Chapter 1. NetView FTP Messages 53 DVG372I Ÿ DVG378I

Ÿ Both PDSs have variable record format and the DVG372I MEMBER member NOT TRANSFERRED TO THE receiving PDS has a record length smaller than RECEIVING PDS the sending PDS. Ÿ Both PDSs have undefined record format and Explanation: Because of the PDS option specified the receiving PDS has a physical block size in the file-transfer request, a member of the sending smaller than the sending PDS. PDS was not transferred to the receiving PDS. The Ÿ Reblocking and TTR translation is required. reason for this message depends on the PDS option specified: Ÿ Data-set organization of the receiving data set is different from DSORG specified in the request. Option Reason System Action: The transfer ends. I PDS member member would have been sent to the receiving PDS, and inserted User Action: None. there, with the same name or with the new name specified in the request, but DVG377I RESTART ERROR; MEMBER member NOT the corresponding member already FOUND existed. U PDS member member should have been Explanation: NetView FTP tried to restart an sent to the receiving PDS to update an interrupted transfer from a checkpoint. The existing member. However, the checkpoint record specified that the transfer should corresponding member was not found in be restarted with the member member. The specific the receiving PDS. member cannot be found in the sending PDS. System Action: Processing continues. System Action: The file transfer is restarted from User Action: None. the beginning. User Action: None. DVG373I EMPTY RECEIVING DATA SET ALLOCATED DVG378I RESTART ERROR; MEMBER member Explanation: A receiving data set, containing no INCOMPLETE members, was allocated. System Action: Processing continues. Explanation: NetView FTP tried to restart the User Action: If this is what you want, no further interrupted file transfer from a checkpoint. action is required. If not, correct the error and The server retrieved, from the checkpoint data set, resubmit the request. the number of the record with which it was to continue the file transfer. While searching through the member for that record, end of member (EOM) DVG374I SPANNED RECORDS NOT SUPPORTED was reached and the record was never found. This situation can occur if: Explanation: NetView FTP cannot transfer a PDS with spanned records. Ÿ The member to be restarted with has fewer records than have already been transferred. System Action: The transfer ends. The member to be sent was changed before User Action: None. restart. Ÿ The number of records in the temporary member DVG375I PDS IS UNMOVABLE at the receiving side (restart depository) has fewer records than already transferred. Explanation: NetView FTP cannot transfer a PDS The temporary member was changed before the that is marked as unmovable. file transfer was restarted. In this situation, System Action: The transfer ends. message DVG236I in the sending and receiving log files can indicate a different number of User Action: None. transferred records. System Action: The transfer ends. DVG376I SENDING AND RECEIVING DATA SET User Action: Change the value of the Restart from ATTRIBUTES ARE INCOMPATIBLE Checkpoint parameter to NO and resubmit the file-transfer request. Explanation: NetView FTP cannot transfer a PDS if Note: If the file-transfer request is resubmitted with one of the following is true: the restarting from checkpoint option a second time, Ÿ Record format is not the same for the sending the restart takes place from the beginning of the and receiving PDS. modified member. All previously transferred members remain unchanged in the receiving PDS. Ÿ Both PDSs have fixed record format and the receiving PDS has a record length different from the sending PDS.

54 NetView FTP Messages and Codes DVG379W Ÿ DVG379W

User Action: Check whether you can browse and DVG379W AT LEAST ONE TTR COULD NOT BE edit the member, and that the content of the member TRANSLATED FOR MEMBER member is correct. If the member is a load module, try it if it is still executable. If it is OK, ignore this message. Explanation: At least one TTR in member member does not correspond to a block of this member. DVG383I MORE THAN ONE NOTELIST TTR FOUND FOR System Action: Processing continues. MEMBER member User Action: Check whether the member received is usable. Explanation: More than one TTR that points to a note list was found in a PDS directory entry. A TTRX field in the user data part of the directory is treated as a note list TTR, if the X field is not X'00'. DVG380I i/o-operation TERMINATED ABNORMALLY; ABEND CODE = abendcd member Name of failing member. System Action: The transfer ends. Explanation: An ABEND occurred during an User Action: None. OPEN, WRITE, or STOW operation. i/o-operation Input/output operation attempted. DVG384I SELECTED MEMBER member NOT FOUND IN abendcd System or user ABEND code. It is SENDING PDS described in the message library system codes book for your operating Explanation: A PDS member was selected that system. cannot be found in the sending PDS. Possibly, you System Action: The transfer ends. specified the wrong member name or the member may have been deleted. User Action: Correct the error and resubmit the file-transfer request. System Action: The transfer ends. User Action: Make sure the member exists in the DVG381I i/o operation ERROR; PDS and the name you specify is correct. Resubmit RETURN CODE = retcd; the request. REASON CODE = rsncd DVG385I SESSION RECOVERY FAILED Explanation: An I/O error occurred during a BLDL or STOW operation. Explanation: The sending server repositions to the i/o-operation Input/output operation attempted. last recently processed member and tries to read the records until the one is found during which the retcd Return code. transfer was interrupted. However, end-of-member rsncd Reason code. occurred before this record could be found. System Action: The transfer ends. This situation can occur if the member to be User Action: Examine the return and reason codes restarted has fewer records than have already been using one of the following: transferred. The member to be sent was changed before the session recovery was complete. Ÿ MVS/DFP V3: Macro Instructions for non-VSAM Data Sets System Action: The file transfer ends. Ÿ MVS/XA Data Administration: Macro Instruction User Action: Change the value of the restart from Reference. the checkpoint parameter to NO and resubmit the Correct the error, and restart the file transfer. file-transfer request.

DVG382W NOTELIST OF MEMBER member CONTAINED DVG386I FILE TRANSFER RESTARTED WITH MEMBER FEWER POINTERS THAN INDICATED IN TTR member

Explanation: The number of pointers indicated in Explanation: The file transfer of a PDS is restarted, the TTR of a note list was greater than the number beginning with member member. of pointers actually contained in that note list. This System Action: Processing continues. message indicates an error during BPAM processing User Action: None. of PDSs, which is caused beyond the scope of NetView FTP or indicates a member in error. member PDS member name. System Action: Processing continues.

Chapter 1. NetView FTP Messages 55 DVG387I Ÿ DVG401I

DVG387I MESSAGES SUPPRESSED; MESSAGE BUFFER DVG392I THE mode SERVER IS NOT A srvmode MODE THRESHOLD REACHED SERVER

Explanation: The message buffer threshold value Explanation: The server’s running mode does not was reached. All further DVG357I, DVG371I, match the running mode required for this request. DVG372I, and DVG842I messages are suppressed. srvmode Server’s running mode. Can be one of System Action: Processing continues. the following: User Action: None. S Single C Continuous.

DVG388I EXCLUDED MEMBER member NOT FOUND IN mode Server location. Either LOCAL or SENDING PDS REMOTE. The server’s running mode is first checked using the Explanation: The PDS member member was in a information found in the server group table. If this list of members not to be transferred, but was not value matches the required running mode (or if no found in the sending PDS. Possibly, you specified information can be found), the connection is the wrong member name or the member may have established. If it is later detected that the server’s been deleted. running mode is not as expected, the transfer ends. This message indicates that there was either System Action: The transfer ends. incorrect information or no information in the server User Action: Make sure the member exists in the group table. PDS. Resubmit the request. System Action: NetView FTP rejects the request. User Action: Change either the running mode to DVG389I MEMBER member1 AND MEMBER member2 agree with the remote server, or the remote LU HAVE THE SAME TTR BUT BOTH ARE REAL name or node ID to agree with the running mode. MEMBERS Resubmit the file-transfer request, specifying a server group name (or LU name) that is associated with a server with the correct running mode. Explanation: The two PDS members mentioned in this message are real members (not aliases) and have the same TTR. This message indicates an DVG400I QUEUE HANDLER IS ALREADY ACTIVE error during BPAM processing of PDS, which is caused beyond the scope of NetView FTP or indicates a PDS in error. Explanation: An attempt was made to start the same queue handler twice but the queue handler is System Action: The servers terminate the session already active. The queue handler represents the before beginning the file transfer. entire NetView FTP system, it also keeps the User Action: Check whether you can access NetView FTP system version, release, and members in the PDS. After you have corrected the modification level. While two NetView FTPs with a problem, resubmit the transfer request. different level can coexist in one system, two NetView FTPs with the same level cannot. You started NetView FTP with the same level twice. DVG391I INVALID PDS OPTION pds-opt FOR MEMBER System Action: The queue handler stops. member User Action: Correct the error as appropriate and restart the queue handler. Explanation: An incorrect PDS option was specified for a member. System Action: If this error is detected by: DVG401I QUEUE HANDLER INITIALIZATION FAILED Ÿ An interface routine, NetView FTP rejects the request. Explanation: An error occurred during the initialization of the queue handler. Normally, this Ÿ A server, the file transfer ends and NetView FTP message is preceded by a message that describes changes the status of the request to finished. the failure. pds-opt PDS option. System Action: The queue handler stops. member PDS member name. User Action: Check the job log or the queue User Action: Correct the error and resubmit the handler log-file for messages that might help you request. analyze the problem. After you have corrected the problem, restart the queue handler.

56 NetView FTP Messages and Codes DVG402I Ÿ DVG406I

DVG402I QUEUE HANDLER READY DVG405I NETVIEW FTP release; QUEUE HANDLER MAINTASK TERMINATED Explanation: The queue handler finished its ABNORMALLY; initialization and is now ready to process queue SYSTEM ABEND CODE = sac; handler commands. USER ABEND CODE = uac System Action: Processing continues. Explanation: An error occurred in the maintask of User Action: None. the NetView FTP queue handler. release Release level of transfer program. DVG403I xxx OF yyy SERVERS HAVE TERMINATED sac System ABEND code (refer to the messages and codes book for your Explanation: If the queue handler is terminating, it operating system for details). requests the termination of all servers and waits a uac ABEND code set up by the queue certain time to allow for confirmation from each handler. server. This message indicates that the time limit was reached and the queue handler shows the System Action: The queue handler stops, and status of the confirmations. All servers are forced to normally provides a dump. terminate if: User Action: See Chapter 2, “NetView FTP Ÿ The operator stops the queue handler. ABEND, Return, and Reason Codes” on page 109. For further details, refer to the NetView FTP Ÿ An irrecoverable error occurred in the queue Installation, Operation, and Administration book that handler. applies to your operating system and transfer xxx Number of servers that have confirmed program. If you think that the problem is not caused their termination. by your installation, contact your IBM Support Center. yyy Number of servers active before termination began. System Action: The queue handler terminates. DVG406I NETVIEW FTP release; QUEUE HANDLER SUBTASK TERMINATED User Action: Any servers that have not confirmed ABNORMALLY; their termination might still be active (use the display SYSTEM ABEND CODE = sac; command to determine the names of any active USER ABEND CODE = uac servers). Normally, these soon terminate by themselves. Cancel any servers that remain in a wait state for an abnormal length of time. Explanation: An error occurred in one of the queue handler’s service subtasks. release Release level of transfer program. DVG404I NETVIEW FTP release; QUEUE HANDLER ENDED sac System ABEND code (refer to the ON yy/mm/dd AT hh:mm:ss; messages and codes book for your RETURN CODE = retcd operating system for details). uac ABEND code set up by the queue Explanation: The queue handler completed its handler. processing. The return code shows if any errors System Action: The queue handler stops and, occurred during processing of the queue handler. normally, the queue handler notifies the originator of The return code is not related to a specific queue the queue handler command, and provides a dump. handler command. User Action: See Chapter 2, “NetView FTP release Release level of transfer program. ABEND, Return, and Reason Codes” on page 109. yy/mm/dd Date that the queue handler stopped: For further details, refer to the NetView FTP yy=year, mm=month, dd=day. Installation, Operation, and Administration book that applies to your operating system and transfer hh:mm:ss Time that the queue handler stopped: program. If you think the problem is not caused by hh=hour, mm=minute, ss=second. your installation, contact your IBM Support Center. retcd Queue handler return code. System Action: The queue handler stops. User Action: None.

Chapter 1. NetView FTP Messages 57 DVG407I Ÿ DVG410I

TERM DVG407I QUEUE HANDLER TERMINATION IN NetView FTP initialization is interrupted and PROGRESS terminates. To remedy this do any of the following: Explanation: In an MVS or VM system, this Ÿ Increase the CSA size in the CSA message is issued when the operator stops the parameter in member IEASYSxx of queue handler. SYS1.PARMLIB. Other address spaces In a VSE system, this message is issued whenever might also require more CSA. the queue handler stops. The queue handler stops Ÿ Decrease the limiting factor for the when the NetView FTP partition stops or when there maximum additional CSA storage allowed is an error in the request queue. for one request (CSAELIM Queue System Action: In an MVS or VM system, Handler Initialization parameter or processing continues. The queue handler stops all maximum request-queue record length). started servers. When all termination processing has When doing this, take the following into finished, the queue handler terminates. In a VSE consideration: system, the termination of the NetView FTP partition continues. Ÿ Requests waiting to be processed that require additional CSA storage will be User Action: None. blocked. They are not executed until the storage requirements can be satisfied. DVG408A UNABLE TO ALLOCATE ADDITIONAL CSA Ÿ Server status information presented STORAGE; following a DISPLAY SERVER REPLY "CONT" OR "TERM" subcommand might be truncated.

Explanation: During queue handler startup, DVG409I TRANSFER REQUEST QUEUE DOES NOT NetView FTP checks for the availability of additional MATCH THE CURRENT LEVEL OF NETVIEW CSA storage. The maximum additional CSA storage FTP allowed for a request is not available.

System Action: NetView FTP waits for the operator Explanation: Record 0 of the file-transfer request response. queue does not contain an identifier that matches the User Action: Enter one of the following: current release of NetView FTP. It is no longer possible to use file-transfer request queues from CONT previous NetView FTP releases. NetView FTP continues, but does not accept any demand for additional CSA storage. The System Action: Queue handler initialization following requests are treated as shown: terminates. Ÿ Requests requiring the following are User Action: Define a file-transfer request queue rejected: using the job provided with the product. – PDS member list processing – VSAM cluster definition DVG410I NETVIEW FTP release; – A user-written file handler QUEUE HANDLER STARTED ON yy/mm/dd AT – VM SFS hh:mm:ss; – SMS MAINTENANCE LEVEL = mlevel – OS/400 – Data encryption – APPC security Explanation: The queue handler finished its – Program call initialization and has started. It must issue the – Job submission message DVG402I before it can process queue – Additional user-exit routine input. handler commands. Ÿ Requests that are waiting to be release Release level. processed and that require additional yy/mm/dd Date that the queue handler started: CSA storage are blocked. They are not yy=year, mm=month, dd=day. executed until the storage requirements hh:mm:ss Time that the queue handler started: can be satisfied. hh=hour, mm=minute, ss=second. Ÿ Information displayed in response to a mlevel Program maintenance-level information. DISPLAY SERVER subcommand might be truncated. System Action: Processing continues. User Action: None.

58 NetView FTP Messages and Codes DVG411I Ÿ DVG416I

DVG411I REQUEST QUEUE IDENTIFICATION = file id DVG414I REQUEST QUEUE WAS DEFINED WITH TOO MANY RECORDS Explanation: The queue handler accessed its request queue. Explanation: The NetView FTP queue handler recognized that the number of records generated for file id File identification of the request queue. the request queue is too large. A maximum of System Action: Processing continues. 100 000 is allowed. User Action: None. System Action: The queue handler stops. User Action: Define a smaller request queue. How DVG412I UNABLE TO ALLOCATE REQUIRED CSA to do this is described in the NetView FTP SPACE Installation, Operation, and Administration book that applies to your operating system and transfer program. Explanation: During queue handler initialization, NetView FTP attempted to obtain an area for the FTP MVS shared block (FSB) from CSA subpool DVG415I ERROR DURING REQUEST QUEUE 231. The allocation failed due to insufficient INITIALIZATION; contiguous CSA space. RETRIEVAL OF A REQUEST FROM THE System Action: The queue handler stops. REQUEST QUEUE FAILED; ERROR CODE = error-code User Action: Try the following: Determine whether all the specified FSB slots Ÿ Explanation: The queue handler was unable to are required. If not, reduce their number until retrieve one or more file-transfer requests from the sufficient space is available. For details about request queue. how to do this, refer to the section on the FSBSLOTS queue handler initialization error-code parameter in the NetView FTP Installation, One of the following: Operation, and Administration book that applies 01 End-of-file reached, record key to your operating system and transfer program. exceeds maximum on request Ÿ Check for CSA fragmentation. queue data set. Ÿ Shut down address spaces that use large 04 Record not found on request amounts of CSA. queue data set. Ÿ Re-IPL the system. 65 Permanent I/O error on request queue data set. System Action: The queue handler stops. DVG413I INVALID RECORD FOUND IN SERVER GROUP TABLE; User Action: Check the job log or the queue RECORD = record handler log file for messages that might help you analyze the problem. After you have corrected the problem, restart the queue handler. Explanation: An incorrect specification was found in a record of the server group table. The syntax of the record in the server group table does not follow DVG416I ERROR DURING REQUEST QUEUE the standards described in the NetView FTP INITIALIZATION; DELETION OF AN EXPIRED Installation, Operation, and Administration book that REQUEST FAILED; applies to your operating system and transfer ERROR CODE = error-code program.

record Number of the record that was processed Explanation: The queue handler failed while by the queue handler. attempting to delete an expired file-transfer request System Action: The queue handler also checks the from the request queue. remainder of the server group table and then stops. error-code User Action: Correct the server group table and One of the following: start the queue handler again. 01 End of file reached, record key exceeds maximum on request queue data set. 04 Record not found on request queue data set. 65 Permanent I/O error on request queue data set.

Chapter 1. NetView FTP Messages 59 DVG417I Ÿ DVG423I

System Action: The queue handler stops. User Action: Check the job log or the queue DVG419I REQUEST QUEUE INITIALIZED WITH A handler log file for messages that might help you MAXIMUM NUMBER OF reqnum REQUESTS analyze the problem. After you have corrected the problem, restart the queue handler. Explanation: During initialization of the request queue the queue handler determined that the request number is the highest request number available with DVG417I ERROR DURING REQUEST QUEUE the current request queue (also the maximum INITIALIZATION; number of requests that will fit in the queue). UPDATE OF A REQUEST FAILED; ERROR CODE = error-code System Action: Processing continues. User Action: None. Explanation: The queue handler failed to update a file-transfer request on the request queue. The DVG420I REQUEST QUEUE WAS DEFINED WITH AN update is necessary because the status of the INCORRECT RECORD LENGTH; file-transfer request is still active. RECORD LENGTH = lrecl error-code One of the following: Explanation: The queue handler retrieved the 01 End of file reached, record key record length of the request queue data set and exceeds maximum on request found it to be inappropriate for storing file-transfer queue data set. requests. 04 Record not found on request System Action: The queue handler stops. queue data set. User Action: Check the job used to define the 65 Permanent I/O error on request request queue and correct the record length queue data set. specified for the request queue. For more System Action: The queue handler stops. information on the request queue definition, refer to the NetView FTP Installation, Operation, and User Action: Check the job log or the queue Administration book that applies to your operating handler log file for messages that might help you system and transfer program. analyze the problem. After you have corrected the problem, restart the queue handler. DVG421I INVALID NETVIEW FTP OPERATOR SUBCOMMAND; DVG418I ERROR DURING REQUEST QUEUE REBUILD; COMMAND INPUT = subcommand DELETION OF AN EXPIRED REQUEST FAILED; ERROR CODE = error-code Explanation: The operator entered an operator command with an incorrect subcommand. Explanation: Due to an overflow of the request queue, the queue handler started rebuilding the subcommand Subcommand that is passed to the request queue. One or more of the expired NetView FTP. file-transfer requests failed to be deleted. System Action: Processing continues. The error-code command is rejected. One of the following: User Action: If appropriate, issue the operator 01 End of file reached, record key command with the correct subcommand. For more exceeds maximum on request information about valid subcommands, refer to the queue data set. NetView FTP Installation, Operation, and Administration book that applies to your operating 04 Record not found on request system and transfer program. queue data set. 65 Permanent I/O error on request queue data set. DVG423I SERVER serverid COULD NOT BE STOPPED System Action: The queue handler stops. Explanation: The operator tried to stop the server User Action: Check the job log or the queue but the server could not be stopped because of one handler log file for messages that might help you of the following: analyze the problem. After you have corrected the The specified server was not found in the server problem, restart the queue handler. Ÿ group table (MVS, VM) Ÿ The specified server was not started (VSE) Ÿ The specified server was not defined using the SRVSUF parameter (VSE).

60 NetView FTP Messages and Codes DVG424I Ÿ DVG430I

serverid One of the following: Ÿ The job name or STC name under DVG426I SERVER serverid COULD NOT BE STOPPED which the server was started (MVS) BECAUSE IT WAS NOT STARTED Ÿ The user ID of the distribution service component virtual machine (VM) Explanation: The operator issued a command to stop a started server. The queue handler accepted Ÿ The server’s suffix (VSE). the command but the server’s address space was System Action: Processing continues. The found to be not active. operator command is ignored. serverid One of the following: User Action: Use the operator command to display Ÿ The job name or STC name under the NetView FTP system status. Verify all active which the server was started (MVS) NetView FTP components. Ÿ The user ID of the distribution service component virtual machine (VM). DVG424I NETVIEW FTP ACCEPTED COMMAND TO System Action: Processing continues. START SERVER serverid User Action: None.

Explanation: The operator issued a command to start a server. The command was accepted. DVG428I DELAY TIME = hhh HOURS serverid One of the following: Ÿ The job name or STC name under Explanation: This message is issued at queue which the server was started (MVS) handler startup and indicates how long, in hours, finished requests remain on the queue before they Ÿ The server prefix plus the server can be deleted during a queue rebuild. suffix (VSE) System Action: Processing continues. Ÿ The user ID of the distribution service component virtual machine (VM). User Action: None. System Action: The queue handler internally starts the specified server by invoking a cataloged DVG429I NETVIEW FTP CANNOT START ANY SERVERS procedure. User Action: None. Explanation: The operator issued a command to start a server. The command was rejected for one of the following reasons: DVG425I SERVER serverid COULD NOT BE STARTED Ÿ A STOP command was previously entered and the queue handler is terminating. Operator Explanation: The operator issued a command to commands are no longer accepted. start a server. The command was performed but the internal start facility returned an error. Ÿ The queue handler entered its shutdown sequence due to an irrecoverable error. One of the following occurred: Operator commands are no longer accepted. Ÿ The specified server was already started System Action: Processing continues. Ÿ The specified server is still terminating User Action: Wait until the queue handler Ÿ The specified server was not defined using the termination sequence finishes, then, start the queue SRVSUF parameter (VSE). handler again. When the queue handler is ready you can start one or more servers via the operator serverid One of the following: interface. Ÿ The job name or STC name under which the server was started (MVS) DVG430I SYSTEM STATUS COULD NOT BE DISPLAYED Ÿ The user ID of the distribution service component virtual machine (VM) Explanation: The operator issued a command to Ÿ The server’s suffix (VSE). display the NetView FTP system status, but this is System Action: Processing continues. not possible. The command is rejected because a previously entered DISPLAY command has not User Action: Use the operator command to display finished processing. the NetView FTP system status. Check if an address space with the same name already exists. System Action: Processing continues. User Action: Wait until the previously issued DISPLAY command finishes.

Chapter 1. NetView FTP Messages 61 DVG431I Ÿ DVG437I

System Action: The command is not processed. DVG431I QUEUE HANDLER TRACE MASK COULD NOT User Action: Use the DISPLAY command to view BE CHANGED the names of started servers. Reenter the command with the name of a started server. Explanation: The operator issued a command to change the currently active trace mask, but the queue handler has not completed its initialization. DVG435I ERROR IN NETVIEW FTP OPERATOR SUBCOMMAND; System Action: Processing continues. Command VALUE FOR PARAMETER parmname IS is rejected. INCORRECT User Action: Wait for message DVG402I, which indicates that the initialization of the queue handler is Explanation: The operator entered a command to complete. modify a request. NetView FTP rejected it for one of the following reasons: DVG432I NETVIEW FTP ACCEPTED OPERATOR Ÿ The value is not numeric, but must be SUBCOMMAND subcommand Ÿ The value is not in the valid range Ÿ If the parameter is REQNUM, then the value is Explanation: The operator issued a command, not the number of a request on the input queue. accompanied by the subcommand shown in this message. NetView FTP accepted it. parmname Name of the incorrect parameter. System Action: Processing continues. NetView System Action: The command is not processed. FTP attempts to carry out the subcommand. User Action: Reenter the command with a correct User Action: None. value.

DVG433I NETVIEW FTP ACCEPTED OPERATOR DVG436I NETVIEW FTP OPERATOR SUBCOMMAND SUBCOMMAND TO WAS CARRIED OUT SUCCESSFULLY STOP system Explanation: The operator entered a command to Explanation: The operator issued a subcommand modify the class or priority of a request. The to stop system. modification was carried out successfully. system One of the following: System Action: Processing continues. Ÿ The queue handler (MVS, VM) User Action: None. Ÿ The NetView FTP partition (VSE). NetView FTP accepted the command. DVG437I REQUEST QUEUE REBUILD COMPLETED AT System Action: All started servers are terminated hh:mm:ss; and all file transfers that are in progress are n REQUESTS WERE DELETED interrupted. The system stops. No further file-transfer requests are accepted. Explanation: The request queue rebuild finished. If User Action: None. the queue handler deleted any file-transfer requests, then new file-transfer request(s) can be added to the request queue. DVG434I SERVER serverid CANNOT BE MODIFIED hh:mm:ss Time that the rebuild completed: hh=hour, mm=minute, ss=second. Explanation: The operator entered a server ID or n Number of file-transfer requests that were server suffix as part of a command to modify a deleted. server. The server was not modified because of one of the following: System Action: Processing continues. Ÿ The specified server has not started. User Action: If the number is zero, refer to the Ÿ The specified server was not defined using the NetView FTP Installation, Operation, and SRVSUF parameter (VSE). Administration book that applies to your operating system and transfer program. serverid One of the following: Ÿ The job name or STC name under which the server was started (MVS) Ÿ The user ID of the distribution service component virtual machine (VM) Ÿ The server’s suffix (VSE).

62 NetView FTP Messages and Codes DVG438I Ÿ DVG446I

DVG438I REQUEST QUEUE REBUILD STARTED AT DVG442I SERVER TO BE HELD OR RELEASED IS hh:mm:ss ALREADY IN THE REQUESTED STATE

Explanation: The queue handler detected an Explanation: The operator issued a command to overflow of the request queue when it attempted to hold or release a server but the server was already write a file-transfer request to it. It reacted by in the requested state. rebuilding the request queue, trying to delete all System Action: Processing continues. file-transfer requests whose status is finished and whose delay time expired. During the rebuild no User Action: None. other queue handler commands that access the request queue are allowed. DVG443I INCORRECT PRIORITY SPECIFIED hh:mm:ss Time that the rebuild started: hh=hour, mm=minute, ss=second. Explanation: The operator issued a command to User Action: Wait for message DVG437I, which change the priority of a specified request, but the indicates the end and the result of the rebuild. specified priority was in error. System Action: The queue handler rejected the DVG439I DELAY TIME SPECIFIED FOR QUEUE REBUILD command. NetView FTP processing continues. WAS INCORRECT User Action: Issue the command again with a valid priority. The priority must be an integer from 0 to 9. Explanation: The operator entered a command to rebuild the queue. Its value was rejected. The delay DVG444I INCORRECT CLASS SPECIFIED time specified was incorrect. It was specified either with more than 3 digits or with nonnumeric characters. Explanation: The operator issued a command to change the class of the specified request, but the System Action: The queue handler rejected the class parameter specified was not alphanumeric. command. The queue rebuild is not performed. System Action: Processing continues. The User Action: Issue the command again, with a request is unchanged. correctly specified delay time. User Action: Issue the command again with a valid class (0 to 9, A to Z). DVG440I SYSTEM STATUS DISPLAY

DVG445I NO SERVERS ACTIVE Explanation: The operator issued a command to display the NetView FTP system status. Explanation: The operator issued a command to System Action: The queue handler collects status display the status of all servers. Because no server information from all active servers. The queue is started, no server data lines are displayed. handler writes the NetView FTP system status display to the operator’s console. The display shows System Action: Processing continues. the status of the queue handler and each server that User Action: None. presented its status so far. The time interval to allow all servers to present their status information is 30 seconds. DVG446I SERVER serverid CANNOT BE DISPLAYED User Action: None. BECAUSE IT IS NOT STARTED

Explanation: The operator issued a command to DVG441I COMPONENT compname COULD NOT BE display the status of the server serverid. A server POSTED with that name has not started. serverid One of the following: Explanation: The queue handler issued a cross memory post to notify another NetView FTP Ÿ The job name or STC name under component. The cross memory post failed, because which the server was started (MVS) the NetView FTP component stopped. Ÿ The user ID of the distribution service compname component virtual machine (VM). STC name or job name under which the System Action: Display terminates. NetView FTP component was started. User Action: Make sure you specify the correct System Action: Processing continues. If the server and reissue the command. message is issued when the queue handler is in the process of terminating, the termination process can take longer than normal. User Action: None.

Chapter 1. NetView FTP Messages 63 DVG447I Ÿ DVG450I

DVG447I SERVER serverid IS UNABLE TO COLLECT DVG450I orig ISSUED QUEUE HANDLER COMMAND cmd DATA FOR REQUEST NUMBER reqnum AT hh:mm:ss ON yy/mm/dd; Explanation: The operator issued a command to RC = retcd; display the status of the server serverid. The server RSN = rsncd is active but did not answer the request within a predefined time limit. Explanation: This message logs each queue This can be because of an error situation in the handler command processed by the queue handler. server or because the server is terminating. orig The user ID of the originator of the queue serverid One of the following: handler command. Ÿ The job name or STC name under cmd Queue handler command performed: which the server was started (MVS) 01 OPEN, issued by a server. The user ID of the distribution service Ÿ 02 CLOSE, issued by a server. component virtual machine (VM). 05 OBTAIN, issued by a server. System Action: Display terminates. 06 NOTIFY, issued by a server. User Action: Repeat the command later. 07 DELETE FINISHED requests issued by interface routine. DVG448I disp OF total SERVERS DISPLAYED 08 GET SESSION VALUES, issued by a server after operator modify. Explanation: The operator issued a command to 0A NOTIFY actual record count. display the status of all started servers. 10 ADD a file-transfer request disp Number of servers about which data could issued by interface routine. be displayed 20 DELETE a specific file-transfer total Number of servers that are currently request issued by interface started. routine. If disp is less than total, there was not enough 30 DELETE all file-transfer requests common storage to pass information about all issued by interface routine. servers to the operator’s console. 32 Queue REBUILD. System Action: Display terminates normally. 33 Queue CLEANUP. User Action: If disp is less than total, repeat the command later. 40 MODIFY class, priority, or status. 50 QUERY a specific file-transfer request issued by interface DVG449I disp OF total SESSIONS DISPLAYED routine. 60 QUERY all file-transfer requests Explanation: The operator issued a command to issued by interface routine. display the status of a server. 61 QUERY ADMINISTRATOR disp Number of file transfers displayed. function for queue statistics. total Number of file transfers currently in 70 GETLUNAME, issued by server. progress. 80 GETOPSYS, issued by interface If disp is less than total, there was not enough routine. common storage to pass information about all file transfers to the operator’s console. 90 STATUS, issued by a server. System Action: Display terminates normally. A0 START queue handler. User Action: If disp is less than total, repeat the A1 INITIALIZE queue handler. command later. A6 TERMINATE queue handler. B0 RESTART a file transfer issued by a interface routine. C1 CHANGE master password. D0 FORCE DELETE of a specific file-transfer request issued by interface routine.

64 NetView FTP Messages and Codes DVG451I Ÿ DVG454I

reqnum Request number (if applicable, else set to zero). DVG452I REQUEST QUEUE OVERFLOW OCCURRED retcd Return code from queue handler WHILE ADDING A REQUEST TO THE REQUEST command. QUEUE rsncd Reason code from queue handler command. Explanation: The queue handler tried to add a request to the queue. The queue handler detected hh:mm:ss Time that the queue handler command that it cannot add the request to the queue because was issued: hh=hour, mm=minute, the queue is full. ss=second. System Action: The queue handler command is yy/mm/dd Date that the queue handler command rejected. The request is not placed in the queue. was issued: yy=year, mm=month, The queue handler initiates a rebuild of the request dd=day. queue. For more information about retcd and rsncd see User Action: Delete old request and resubmit the Chapter 2, “NetView FTP ABEND, Return, and request. For a description of how to avoid request Reason Codes” on page 109. queue overflows, refer to the NetView FTP System Action: Processing continues. Installation, Operation, and Administration book that applies to your operating system and transfer User Action: None. program.

DVG451I ERROR DURING QUEUE HANDLER DVG453I UNABLE TO DISPLAY ALL AVAILABLE DATA INITIALIZATION PARAMETER HANDLING; ERROR CODE = error-code Explanation: Only some of the data retrieved can be displayed following a DISPLAY server command. Explanation: An error occurred when the queue handler processed its initialization parameters. During queue handler startup, you specified the maximum additional CSA storage allowed. This error-code value is passed to the server during the OPEN One of the following: phase. When the server presents its detailed status 01 No parameters found. following a DISPLAY SERVER command, the basic 02 No value found for the plus the additional CSA storage was not enough to mandatory NFTPNAME hold all the data that was retrieved. There is an parameter. information unit for each of the active sessions on this server. 03 The number of servers to be started exceeds the value of the System Action: The server presents as much data MAXSRV parameter. as it can. 04 The specified number of TSO User Action: To avoid this situation, do one of the sessions exceeds the number of following: available sessions. Ÿ Increase the limiting factor that determines the 08 If ALL is specified for the maximum additional CSA obtained (CSAELIM NVEVENT parameter, no other Queue Handler Initialization parameter). values can be assigned to this Ÿ Decrease the maximum number of simultaneous parameter. sessions for this server (MAXSESS server 09 Duplicate events were specified initialization parameter). for the NVEVENT parameter. System Action: The queue handler stops. DVG454I UNABLE TO ALLOCATE SUFFICIENT CSA User Action: Correct the error and start the queue STORAGE handler again. FOR REQUEST NUMBER reqnum; ERROR CODE = error-code

Explanation: This message occurs during processing of a file-transfer request. The problem that caused this message to be issued may be temporary. However, if it occurs often, it indicates a possible permanent CSA space problem. reqnum Number of the file-transfer request currently being processed by a queue handler command. On a failing ADD queue handler command or STATUS display, reqnum is zero.

Chapter 1. NetView FTP Messages 65 DVG455I Ÿ DVG459I

error-code One of the following: DVG456I SERVER servername CANNOT BE STARTED; 01 Error occurred on an ADD queue MAXIMUM NUMBER OF SERVERS REACHED handler command. 10 Error occurred on an OBTAIN Explanation: You tried to start the server queue handler command. servername but the maximum number of servers are already active. 11 Error occurred on a STATUS display. System Action: The server stops. Processing continues. 12 Error occurred on a NOTIFY RESTARTABLE queue handler User Action: Stop a started server and restart the command. failed server, or restart the queue handler with a larger maximum number of servers. 13 Error occurred on a NOTIFY FINISHED queue handler command. DVG457I DISPLAY OF QUEUE HANDLER AND SERVER System Action: If the problem occurs on: INFORMATION Ÿ An ADD queue handler command, the failing Explanation: The operator issued a command to file-transfer request is rejected. display the information about the queue handler and Ÿ A STATUS DISPLAY, the displayed information all active servers. is truncated. System Action: The queue handler asks all started Ÿ An OBTAIN queue handler command, the failing servers for information. After a short time interval, file-transfer request is requeued with the status the queue handler status display is written to the DEFERRED. operator’s console, showing the status of the queue Ÿ Any NOTIFY queue handler command, the handler and each server that presented its status so file-transfer request is processed. far. The time interval to allow all servers to present their status information is 30 seconds. User Action: If the message occurs often, it is possible that the limiting factor to determine the User Action: None. For more information on the maximum additional CSA size for one request is too queue handler and server, refer to NetView FTP V2 high (CSAELIM queue handler initialization MVS Installation, Operation, and Administration. parameter or maximum request-queue record length). If this is the case, decrease this value. DVG458I DISPLAY OF QUEUE HANDLER INFORMATION

DVG455I ENTRY FOR SERVER servername ALREADY IN Explanation: The operator issued a command to SERVER TABLE display the status of the queue handler. Detailed queue statistics are shown. For more information Explanation: A server with the name servername refer to the operating section of the NetView FTP V1 started and asked the queue handler to make an MVS or NetView FTP V2 MVS Installation, entry in the queue handler’s server table, but there is Operation, and Administration manual. already an entry for a server with that name. This System Action: The data collected by the queue can happen if a server terminated abnormally and handler is displayed on the operator’s console. was not able to inform the queue handler. User Action: None. servername Procedure name of server. System Action: The server terminates and the DVG459I DISPLAY OF SERVER serverid queue handler clears the server table entry for that server. Explanation: The operator issued a command to User Action: Restart the server. Because the display the status of server serverid. queue handler cleared the entry in the server table, the server startup should proceed normally. If the serverid One of the following: problem occurs again or if it occurs for the same Ÿ The job name or STC name under server, contact your IBM Support Center. which the SNA or OSI server was started (MVS) Ÿ The user ID of the distribution service component virtual machine (VM). System Action: The queue handler collects status information for the specified server, and writes it to the operator’s console. User Action: None. For more information on the server, refer to NetView FTP V2 MVS Installation, Operation, and Administration.

66 NetView FTP Messages and Codes DVG460I Ÿ DVG464I

System Action: If this error is detected by: DVG460I ERROR DURING SPACE ALLOCATION; Ÿ An interface routine, NetView FTP rejects the ERROR CODE = error-code command Or, for NetView FTP V2.2 MVS: DVG460I ERROR DURING SPACE ALLOCATION Ÿ A server, the file transfer ends and NetView FTP changes the status of the request to finished.

Explanation: An error occurred when NetView FTP User Action: Try again later. If the problem tried to allocate space. The error is permanent and persists contact your system administrator. For error is due to the defined maximum record size of the code 3, either submit several requests each with request queue or limited CSA space (MVS only) fewer members, or try again later. available to NetView FTP. The defined limitations were set by the system administrator. DVG461I INCORRECT REQUEST NUMBER SPECIFIED NetView FTP other than NetView FTP V2.2 MVS: error-code Explanation: The operator issued a command to Insufficient space is available to store: modify a request. The specified request number was 01 User-written file handler incorrect; there is no request with such a number. parameters. Either: 02 VSAM cluster definition Ÿ The specified request number is out of range parameters. Ÿ The specified request number is unused. 03 Member selection or exclusion System Action: Processing continues. list. User Action: Display the queue handler to see the 04 Receiving SFS directory access maximum required number allowed. Reissue the parameters. command with the correct number. If necessary use 05 Sending SFS directory access the user interfaces to query and change requests. parameters. 06 Receiving SFS parameters or DVG462I REQUEST CANNOT BE CHANGED BECAUSE IT sending SFS and VSAM Cluster IS NOT WAITING Definition parameters. 07 SMS (Storage Management Explanation: The operator issued a command to Subsystem) parameters. change the status, class or priority of a request. The 08 APPC Security parameters. request is not waiting, so the command is rejected. 09 OS/400 parameters. System Action: Processing continues. The parameter values are unchanged. 10 Extended user-exit information parameters. User Action: None. 11 Post-transfer JOB parameters. DVG463I INVALID NEW SERVER SESSION 12 Post-transfer program PARAMETERS SPECIFIED parameters. 13 Data Encryption parameters. Explanation: The operator issued a command to 14 OSI parameters. change the session parameters of a server, which For NetView FTP V2.2 MVS, insufficient space is was rejected. Either the number of local sessions available to store one of the following: (AVLLRH), the number of remote sessions (AVLRRH), or the total number of sessions Ÿ User-written file handler parameters (AVLSESS) is larger than the maximum number of Ÿ VSAM cluster definition parameters available sessions. Ÿ Member selection or exclusion list Ÿ Sending SFS parameters System Action: Processing continues. The server Ÿ Receiving SFS parameters is unchanged. Ÿ SMS parameters User Action: Reissue the command with correct Ÿ APPC conversation security parameters values. Ÿ Sending OS/400 parameters Ÿ Receiving OS/400 parameters Ÿ Sending OS/2* parameters DVG464I ERROR DURING REQUEST QUEUE HANDLING; Ÿ Receiving OS/2 parameters UPDATE OF A REQUEST FAILED; Ÿ Sending file ID parameter ERROR CODE = error-code Ÿ Receiving file ID parameter Ÿ User-exit information parameters. Explanation: The queue handler failed to update a file-transfer request on the request queue. The update is necessary because the class or priority should be changed.

Chapter 1. NetView FTP Messages 67 DVG471I Ÿ DVG500I

error-code One of the following: DVG500I QUEUE HANDLER COMMAND cmd ISSUED BY 01 End of file reached, record key SERVER FAILED; exceeds maximum on request RETURN CODE = retcd; queue data set. REASON CODE = rsncd 04 Record not found in request queue data set. Explanation: An error occurred when a server issued a queue handler command. 65 Permanent I/O error in request queue data set. cmd The command was one of the following: System Action: The queue handler stops. The 01 OPEN, issued by a server to request is not changed. come under the control of the queue handler. User Action: Check the job log or the queue handler log file for messages that help you analyze 02 CLOSE, issued by a server to the problem. After you have corrected the problem, leave the control of the queue restart the queue handler. handler. 05 OBTAIN, issued by a server to get a new file-transfer request for DVG471I SERVER SESSION VALUES ACCEPTED FOR processing. servername 06 NOTIFY, issued by a server to change the status of a Explanation: The operator-issued command to file-transfer request on the change the session parameters for the server request queue. servername was accepted. 08 GETSESSPRM, issued by a System Action: Processing continues. The server to get the new session specified server runs with the new parameters. values. User Action: None. 70 GETLUNAME, issued by a server to get more LU names for a specified server group name. DVG481I SMF WRITING FAILED AT time; SMF RETURN CODE = smfretcd 90 STATUS, issued by a server, to report its status, in response to a DISPLAY command. Explanation: The writing of an SMF record failed. For further information refer to MVS/ESA System retcd Queue handler command return code. Management Facilities (SMF) or MVS/XA SMF. rsncd Queue handler command reason code. hh:mm:ss Time that SMF writing failed at: hh=hour, Refer to Chapter 2, “NetView FTP ABEND, Return, mm=minute, ss=second. and Reason Codes” on page 109 for more smfretcd SMF return code. Indicates that the information about retcd and rsncd. record was not written because: System Action: The server interrupts all active file 16 SMF is not active. transfers and terminates immediately. 20 The user-written IEFU83 or User Action: Use the return and reason code to IEFU84 exit routine suppressed analyze and fix the problem. If the problem persists, the record. contact your IBM Support Center. 24 The data was lost. If the error occurred during the NOTIFY command, NetView FTP cannot update the status of formerly 36 The record type specified is not active requests. To correct this, do the following: currently being recorded. 1. Stop the queue handler (MVS, VM) or the 40 A buffer shortage caused the NetView FTP partition (VSE). NetView FTP data to be lost. changes the status of all active requests to 44 SVC 83 could not establish waiting. recovery. 2. Restart the queue handler (MVS, VM) or the System Action: Processing continues. The SMF NetView FTP partition (VSE). All waiting record is not written. requests are available for scheduling by servers. User Action: None. If the error occurred during the NOTIFY command and before the receiving server created the receiving data set, it can happen that the file transfer cannot be automatically restarted. This is because, when automatically restarting a transfer, NetView FTP allocates the receiving data set with the disposition MOD, and this allocation can be successful only if the data set already exists. In this situation, you need to submit a new request to transfer the file.

68 NetView FTP Messages and Codes DVG510I Ÿ DVG530I

DVG510I NO LU NAME FOUND IN SERVER GROUP DVG513I ENCRYPTION LABEL NOT CORRECT TABLE FOR servergroup Explanation: The Programmed Cryptographic Explanation: No LU name is found in the server Facility (PCF) does not recognize the encryption group table for the server group specified in the label specified. file-transfer request. This situation happens if the System Action: The transfer ends. queue handler was stopped (after the file-transfer request was added to the request queue) and then User Action: Correct the encryption label and started again with a different, a changed, or no resubmit the file-transfer request. Make sure the server group table. encryption label is stored in the PCF key data set (CKDS). System Action: The transfer ends and NetView FTP changes the status of the file-transfer request to finished. DVG514I DATA ENCRYPTION = encrypt User Action: Restart the queue handler with a different or a changed server group table that Explanation: This message tells you whether or not contains the entry for the server group specified in the Data Encryption parameter was specified. the request, or change the server group name in the encrypt One of the following: file-transfer request and resubmit it. YES Data encryption was specified. NO Data encryption was not specified. DVG511I PCF IS NOT ACTIVE AT BOTH LOCATIONS System Action: Processing continues. Explanation: You specified that data is to be User Action: None. encrypted during file transfer. NetView FTP V2 MVS allows encryption only if the Programmed Cryptographic Facility (PCF) is active at the sending DVG515I ENCRYPTION LABEL CONTENTS location and at the receiving location. INCONSISTENT System Action: The transfer ends. User Action: If you want to encrypt data during file Explanation: The cross key at the sending location transfer, make sure PCF is active at both locations. is different from the cross key at the receiving location that has the same label. Because of this, the enciphered data cannot be deciphered. For DVG512I PCF RETURNED AN ERROR BY COMMAND more details, see OS/VS1 OS/VS2 MVS cmd; Programmed Cryptographic Facility: Installation RETURN CODE = retcd Reference. System Action: The transfer ends. Explanation: An error occurred with the User Action: Check the encryption label at both Programmed Cryptographic Facility (PCF) during locations. server initialization or during file transfer. cmd One of the following: DVG530I PARAMETER WITH KEYWORD keyword IS NOT GEN_OPKY Generate an operational PERMITTED FOR AN EXISTING DATA SET key.

ENCR_ICV Encipher ICV. Explanation: You specified at least one parameter DECR_ICV Decipher ICV. incorrectly for a file that already exists. Either, the parameter whose keyword is shown in the message, ENCR_DAT Encipher data. or the data set status specified in the request, is in DECR_DAT Decipher data. error. retcd Return code issued by PCF. keyword The batch job interface keyword. System Action: The transfer ends. System Action: If this error is detected by: User Action: None. Ÿ An interface routine, NetView FTP rejects the request Ÿ A server, the file transfer ends and NetView FTP changes the status of the request to finished. User Action: Correct the error and resubmit the request.

Chapter 1. NetView FTP Messages 69 DVG531I Ÿ DVG541I

DVG531I DO NOT SPECIFY THE PARAMETER WITH DVG538I RESULTS OF ADMINISTRATOR QUERY OF KEYWORD keyword IF NOMAX IS SPECIFIED ACTIVE REQUESTS: FOR INITIAL NUMBER OF RECORDS Explanation: This message is used as the header Explanation: You specified NOMAX for the initial line for messages issued in response to an number of records for an OS/400 file, and also a administrator query for active requests. value for the parameter whose keyword is shown in System Action: Processing continues. the message. However, these values are incompatible. User Action: None. keyword The batch job interface keyword. System Action: If this error is detected by: DVG539I RESULTS OF ADMINISTRATOR QUERY OF FINISHED REQUESTS: Ÿ An interface routine, NetView FTP rejects the request Explanation: This message is used as the header Ÿ A server, the file transfer ends and NetView FTP line for messages issued in response to an changes the status of the request to finished. administrator query for finished requests. User Action: Either, do not specify NOMAX for the System Action: Processing continues. initial number of records, or remove the value for the parameter shown in the message, and then resubmit User Action: None. your request. DVG540I REQUEST QUEUE STATISTICS: DVG536I NOT ENOUGH STORAGE AVAILABLE QUEUE HANDLER = qhname; TO PROCESS ADDITIONAL PARAMETERS; START DATE = date; ERROR CODE = error-code START TIME = time; QUEUE SIZE = qsize

Explanation: The maximum additional CSA storage allowed for a request is too small to contain all your Explanation: This message is issued in response parameters. This is a restriction of the current to an administrator query for information about the definition of your NetView FTP environment. request queue. The displayed information consists of: error-code One of the following: qhname One of the following: 01 User-written file handler Ÿ The STC name under which the parameters. queue handler was started (MVS) Ÿ User ID of the queue handler’s virtual 02 VSAM cluster definition machine (VM). parameters. date Date that the queue handler was started. 03 PDS member list. time Time that the queue handler was started. 04 OSI file-transfer request. qsize Size of the request queue. This value is System Action: NetView FTP rejects the request. the sum of the number of waiting, active, User Action: If the error code is 1 or 2, the queue and finished requests, and the unused handler presently cannot accept or pass to servers, request slots. requests using these kinds of parameters. System Action: Processing continues. If the error code is 3, resubmit your request with User Action: None. fewer selected or excluded PDS members.

DVG541I WAITING = waiting; DVG537I RESULTS OF ADMINISTRATOR QUERY OF ACTIVE = active; WAITING REQUESTS: FINISHED = finished; RESTARTED = restarted; Explanation: This message is used as the header UNUSED = unused line for messages issued in response to an administrator query for waiting requests. Explanation: This message is issued in response System Action: Processing continues. to the query administrator-command for information about requests in the queue. The displayed User Action: None. information consists of: waiting Total number of waiting requests in the queue. active Total number of active requests in the queue.

70 NetView FTP Messages and Codes DVG542I Ÿ DVG544I

finished Total number of finished requests in the status Status of the request. Can be any of the queue. following: restarted Total number of waiting requests in the W Waiting queue that were previously active and are H Waiting and held now to be restarted. B Waiting and blocked D Waiting and deferred. unused Number of free request slots. priority Request priority. System Action: Processing continues. restart Indicates whether or not the specified User Action: None. request is waiting to be restarted. Can be blank (indicating that the request is not DVG542I CLASS = class; waiting to be restarted) or one of the HELD = state; following: WAITING = waiting; A Request is waiting for an ACTIVE = active; automatic transfer restart. SERVED = served M Request is waiting for a manual transfer restart. Explanation: This message contains statistical information for one request class. It is issued in yy/mm/dd,hh:mm:ss response to the query administrator-command for Date and time that the request was information about requests, only for server classes entered by the user and added to the that are held by the operator, or if it contains waiting queue. or active requests. The displayed information svname Name of the server processing the consists of: request. (Not applicable to VSE.) class Letter or number of the server class. loclu Local LU name. state Whether or not the server class was put remlu Remote LU name or server group name. on hold by the operator. Can be one of orig User ID of the originator of the file-transfer the following: request. Y Class is held. System Action: Processing continues. N Class is not held. User Action: None. waiting Number of waiting requests in the queue with that class. DVG544I REQUEST NUMBER = reqnum; active Number of active requests in the queue CLASS = class; with that class. SUBMITTED = yy/mm/dd,hh:mm:ss; served Whether or not a server is started for the STARTED = yy/mm/dd,hh:mm:ss; class. Can be one of the following: SERVER NAME = svname; Y A server is started. LOCAL LU NAME = loclu; REMOTE LU NAME = remlu; N No server is started. ORIGINATOR = orig U Unknown. System Action: Processing continues. Explanation: This message contains information for one active request. It is issued in response to an User Action: None. administrator query for active requests. reqnum Request number of the file-transfer DVG543I REQUEST NUMBER = reqnum; request. CLASS = class; class Server class. STATUS = status; PRIORITY = priority; yy/mm/dd,hh:mm:ss RESTART = restart; Date and time that either the request was SUBMITTED = yy/mm/dd,hh:mm:ss; entered by the user and stored on the SERVER NAME = svname; queue, or the file transfer for this request LOCAL LU NAME = loclu; started. REMOTE LU NAME = remlu; svname Name of the server processing the ORIGINATOR = orig request. (Not supported by VSE.) loclu Local LU name. Explanation: This message contains information for one waiting request. It is issued as a result of the remlu Remote LU name. query administrator-command for waiting requests. orig User ID of the originator of the file-transfer reqnum Request number of the file-transfer request. request. System Action: Processing continues. class Server class. User Action: None.

Chapter 1. NetView FTP Messages 71 DVG545I Ÿ DVG550I

User Action: For further information, see one or DVG545I REQUEST NUMBER = reqnum; more of the following: CLASS = class; Ÿ MVS/DFP V3.3: Managing Catalogs SUBMITTED = yy/mm/dd,hh:mm:ss; Ÿ MVS/XA Catalog Administration Guide. STARTED = yy/mm/dd,hh:mm:ss; FINISHED = yy/mm/dd,hh:mm:ss; RETURN CODE = retcd; DVG548I function FAILED FOR DATA SET dsname; REASON CODE = rsncd; ERROR CODE = error-code RECORDS = records; ORIGINATOR = orig Explanation: An error occurred for the specified data set during OBTAIN or LOCATE. Explanation: This message contains information for function OBTAIN or LOCATE. one finished request. It is issued in response to an administrator query for finished requests. dsname Sending data set from which data-set information should be retrieved. reqnum Request number of the file-transfer request. error-code One of the following: class Server class. 01 Data-set not cataloged. yy/mm/dd,hh:mm:ss Date and time that either the request was 02 Required volume not mounted. entered by the user and stored on the 03 Data set not found on volume. queue, or the file transfer for this request started, or the file transfer for this request 04 Permanent I/O error. was finished. 05 Data-set type retrieved is not retcd Return code from the file transfer. supported by NetView FTP. rsncd Reason code from the file transfer. 06 Data set is migrated to HSM. records Number of transferred records. System Action: NetView FTP rejects the request. orig User ID of the originator of the file-transfer User Action: The response depends on the error request. code: System Action: Processing continues. 01 If the data-set name specified is correct, specify a volume serial number. User Action: None. 02 Mount the volume. 03 Specify the correct data-set name or volume DVG546I NAME OF SENDING DATA SET = dsname serial number. 04 Contact your system administrator. Explanation: This message contains the name of the sending data set specified in a request. This 05 Contact your system administrator. information was requested additionally for an 06 Contact your system administrator. administrator query for waiting, active, or finished requests. DVG550I NETVIEW FTP release; System Action: Processing continues. BATCH JOB INTERFACE STARTED ON User Action: None. yy/mm/dd AT hh:mm:ss; MAINTENANCE LEVEL = mlevel

DVG547I ERROR OCCURRED DURING function FOR DATA SET dsname; Explanation: The batch job interface routine ERROR CODE = error-code started. release Release level of transfer program. Explanation: An error occurred during an OBTAIN yy/mm/dd Date that the batch job interface routine or LOCATE macroinstruction. started: yy=year, mm=month, dd=day. function OBTAIN or LOCATE. hh:mm:ss Time that the batch job interface routine dsname Sending data set from which data-set started: hh=hour, mm=minute, ss=second. information should be retrieved. mlevel Program maintenance-level information. error-code System Action: Processing continues. Message code from OBTAIN or LOCATE. User Action: None. System Action: NetView FTP rejects the request.

72 NetView FTP Messages and Codes DVG551I Ÿ DVG554I

Ÿ QUERY DVG551I REQNUM = reqnum; Ÿ QRYALL ST = status; Ÿ MODIFY. PRTY = priority; orig User ID of the originator of the file-transfer RC = retcd; request. RSN = rsncd; CL = class; retcd The return code from the queue handler ADDED = yy/mm/dd,hh:mm:; command. Refer to Chapter 2, “NetView ORIG = orig; FTP ABEND, Return, and Reason Codes” REC = trrec; on page 109 for more information. REQNAME = reqname rsncd The reason code from the queue handler command. Refer to Chapter 2, “NetView Explanation: This message is issued in response FTP ABEND, Return, and Reason Codes” to a user query command. on page 109 for more information. reqnum The request number of the file-transfer hh:mm:ss Time: hh=hour, mm=minute, ss=second. request. reqnum The request number of the file-transfer status The status of the request: request, if applicable; otherwise set to zero. W Waiting System Action: Processing continues. H Waiting and held User Action: None. B Waiting and blocked D Waiting and deferred DVG553I PARAMETER WITH KEYWORD keyword IS NO priority The priority of the request. LONGER SUPPORTED retcd The return code of the last attempt to process the file-transfer request. Explanation: Some FTP V2.2 parameters are rsncd The reason code of the last attempt to ignored by NetView FTP. They represent obsolete process the file-transfer request. or replaced FTP V2.2 functions. class The server class. keyword The batch job interface keyword. It can be one of the following: xLU, TIME, yy/mm/dd Date that the request was submitted: xCMSUSER, xCMSFID, RDSN, or yy=year, mm=month, dd=day. RUSIZE. hh:mm: Time that the request was submitted: System Action: The parameter is ignored. hh=hour, mm=minute. Processing continues. orig The originator of the file-transfer request. User Action: Do not use these parameters in trrec The number of records that were subsequent file-transfer requests. transferred on the last attempt to process the file-transfer request. DVG554I NETVIEW FTP release; BATCH JOB INTERFACE reqname The name of the request. ENDED ON yy/mm/dd AT hh:mm:ss; System Action: Processing continues. RETURN CODE = retcd; User Action: None. REASON CODE = rsncd

Explanation: This is the completion message of the DVG552I QUEUE HANDLER COMMAND commandname batch job interface routine. CARRIED OUT FOR USER orig; RETURN CODE = retcd; release Release level of transfer program. REASON CODE = rsncd; yy/mm/dd Date that the batch job interface routine TIME = hh:mm:ss; terminated: yy=year, mm=month, dd=day. REQUEST NUMBER = reqnum hh:mm:ss Time that the batch job interface routine terminated: hh=hour, mm=minute, Explanation: This message indicates the ss=second. completion of a queue handler command that was retcd Return code for queue handler command initiated by the batch job interface routine. or file transfer. commandname rsncd Reason code for queue handler command Queue handler command as specified in or file transfer. the FUNCTION parameter of the batch job interface: Ÿ ADD Ÿ DELETE Ÿ DELALL Ÿ DELFIN

Chapter 1. NetView FTP Messages 73 DVG555I Ÿ DVG557I

Whether the return and reason codes are for a VSE SMS parameters queue handler command or for the file transfer SFS parameters depends on the value of the WAIT parameter and on OS/400 file parameters the outcome of the file transfer: OSI file-transfer parameters Post-transfer jobs and post-transfer Ÿ If WAIT=YES; the batch job interface routine program parameters adds the file-transfer request to the request VM link parameters queue and then periodically issues a QUERY Encryption parameters queue handler command to check the status of PDS processing parameters the file-transfer request. If a queue handler error OS/2 file parameters occurred before the file transfer ended, the codes are the return and reason code of the OS/400 Anything other than OS/400 file QUERY queue handler command. Otherwise parameters the codes are the return and reason code of the OS/2 SMS parameters file transfer. SFS parameters Ÿ If WAIT=NO; the codes are the return and OS/400 file parameters reason code of the ADD queue handler OSI file-transfer parameters command. Post-transfer jobs and post-transfer program parameters System Action: The batch job interface routine VM link parameters terminated. Encryption parameters User Action: None. PDS processing parameters User-written file handler parameters DVG555I PARAMETER WITH KEYWORD keyword IS NOT System Action: If this error is detected by: VALID FOR THE OPERATING SYSTEM opsys Ÿ An interface routine, NetView FTP rejects the request Explanation: The specified parameter is not valid Ÿ A server, the file transfer ends and NetView FTP for the noted operating system. changes the status of the request to finished. keyword Batch job interface keyword. User Action: Correct the error and resubmit the System Action: If this error is detected by: request. Ÿ An interface routine, NetView FTP rejects the request DVG557I VALUE SPECIFIED FOR THE PARAMETER Ÿ A server, the file transfer ends and NetView FTP WITH KEYWORD keyword IS INVALID FOR THE changes the status of the request to finished. OPERATING SYSTEM opsys User Action: Correct the error and resubmit the request. Explanation: The value is incorrect for the noted operating system. keyword The batch job interface keyword. DVG556I PARAMETER ERROR; SPECIFIED PARAMETERS OR THEIR VALUES opsys The operating system. It can be one of ARE INCOMPATIBLE; THEY REQUIRE the following: DIFFERENT OPERATING SYSTEMS Ÿ MVS Ÿ VM Explanation: You specified parameters or values Ÿ VSE that are only valid for certain operating systems. Ÿ OS/400 You also specified other parameters or values that Ÿ OS/2 are valid only for other operating systems. System Action: If this error is detected by: The following file parameter specifications are not Ÿ An interface routine, NetView FTP rejects the valid for a location: request. Operating Parameter Group Ÿ A server, the file transfer ends and NetView FTP System changes the status of the request to finished. MVS SFS parameters User Action: Correct the error and resubmit the OS/400 file parameters request. VM link parameters OS/2 file parameters VM SMS parameters OS/400 file parameters OSI file-transfer parameters Post-transfer job and post-transfer program parameters Encryption parameters PDS processing parameters OS/2 file parameters

74 NetView FTP Messages and Codes DVG558I Ÿ DVG560I

hh:mm Time that the request was started: DVG558I QUEUE HANDLER COMMAND commandname hh=hour, mm=minute. CARRIED OUT FOR USER orig; orig The originator of the file-transfer request. RETURN CODE = retcd; REASON CODE = rsncd; trrec The number of records that were TIME = hh:mm:ss transferred at the last attempt to process the file-transfer request.

Explanation: This message indicates the reqname The name of the request. completion of a queue handler command that was System Action: Processing continues. initiated by the batch job interface routine. User Action: None. commandname Queue handler command as specified in the FUNCTION parameter of the batch DVG560I REQNUM = reqnum; job interface: ST = status; PRTY = priority; Ÿ QRYALL RC = retcd; Ÿ DELALL RSN = rsncd; Ÿ DELFIN CL = class; Ÿ QRYADM FINIS = yy/mm/dd,hh:mm; Ÿ FORCE ORIG = orig; Ÿ RESTART REC = records; Ÿ MODIFY REQNAME = reqname Ÿ CHANGEPW Ÿ REBUILD. Explanation: This message is issued in response orig The originator of the file-transfer request. to a user query. retcd The return code of the queue handler reqnum The request number of the file-transfer command. request. rsncd The reason code of the queue handler status The status of the request: command. F Finished. hh:mm:ss Time: hh=hour, mm=minute, ss=second. priority The priority of the request. System Action: Processing continues. retcd The return code of the last attempt to User Action: None. process the file-transfer request. rsncd The reason code of the last attempt to DVG559I REQNUM = reqnum; process the file-transfer request. ST = status; class The server class. PRTY = priority; RC = retcd; yy/mm/dd Date that the file transfer ended: yy=year, RSN = rsncd; mm=month, dd=day. CL = class; hh:mm Time that the file transfer ended: START = yy/mm/dd,hh:mm; hh=hour, mm=minute. ORIG = orig; REC = trrec; orig The originator of the file-transfer request. REQNAME = reqname records The number of records that were transferred on the last attempt to process Explanation: This message is issued in response the file-transfer request. to a user query. reqname The name of the request. reqnum The request number of the file-transfer System Action: Processing continues. request. User Action: None. status The status of the request: A Active (file transfer in progress). priority The priority of the request. retcd The return code of the last attempt to process the file-transfer request. rsncd The reason code of the last attempt to process the file-transfer request. class The server class. yy/mm/dd Date that the file transfer started: yy=year, mm=month, dd=day.

Chapter 1. NetView FTP Messages 75 DVG561I Ÿ DVG580I

DVG561I MEMBER OR GDG NOTATION NOT VALID FOR DVG563I PARAMETER WITH KEYWORD keyword NOT THE OPERATING SYSTEM opsys; SPECIFIED; PARAMETER TYPE = type NETVIEW FTP ASSUMES value

Explanation: A PDS member name or a GDG Explanation: The user has not specified a value for number is defined as part of the data-set name or the parameter indicated by the batch job interface with the keyword xPDSMEM. They are not valid for keyword. NetView FTP uses the value shown. the noted operating system. The assumption is derived by checking other request opsys Operating system which does not support specifications. PDS or GDG processing. System Action: This message is for information type One of the following: only. S Parameter applies to sending User Action: None. data set.

R Parameter applies to receiving DVG580I REQUEST NUMBER = reqnum; data set. CLASS = class; System Action: If this error is detected by: STATUS = status; PRIORITY = priority; Ÿ An interface routine, NetView FTP rejects the RESTART = restart; request. SUBMITTED = yy/mm/dd,hh:mm:ss; Ÿ A server, the file transfer ends and NetView FTP OSI SERVER NAME = svname; changes the status of the request to finished. APPLICATION ENTITY TITLE = aet; User Action: Correct the error and resubmit the ORIGINATOR = orig request. Explanation: This message contains information for one waiting OSI request. It is issued as a result of DVG562I MEMBER OR GDG NOTATION NOT VALID FOR the query administrator command for waiting THE DATA SET TYPE ftype; requests. PARAMETER TYPE = type Or, for NetView FTP V2.2 MVS: reqnum Request number of the file-transfer DVG562I MEMBER OR GDG NOTATION NOT VALID FOR request. THE FILE ORGANIZATION ftype, LABEL TYPE class Server class. lab-type; status Status of the request. Can be one of the PARAMETER TYPE = type following: W Waiting Explanation: A PDS member name or GDG H Waiting and held. number is defined as part of the data set or with the keyword xPDSMEM. They are not valid for the priority Request priority. noted file type or organization. restart Indicates whether or not the specified ftype The specified data-set type does not request is waiting to be restarted. Can be support PDS or GDG processing. blank (indicating that the request is not waiting to be restarted) or: type One of the following: A Request is waiting for an S Parameter applies to sending automatic transfer restart. data set. yy/mm/dd,hh:mm:ss R Parameter applies to receiving Date and time that the request was data set. entered by the user and added to the System Action: If this error is detected by: queue. Ÿ An interface routine, NetView FTP rejects the svname The job name or STC name under which request the OSI server was started. Ÿ A server, the file transfer ends and NetView FTP aet Application entity title. changes the status of the request to finished. orig User ID of the originator of the file-transfer User Action: Correct the error and resubmit the request. request. System Action: Processing continues. User Action: None.

76 NetView FTP Messages and Codes DVG581I Ÿ DVG584I

DVG581I REQUEST NUMBER = reqnum; DVG583I FILE NAME = local/osiname CLASS = class; SUBMITTED = yy/mm/dd,hh:mm:ss; Explanation: This message contains the name of STARTED = yy/mm/dd,hh:mm:ss; the sending file specified in an OSI request. It is OSI SERVER NAME = svname; either the local file name for transfer mode TO, or APPLICATION ENTITY TITLE = aet; the OSI file name for transfer mode FROM. This ORIGINATOR = orig information was requested additionally for an administrator query for waiting, active, or finished Explanation: This message contains information for requests. one active OSI request. It is issued in response to System Action: Processing continues. an administrator query for active requests. User Action: None. reqnum Request number of the file-transfer request. class Server class. DVG584I REQNUM = reqnum; ST = status; yy/mm/dd,hh:mm:ss PRTY = priority; Date and time that either the request was RC = retcd; entered by the user and stored on the RSN = rsncd; queue, or the file transfer for this request CL = class; was started. ADDED = yy/mm/dd,hh:mm; svname The job name or STC name under which ORIG = orig; the OSI server was started. REQNAME = reqname aet Application entity title. Explanation: This message is issued in response orig User ID of the originator of the file-transfer to a user query command for an OSI request. request. reqnum The request number of the file-transfer System Action: Processing continues. request. User Action: None. status The status of the request: W Waiting DVG582I REQUEST NUMBER = reqnum; H Waiting and held. CLASS = class; priority The priority of the request. SUBMITTED = yy/mm/dd,hh:mm:ss; STARTED = yy/mm/dd,hh:mm:ss; retcd The return code of the last attempt to FINISHED = yy/mm/dd,hh:mm:ss; process the file-transfer request. RETURN CODE = retcdd; rsncd The reason code of the last attempt to REASON CODE = rsncd; process the file-transfer request. ORIGINATOR = orig class The server class.

Explanation: This message contains information for yy/mm/dd Date that the request was submitted: one finished OSI request. It is issued in response to yy=year, mm=month, dd=day. an administrator query for finished requests. hh:mm Time that the request was submitted: reqnum Request number of the file-transfer hh=hour, mm=minute. request. orig User ID of the originator of the file-transfer class Server class. request. yy/mm/dd,hh:mm:ss reqname The name of the OSI request. Date and time that either the request was System Action: Processing continues. entered by the user and stored on the User Action: None. queue, or the file transfer for this request was started, or the file transfer for this request was completed. retcd Return code from the file transfer. rsncd Reason code from the file transfer. orig User ID of the originator of the file-transfer request. System Action: Processing continues. User Action: None.

Chapter 1. NetView FTP Messages 77 DVG585I Ÿ DVG588I

yy/mm/dd Date that the file transfer ended: yy=year, DVG585I REQNUM = reqnum; mm=month, dd=day. ST = status; hh:mm Time that the file transfer ended: PRTY = priority; hh=hour, mm=minute. RC = retcd; RSN = rsncd; orig User ID of the originator of the file-transfer CL = class; request. START = yy/mm/dd,hh:mm; reqname The name of the OSI request. ORIG = orig; System Action: Processing continues. REQNAME = reqname User Action: None. Explanation: This message is issued in response to a user query for an OSI request. DVG587I OSI INPUT PARAMETER parmname INCORRECT reqnum The request number of the file-transfer OR MISSING request. status The status of the request: Explanation: An OSI file-transfer parameter is missing or incorrectly specified. parmname can be A Active (file transfer in progress). one of the following: priority The priority of the request. Ÿ Application Entity Title retcd The return code of the last attempt to Ÿ Permitted Actions Passwords process the file-transfer request. Ÿ Initiator Function rsncd The reason code of the last attempt to Ÿ Destination Effect process the file-transfer request. Ÿ Document Type Ÿ File Availability class The server class. Ÿ Filestore Owner yy/mm/dd Date that the file transfer started: Ÿ Future Filesize yy=year, mm=month, dd=day. Ÿ Local File Name Ÿ Local OSI File Name hh:mm Time that the request was started: Ÿ Local Filestore Subset hh=hour, mm=minute. Ÿ Maximum String Length orig User ID of the originator of the file-transfer Ÿ Transfer Mode request. Ÿ Remote OSI File Name reqname The name of the OSI request. Ÿ Local Filestore Nickname Ÿ String Significance System Action: Processing continues. Ÿ Universal Class. User Action: None. Ÿ No OSI Parameters. This message is displayed when the interface validation routine found that the indicated parameter DVG586I REQNUM = reqnum; was either missing or not specified according to the ST = status; restrictions as specified in the OSI transfer parameter PRTY = priority; description. If there is more than one parameter in RC = retcd; error, only the last parameter found in error results in RSN = rsncd; a message. CL = class; FINIS = yy/mm/dd,hh:mm; Note: Some restrictions can be checked only within ORIG = orig; the OSI environment, that is in OSI/File Services. REQNAME = reqname System Action: The request is not submitted. Processing continues. Explanation: This message is issued in response User Action: Correct the error and resubmit the to a user query for an OSI request. request. reqnum The request number of the file-transfer request. DVG588I OSI TRANSFER REQUEST NUMBER reqnum status The status of the request: REJECTED F Finished. priority The priority of the request. Explanation: This message is issued when an OSI file-transfer request cannot be processed. Probably retcd The return code of the last attempt to a parameter value is incorrectly specified. This process the file-transfer request. message follows message DVG587I. rsncd The reason code of the last attempt to System Action: The request is not submitted. process the file-transfer request. Processing continues. class The server class. User Action: Correct the error and resubmit the request.

78 NetView FTP Messages and Codes DVG589I Ÿ DVG602A

User Action: The operator must enter either a DVG589I AT LEAST ONE PARAMETER WAS NetView FTP VSE command or at least the first REQUESTED WHICH IS VALID FOR AN letter of one of the following: SNA-TYPE REQUEST BUT INCOMPATIBLE MOUNTED WITH AN OSI REQUEST To indicate that the tape was mounted, as requested. The file-transfer request is Explanation: This message is issued if a service is processed. required that is not offered for an OSI file-transfer REQUEUE request. For example, it applies to the following To tell NetView FTP VSE to put the parameters: file-transfer request back in the request Ÿ Remote LU name or remote server group queue and change its status to waiting. Ÿ Server running mode (= single) CANCEL To tell NetView FTP VSE to cancel the Ÿ Restart from checkpoint file-transfer request. The file-transfer Ÿ Automatic transfer restart request status is set to finished. Ÿ Data Compression Ÿ Data encryption Ÿ Remote check of the request DVG602A MOUNT TAPE volser WITHOUT RING ON UNIT Ÿ OS/400 connection unit; Ÿ Post-transfer program (local and remote) REPLY WITH M(OUNTED), R(EQUEUE), OR Ÿ Remote post-transfer job. C(ANCEL) Note: All non-OSI file parameters are rejected. System Action: The request is not submitted. Explanation: NetView FTP wants the operator to Processing continues. mount a tape. User Action: Correct the error and resubmit the volser Volume serial number of the tape to be request. mounted. If, for an unlabeled tape, a value for the volume serial number is not specified, the default value SCRTCH is DVG600A ENTER NETVIEW FTP COMMAND OR END used. unit Tape unit that the tape is to be mounted Explanation: The operator started communication on. with VSE by entering the VSE command MSG p, System Action: The server that needs the tape where p is the identifier of the NetView FTP partition. waits until the operator replies to the message. The NetView FTP VSE responds by displaying this NetView FTP partition that issued the message message. continues processing, but cannot display any further System Action: NetView FTP processing console messages until the operator replies to the continues, the NetView FTP partition that issued this message. message cannot display any further console User Action: The operator must enter either a messages until the operator replies to this message. NetView FTP VSE command or at least the first User Action: The operator must enter either END, letter of one of the following: to terminate the communication with NetView FTP MOUNTED VSE, or a NetView FTP VSE command. To indicate that the tape was mounted, as requested. The file-transfer request is processed. DVG601A MOUNT TAPE volser WITH RING ON UNIT unit; REPLY WITH M(OUNTED), R(EQUEUE), OR REQUEUE C(ANCEL) To ask NetView FTP VSE to put the file-transfer request back in the request Explanation: NetView FTP wants the operator to queue and change its status to waiting. mount a tape. CANCEL To ask NetView FTP VSE to cancel the volser Volume serial number of the tape to be file-transfer request. The file-transfer mounted. If, for an unlabeled tape, a request status is set to finished. value for the volume serial number is not specified, the default value SCRTCH is used. unit Tape unit that the tape is to be mounted on. System Action: The server that needs the tape waits until the operator replies to the message. The NetView FTP partition that issued the message continues processing, but cannot display any further console messages until the operator replies to the message.

Chapter 1. NetView FTP Messages 79 DVG603I Ÿ DVG613I

User Action: The operator should first reply to this DVG603I TRANSFER reqnum ENDED; message with one of the following: RC=retcd; GO To indicate that NetView FTP VSE is to RSN=rsncd continue transferring files without sending any transfer report files. Explanation: This message informs the recipient of STOP NVFTP the outcome of the file transfer. Stop all servers immediately and reqnum Request number. This can be zero, if terminate processing in the NetView FTP there is no valid file-transfer request when partition. the message is issued. Then analyze the problem referring to message retcd Return code from file transfer. DVG613I in the log file. rsncd Reason code from file transfer. System Action: Processing continues. DVG612W COMMUNICATION WITH VSE/POWER NOT ESTABLISHED OR INTERRUPTED; User Action: If the return code is 0, no action is PROCESSING CONTINUES WITHOUT REPORT required. If the return code is not 0, the return and TRANSMISSION reason codes indicate the required action. REPLY WITH “GO” TO CONTINUE OR “STOP NVFTP” TO TERMINATE DVG610A COMMUNICATION WITH VSE/POWER NOT ESTABLISHED; Explanation: Either NetView FTP VSE could not REPLY WITH “GO” TO CONTINUE OR “STOP establish communication with VSE/POWER or NVFTP” TO TERMINATE communication with VSE/POWER was interrupted. If the NetView FTP partition initialization parameter Explanation: The communication with OPMODE is set to UNATTENDED this message is VSE/POWER could not be established at NetView issued instead of DVG610A or DVG611A. FTP partition startup time, so NetView FTP VSE System Action: The program continues transferring cannot send file-transfer reports. files without sending any transfer report files until a System Action: The program waits for an operator reply is received. The message remains on the response. Further processing depends on the screen until the operator replies. operator’s response. User Action: The operator should first reply to this User Action: The operator should first reply to this message with one of the following: message with one of the following: GO To indicate that NetView FTP VSE is to GO To indicate that NetView FTP VSE is to continue transferring files without sending continue processing without sending any any transfer report files. transfer report files. STOP NVFTP STOP NVFTP Stop all servers immediately and To indicate that NetView FTP VSE is to terminate processing in the NetView FTP terminate processing. partition. and then analyze the problem referring to message Then analyze the problem referring to message DVG613I in the log file. DVG613I in the log file.

DVG611W COMMUNICATION WITH VSE/POWER DVG613I COMMUNICATION WITH VSE/POWER FAILED; INTERRUPTED; NETVIEW FTP TASK = task-name; PROCESSING CONTINUES WITHOUT REPORT RETURN CODE = retcd; TRANSMISSION; FUNCTION = function; REPLY WITH “GO” TO CONTINUE OR “STOP POWER SAS RETURN INFO (HEX) = errinfo NVFTP” TO TERMINATE Explanation: This message is written to the log file Explanation: The NetView FTP partition whenever any of the messages concerning established communication with VSE/POWER, but VSE/POWER communication problems (DVG610A, the communication was interrupted while the DVG611A, DVG612I) are written to the operator’s NetView FTP partition was running. NetView FTP console. It contains more information about the VSE can no longer send transfer reports. problem. System Action: The program continues transferring task-name files without sending any transfer report files until a Name of the affected NetView FTP task. reply is received. The message remains on the retcd VSE/POWER or XPCC return code. screen until the operator replies.

80 NetView FTP Messages and Codes DVG614I Ÿ DVG619I

function Performed XPCC function. errinfo Additional error information. One or two DVG616I CDLOAD OF TAPE DEFINITION TABLE FAILED; hexadecimal digits for each of the CDLOAD RETURN CODE = cdlretcd following: ALL TAPE UNITS IGNORED; Ÿ XPCC return code Ÿ XPCC reason code Explanation: The tape definition table (DVGTDF) Ÿ VSE/POWER return code could not be loaded. All assigned tape units are Ÿ VSE/POWER feedback code. ignored and file-transfer requests, involving files stored on tape, cannot be satisfied. See VSE/POWER 4.1 Application Programming for information about VSE/POWER return and feedback cdlretcd Return code from the VSE CDLOAD codes. macro. System Action: Processing continues according to System Action: NetView FTP VSE acts as if no corresponding message DVG610A, DVG611A, or tape unit is assigned. DVG612A. User Action: NetView FTP VSE continues without User Action: Analyze the information in the tape units. If these are urgently needed, terminate message to find the reason for the problem. It may the program and correct the error condition by be caused by one of the following: including the DVGTDF phase in the defined libraries. Ÿ VSE/POWER problems (for example: no response within 2 minutes or termination) DVG618I UNKNOWN DEVICE MODE FOUND FOR lunum; Ÿ VSE XPCC System GETVIS problems. DEVICE MODE device mode;

Explanation: The tape mode taken from the VSE DVG614I DEVICE TYPE dev-type ASSIGNED TO lunum Physical Unit Control Block (PUB) could not be found in the tape definition table (DVGTDF). Explanation: A tape device of type dev-type is If the tape device assigned to this logical unit number assigned to the logical unit lunum. is not a cartridge device, it is not possible to write to dev-type Type of tape device. an unlabeled tape. If the tape device assigned to this logical unit number is a cartridge device that lunum Logical unit number of the tape unit. allows data compression, it is not possible to write to System Action: None. this cartridge. User Action: If the correct tape-device type is lunum Logical unit number of tape unit. assigned, none. If the tape-device type is not device mode correct, stop NetView FTP and check NetView FTP Unknown tape device mode. VSE tape definition table. System Action: NetView FTP VSE cannot write to unlabeled reel tapes or to cartridge tape units that DVG615I NO TAPE DEVICE TYPE FOUND FOR lunum; allow data compression. DEVICE TYPE CODE dev-type; User Action: Check whether the tape unit assigned UNIT IGNORED to the logical unit number is shown in the NetView FTP VSE tape definition table. If not, only restricted Explanation: The VSE EXTRACT macro did not use is possible. return the device-type number and VSE PUB device type code is not X'50', X'52', or X'53'. DVG619I UNKNOWN DEVICE TYPE FOUND FOR lunum; lunum Logical unit number of unit. DEVICE TYPE CODE device type code; dev-type PUB device type code. System Action: NetView FTP VSE ignores the Explanation: The device type extracted from the tape unit. VSE Physical Unit Control Block Extension (PUBX) User Action: Check that the tape unit is correctly could not be found in the tape definition table assigned. This situation should not occur with IBM (DVGTDF). tape units. If it does, contact your IBM Support lunum Logical unit number of tape unit. Center. device type code Unknown device type code. System Action: NetView FTP VSE uses the tape unit as assigned. User Action: Check whether the tape device assigned to the logical unit number is shown in the NetView FTP VSE tape definition table. If not, only restricted use is possible.

Chapter 1. NetView FTP Messages 81 DVG620I Ÿ DVG627I

DVG620I REQUEST QUEUE NOT CLEANED UP DVG624I ERROR WHEN UNLOCKING THE REQUEST QUEUE; Explanation: During initialization of a NetView FTP ERROR CODE FROM UNLOCK = code partition, requests on the request queue that have the status active were not given the status waiting, Explanation: An error occurred when the queue because another NetView FTP partition or another handler task tried to unlock the request queue. NetView FTP user interface is already running. code System return code. System Action: Initialization of the NetView FTP System Action: The queue handler is stopped. partition continues. User Action: See VSE/ESA Version 1 System User Action: None. Macros Reference or VSE/AF 4.1.1 Macro Reference. DVG621I REQUEST QUEUE SUCCESSFULLY CLEANED UP; DVG625I ERROR IN THE REQUEST QUEUE WHILE recnum REQUEST(S) REQUEUED PROCESSING REQUEST NUMBER number

Explanation: During initialization of the NetView Explanation: During processing of a queue handler FTP partition, any requests in the request queue that command either a logical error was detected for a have the status active were given the status request in the request queue or an inconsistency has waiting. been detected between the request queue’s base recnum Number of records that were requeued. cluster and its alternate index. System Action: Initialization of the NetView FTP number The number of the request that was being partition continues. processed. User Action: None. System Action: Processing is terminated. User Action: Ask the NetView FTP system DVG622I ERROR WHEN DEFINING A LOCK FOR THE administrator to delete the faulty request, or to REQUEST QUEUE; rebuild the alternate index. ERROR CODE FROM GENDTL = code DVG626I REQUEST NUMBER reqnum NOT DELETED; Explanation: When generating DTL for request REQUEST IS ACTIVE queue locks, via the system macro GENDTL, an error occurred. Explanation: A user tried to delete an active code System return code. request but requests marked as active cannot be deleted. System Action: The queue handler is stopped. reqnum Request number. User Action: See VSE/ESA Version 1 System Macros Reference or VSE/AF 4.1.1 Macro System Action: Processing continues. If a request Reference. is still active after a NetView FTP partition ends, it is automatically requeued and given the status waiting.

DVG623I ERROR WHEN LOCKING THE REQUEST User Action: Either wait until the transfer has QUEUE; finished and then delete the request, or ask your ERROR CODE FROM LOCK = code operator to stop the server that handles the request at the moment, and then delete the request, before it is restarted again. Explanation: An error occurred when the queue handler task tried to lock the request queue. code System return code. DVG627I RETRIEVAL OF REQUEST reqnum FAILED System Action: The queue handler is stopped. Explanation: An attempt to retrieve the request User Action: See VSE/ESA Version 1 System with the given request number from request queue Macros Reference or VSE/AF 4.1.1 Macro failed, although this is a valid request number. Reference. reqnum Request number. System Action: Queue handler processing terminates. User Action: Ask your system administrator to check the request queue.

82 NetView FTP Messages and Codes DVG628I Ÿ DVG632I

DVG628I CLUSTER DEFINITION OF num TOO SMALL DVG631I NETVIEW FTP PARTITION jobname ENDED FOR REQUEST QUEUE ON yy/mm/dd AT hh:mm:ss; RETURN CODE=retcd; Explanation: The queue handler recognized that REASON CODE = rsncd; the number of records generated for the request OPERATING SYSTEM RETURN CODE = queue was too small. No records for use by opsysrc requests could be added. Explanation: The NetView FTP partition stopped. num Number of records in request queue. jobname Job name of the NetView FTP partition. System Action: Queue handler processing terminates. yy/mm/dd Date that the NetView FTP partition stopped: yy=year, mm=month, dd=day. User Action: Define a larger request queue. hh:mm:ss Time that the NetView FTP partition stopped: hh=hour, mm=minute, DVG629I num RECORD(S) IN ERROR ON REQUEST ss=second. QUEUE; STARTING RECORD NUMBER = strtno; retcd Highest return code returned by a server ENDING RECORD NUMBER = endno (at least 4) or from the NetView FTP partition.

Explanation: While scanning the request queue for rsncd Reason code from the NetView FTP a query request, records were found with an error in partition. their request status fields. opsysrc Return code from the related operating num Number of records in error. system. strtno Record number of the first record in error System Action: The NetView FTP partition stops. in the request queue. User Action: None. endno Record number of the last record in error in the request queue. DVG632I NETVIEW FTP TASK task TERMINATED System Action: Processing continues. ABNORMALLY; User Action: Notify your system administrator. TASK RETURN CODE = stretcd; Print the request queue and identify the record in TASK REASON CODE = strsncd; error using the request number that can be found: SYSTEM INFORMATION = sysinfo Ÿ For MVS and VM, at offset 0 with a length of 4 Explanation: The specified task terminated bytes abnormally. Ÿ For VSE, at offset 16 with a length of 4 bytes. task Server ID (or server prefix + QH, TC, UN, Contact your IBM Support Center. SY, or OI) of the task that terminated abnormally. DVG630I NETVIEW FTP PARTITION jobname STARTED stretcd Return code from the task. ON yy/mm/dd AT hh:mm:ss strsncd Reason code from the task.

Explanation: The NetView FTP partition sysinfo Additional system ABEND information. initialization is completed. System Action: NetView FTP VSE proceeds as jobname Job name of the NetView FTP partition. follows: yy/mm/dd Date that the NetView FTP partition Ÿ If a server task terminated abnormally and there started: yy=year, mm=month, dd=day. is still at least one started server, the number of available servers is reduced. hh:mm:ss Time that the NetView FTP partition started: hh=hour, mm=minute, Ÿ If a server task terminated abnormally and the ss=second. server was the last started server, and AUTOTERM=YES was specified in the startup System Action: Processing continues. job for the NetView FTP partition, the maintask User Action: None. terminates. Ÿ If another task is terminated abnormally (that is, where the last two characters are QH, TC, UN, SY, or OI) the NetView FTP partition terminates immediately. User Action: None.

Chapter 1. NetView FTP Messages 83 DVG633I Ÿ DVG639I

DVG633I NETVIEW FTP PARTITION INITIALIZATION DVG635I SEVERE ERROR WHILE PROCESSING FILE FAILED; TRANSFER; RETURN CODE = retcd; FILE TRANSFER INTERRUPTED REASON CODE = rsncd; SYSTEM CODE = syscd Explanation: An error occurred in the NetView FTP partition processing while your file-transfer request Explanation: An error occurred during initialization was being processed. of a NetView FTP partition. System Action: The file transfer ends and NetView retcd Return code (decimal) from the NetView FTP changes the status of the request to finished. FTP partition. User Action: If you want the file transfer to be rsncd Reason code (decimal) from the NetView reestablished, ask the operator if there is a server FTP partition. started that processes the class of the interrupted request. If not, ask the operator to start one, and syscd Return code (decimal) from the related then resubmit your request. If the problem persists, operating system. If the return code is contact your IBM Support Center. greater than zero the GETVIS system macro failed. System Action: The NetView FTP partition job is DVG638I CDLOAD OF MODULE phase FAILED; RETURN canceled. CODE FROM CDLOAD = cdrc User Action: Correct the error and restart the job. Explanation: The loading of an essential module failed during initialization of NetView FTP. This may DVG634I COMMAND command CURRENTLY NOT be because you tried to load a message definition ALLOWED; module that is not available. The message module VALID COMMANDS ARE list name is in the form DVGCCMDx, where x represents the first letter of the specified language. Explanation: This message is written to the phase Name of load module. operator’s console whenever NetView FTP cannot cdrc Return code from CDLOAD. currently handle a NetView FTP operator command. System Action: Processing terminated. command User Action: Ask your administrator to check if the Command entered by the operator. load module is available, or refer to VSE/ESA list List of valid commands. Can be any of Version 1 System Macros Reference or VSE/AF the following: 4.1.1 Macro Reference for information about the C Cancel a file-transfer request for return code. a tape file E End operator communication DVG639I MACRO macro FAILED; RETURN CODE = retcd; D Display information PHASE NAME = phase-name F Modify a server G Make NetView FTP continue processing Explanation: An error occurred in a NetView FTP M Indicate that a requested tape is component when it attempted to load or delete a mounted module. P Stop servers or the NetView FTP macro Macro that encountered the error: partition R Requeue a file-transfer request Ÿ LOAD for a tape file Ÿ CDLOAD S Start servers. Ÿ DELETE. System Action: Processing continues. retcd Return code from the macro. For more information about this return code, refer to User Action: Enter one of the allowed commands. VSE/ESA Version 1 System Macros Other operator commands can be entered after Reference or VSE/AF 4.1.1 Macro enabling the operator interface using the VSE MSG Reference. command. phase-name Note: When AUTOTERMINATION is set to YES Phase name. and all servers have stopped. Enter END to cause System Action: Processing terminates if the error the NetView FTP partition to finish termination. No occurs when loading or deleting an essential load other command is allowed. module.

84 NetView FTP Messages and Codes DVG640I Ÿ DVG647I

User Action: If the problem persists for: Ÿ LOAD, analyze the return code DVG643I VSE/POWER SAS COMMUNICATION NOT Ÿ CDLOAD, analyze the return code AVAILABLE; Ÿ DELETE, contact your IBM Support Center. REPORT WAS NOT TRANSMITTED

Explanation: VSE/POWER spool access services DVG640I LOCAL VSE/POWER HAS NO PNET SUPPORT; (SAS) communication could not be established or RETURN CODE FROM POWER = retcd was interrupted. This message precedes the corresponding report in Explanation: This message is issued during the report collection file. initialization of the NetView FTP partition if no VSE/POWER PNET support is installed on your VSE System Action: The report is not transmitted. system. User Action: Stop NetView FTP. After you can retcd The POWER return code from PWRSPL. establish an XPCC connection via the VSE/POWER SAS, restart NetView FTP. System Action: Processing continues. No spooling of NetView FTP transfer reports takes place. User Action: None. DVG645I TASK task1 TRIED TO POST TASK task2 BUT task2 WAS NOT READY

DVG641I TRANSMISSION TO VSE/POWER PNET NODE Explanation: While processing a file-transfer node WAS REQUESTED BUT PNET WAS NOT request a task tried to post another task but the AVAILABLE; posted task was not ready. REPORT WAS NOT TRANSMITTED task1 Posting task.

Explanation: A file-transfer request specified that a task2 Posted task. file-transfer report was to be sent to a user at the System Action: Processing continues. remote VSE/POWER node shown in the message, User Action: Contact your IBM Support Center. however VSE/POWER PNET support was not available. This message precedes the corresponding report in DVG646I THE OPERATOR HAS CANCELED A TAPE-FILE the report collection file. TRANSFER System Action: The report is not transmitted. Explanation: You tried to transfer a tape file, User Action: Ask your system administrator to however, the operator received a tape mount provide VSE/POWER PNET support. message and canceled the tape-file transfer. System Action: The file transfer ends and NetView DVG642I VSE/POWER SAS OPEN WAS REJECTED; FTP changes the status of the request to finished. FEEDBACK CODE = code; User Action: Contact the tape operator at the REPORT DESTINATION = user AT node; system where the file transfer was canceled. REPORT WAS NOT TRANSMITTED Resubmit the file transfer when the tape operator is able to handle your file-transfer request. Explanation: The VSE/POWER spool access services (SAS) rejected the transmission startup request for this transmission. DVG647I THE OPERATOR HAS REQUEUED A TAPE-FILE TRANSFER This message precedes the corresponding report in the report collection file. Explanation: You tried to transfer a tape file, code VSE/POWER SAS feedback code as however, the operator received a tape mount described in VSE macro PWRSPL. message and requeued the tape-file transfer. user User to whom the report was to be sent. System Action: The file transfer ends. Depending node VSE/POWER node of the user to whom on the value of the Automatic Transfer Restart the report was to be sent. parameter, NetView FTP changes the status of the System Action: The report is not transmitted. request either to waiting or finished. User Action: Check the user ID and node name User Action: Take whatever action is appropriate. specified in the request; possibly one of these is incorrect. If they are both correct, analyze the VSE/POWER SAS feedback code.

Chapter 1. NetView FTP Messages 85 DVG648I Ÿ DVG660I

DVG648I THE TRANSFER OF A TAPE FILE IS NOT DVG655I STORAGE MANAGEMENT SUBSYSTEM (SMS) POSSIBLE AT AN UNATTENDED NODE IS NOT AVAILABLE

Explanation: You tried to transfer a tape file but the Explanation: Dynamic allocation for the receiving system where the tape file is stored is running in data set failed and returned error reason code 1232 unattended mode. (X'04D0'). System Action: The file transfer ends and NetView System Action: The server tries to dynamically FTP changes the status of the request to finished. allocate the receiving data set without using the SMS parameters specified in the request. User Action: Take whatever action is appropriate. For example, ask the system administrator at the User Action: None. system where the file transfer has been stopped to change to attended mode. DVG656I text

DVG650I TAPE UNIT SELECTION FAILED; Explanation: This message contains output from REASON CODE = rsncd Dynamic Allocation. If a problem occurred during dynamic allocation, this message might help you Explanation: NetView FTP failed to select a tape solve the problem. unit from the FTP Tape Unit List. The reason code System Action: Processing continues. contains details of the problem. User Action: None. rsncd Reason code from tape select. Refer to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109. DVG657I SMS PARAMETERS; System Action: The server processing the request DATA CLASS = dataclass; terminates. The request is finished or requeued, MANAGEMENT CLASS = manclass; depending on the reason code. STORAGE CLASS = storclass User Action: Specify the tape information in the request or wait for the next request selection for file Explanation: This message is issued at the end of transfer. a file transfer for which SMS parameters were specified. dataclass SMS data class. DVG651I SERVER servername HELD ACCESS manclass SMS management class. AUTHORIZATION LONGER THAN ALLOWED BY storclass SMS storage class. THE TIME INTERVAL intval; THE SERVER HAS STOPPED System Action: Processing continues. User Action: None. Explanation: The server has requested Access Authorization. Access Authorization was not DVG660I JOB jobname(jobid) SUBMITTED; disabled within the specified time interval. MEMBER NAME = memname; servername DATA SET NAME = dsname Server ID holding Access Authorization. intval Timer interval. Explanation: NetView FTP successfully submitted System Action: The server is forced to terminate a post-transfer job. abnormally to avoid security problems. jobname The job name of the submitted job. User Action: Check why the time interval is not jobid The job ID of the submitted job assigned sufficient for the functions requiring Access by the job entry system. Authorization. For example, an outstanding tape memname mount, or a program loop in a user-written file The name of the member containing the handler. JCL of the submitted job. In the case of a program loop in a user-written file dsname The name of the data set containing the handler that can establish its own recovery routine, member memname. this user-written file handler cannot be used until the NetView FTP partition has stopped. System Action: Processing continues. User Action: None.

86 NetView FTP Messages and Codes DVG661I Ÿ DVG667I

DVG661I DYNAMIC ALLOCATION ERROR; DVG663I MEMBER memname NOT FOUND; DATA SET NAME = dsname; DATA SET NAME = dsname RETURN CODE = retcd; INFORMATION REASON CODE = infcode; Explanation: The data set with the name dsname ERROR REASON CODE = errcode did not contain the member with the name memname. The post-transfer job submission Explanation: An error occurred during the dynamic parameter values are not correct. allocation of the data set containing the job. System Action: The job is not submitted. dsname Name of the data set in error. If the Processing continues. data-set name is INTRDR, a dynamic User Action: Take whatever action is appropriate. allocation error occurred for the SYSOUT For example, make sure the member exists and its data set that was destined for the internal name is specified correctly. reader. retcd Return code. DVG666I DATA SET ORGANIZATION IS NOT PO; infcode Information reason code. DATA SET NAME = dsname; errcode Error reason code. DSORG RETURNED BY SVC 99 = dsorg System Action: The request is not submitted. Processing continues. Explanation: The data set containing a post-transfer job must be partitioned organized (PO). User Action: Refer to the description of the SVC 99 (sometimes referred to as Dynamic dynamic allocation interface return (DAIR) errors that Allocation Service) returned a DSORG other than can be found in the online ISPF tutorial. For further PO. information, refer to: dsname The name of the data set. Ÿ MVS/ESA SPL: Application Development Guide Ÿ MVS/XA System Macros and Facilities dsorg The DSORG that SVC 99 returned for the Volume 1. data set. System Action: The job is not submitted. Processing continues. DVG662I I/O ERROR FOR QSAM macro; DATA SET NAME = dsname; User Action: Refer to MVS/ESA SPL: Application UNIT = unit; Development Guide and MVS/XA System Macros DEVICE TYPE = devtype; and Facilities Volume 1 for information about OPERATION = operation; DSORG return specifications from SVC 99. ERROR DESCRIPTION = errordesc; PHYSICAL RECORD ADDRESS = bbcchhr DVG667I VSAM request ERROR ON INTERNAL READER DATA SET; Explanation: An I/O error occurred while NetView REG 15 RETURN CODE = reg15; FTP was processing the job submission request via VSAM ERROR CODE = errcode QSAM.

macro QSAM macro in error is one of the Explanation: An error occurred during job following: submission processing of the VSAM SYSOUT data Ÿ CLOSE set allocated to the internal reader. Ÿ GET request One of the following: Ÿ OPEN Ÿ PUT. Ÿ OPEN Ÿ PUT dsname Name of the data set. Ÿ ENDREQ unit Unit address. Ÿ CLOSE. devtype Device type. reg15 Contents of register 15 returned by VSAM. operation Operation attempted. errcode VSAM error code. errordesc Description of error. System Action: The submitted job is not executed. bbcchhr Direct access address of record in error. Processing continues. System Action: The job is not submitted. User Action: Analyze the problem using one or Processing continues. more of the following: User Action: See one or more of the following: Ÿ MVS/DFP V3: Macro Instructions for VSAM Data Ÿ MVS/DFP V3: Macro Instructions for non-VSAM Sets Data Sets Ÿ MVS/XA VSAM Administration Macro Instruction Ÿ MVS/XA Data Administration: Macro Instruction Reference. Reference.

Chapter 1. NetView FTP Messages 87 DVG668I Ÿ DVG675W

DVG668I MEMBER memname OF DATA SET dsname IS DVG673I DATA SET ORGANIZATION MISMATCH; EMPTY TARGET DATA SET IS A VSAM RELATIVE RECORD DATA SET Explanation: The member with the name memname specified to contain the JCL of the job to Explanation: To transfer data to a VSAM RRDS, be submitted is empty. the source file must also be relative record organized. System Action: The job is not submitted. Processing continues. System Action: Transfer ends. User Action: Either fill the member with the User Action: Check whether the specified data set appropriate job, or correct the member name or names are correct. If the source data set is not data-set name if they were wrongly specified. relative-record organized, specify a data set with a data set organization other than VSAM RRDS as target data set. DVG670I NETVIEW EVENTS

Explanation: Certain NetView FTP events are DVG674I VSAM LINEAR DATA SETS CANNOT BE issued to the operator’s console as WTO messages. TRANSFERRED FROM OR TO OTHER DATA A NetView CLIST scanning these messages can SET TYPES initiate automatic operations according to the information issued with the event. Explanation: NetView FTP does not support the combination of VSAM linear data sets and data sets System Action: Processing continues. of different types within one file transfer. User Action: None. For more information, refer to System Action: The file transfer ends and NetView NetView FTP V2 MVS Installation, Operation, and FTP changes the status of the request to finished. Administration. User Action: Correct the error and resubmit the request. DVG671I MODULE module SUCCESSFULLY LOADED

Explanation: The module to be executed as DVG675W CONTROL INTERVALS FOUND WHILE specified by the post-transfer program parameter OPENING VSAM LINEAR DATA SET dsname was loaded successfully. Explanation: The receiving data set is a VSAM module Name of load module. linear data set and has the name dsname. While System Action: Processing continues. opening the receiving data set the server detected User Action: None. that it was not empty. Because a related checkpoint record did not exist, the server expected the receiving data set to be empty. The server writes DVG672I ERROR WHILE LOADING module; over any existing control intervals. If there are more SYSTEM ABEND CODE = abnd; control intervals in the data set than are being SYSTEM REASON CODE = rscd transferred to it, these other control intervals remain in the data set. This may cause an integrity problem. Explanation: During execution of a LOAD System Action: The server writes control intervals macroinstruction, a system error occurred. from the beginning of the data set. A warning is module Module name that could not be loaded. issued in the file-transfer completion message. abnd System ABEND code. User Action: If an integrity problem exists, delete and redefine the data set. After you have corrected rscd System reason code. the errors, resubmit the file-transfer request. If no System Action: The specified module is not integrity problem exists ignore the message. loaded. Processing continues. User Action: Refer to one or more of the following: Ÿ MVS/ESA Application Development Reference: Services for Assembler Language Programs Ÿ MVS/XA Supervisor Services and Macros.

88 NetView FTP Messages and Codes DVG676I Ÿ DVG690I

DVG676I REMOTE CHECK FOR FILE TRANSFER DVG679W RECORDS FOUND WHILE OPENING VSAM REQUEST reqnum STARTED ON yy/mm/dd AT RRDS dsname hh:mm:ss Explanation: The receiving data set is a VSAM Explanation: Remote check was specified in the RRDS and has the name dsname. During the OPEN request. This is the date and time that NetView FTP on the receiving data set, the server detected that it started checking the file-transfer request reqnum. was not empty. reqnum Request number. System Action: Processing continues; the server writes records from the beginning of the data set. A yy/mm/dd Date that the remote check started: warning is issued in the file-transfer completion yy=year, mm=month, dd=day. message. hh:mm:ss Time that the remote check started: User Action: If an integrity problem exists, delete hh=hour, mm=minute, ss=second. and redefine the data set and, after you have System Action: NetView FTP processing corrected the errors, resubmit the file-transfer continues. request. User Action: None. DVG680I MODIFICATION OF TRANSFER REQUEST DVG677I REMOTE CHECK FOR FILE TRANSFER REJECTED BECAUSE OF INVALID INPUT REQUEST reqnum ENDED ON yy/mm/dd AT FROM THE POST-CONVERSATION EXIT hh:mm:ss; ROUTINE RC = retcd; RSN = rsncd Explanation: The post-conversation user exit routine was called. On return, NetView FTP Explanation: Remote check was specified in the detected any of the following incorrect modifications request. This is the date and time that NetView FTP made to the file-transfer request: finished checking the file-transfer request reqnum. Ÿ Not-after time and date yy/mm/dd Date that the remote check finished: Ÿ Not-before time and date yy=year, mm=month, dd=day. Ÿ Restart from checkpoint indicator. hh:mm:ss Time that the remote check finished: System Action: NetView FTP processing hh=hour, mm=minute, ss=second. continues. The file-transfer request is not modified. retcd Return code. User Action: Check the modification made in the rsncd Reason code. post-conversation user exit routine. Refer to System Action: NetView FTP processing NetView FTP Customization for a further explanation continues. of what modifications can be made. Correct the error, and compile and link the exit routine. User Action: None.

DVG690I REQUEST QUEUE INFORMATION; QUEUE SIZE DVG678I CHECK reqnum ENDED; = size RC = retcd; RSN = rsncd Explanation: This message is issued in response to an administrator query for information about the Explanation: Remote check was specified in the request queue. request. This message is issued when a remote check has finished. size The total number of requests the request queue can hold. This number is specified reqnum Request number. by the system administrator when retcd Return code from the remote check. initializing the queue. rsncd Reason code from the remote check. System Action: NetView FTP processing continues. Refer to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109. User Action: None. System Action: Processing continues. If the return code from the remote check is zero, the file-transfer request is requeued with the status WAITING. Otherwise, the transfer request is given the status FINISHED. User Action: If the file-transfer request has the status WAITING, no action is necessary. Otherwise, check the return and reason code that explains the error. Correct it and resubmit the request.

Chapter 1. NetView FTP Messages 89 DVG701A Ÿ DVG710I

DVG701A MOUNT labeltype TAPE volser WITH RING ON DVG704I FILE-SERVICE COMPONENT COULD NOT UNIT unit WITH DENSITY density LOAD CMSAMS DCSS; CMS RETURN CODE = retcd Explanation: NetView FTP wants the operator to mount a tape. Explanation: The file-service component virtual machine tried to load the CMSAMS discontiguous labeltype Can be one of the following: shared segment, but the LODSYS command failed. SL Standard label retcd Return code from the LODSYS CMS NL Unlabeled command that was issued. Can be any of volser Volume serial number of the tape to be the following: mounted. If a value for the volume serial 1 Named segment defined as a number for an unlabeled tape is not VMGROUP specified, the default value is SCRTCH. 44 Named segment does not exist unit Tape unit that the tape is to be mounted on. 174 Paging I/O errors density Tape density. 179 The DASD volume specified by SYSVOL in the NAMESYS macro System Action: The file service component that is not owned by CP needs the tape waits until the operator replies to the message. NetView FTP continues processing, but 203 Users in a V=R area. cannot display any further NetView FTP console System Action: Processing terminates. messages until the operator replies to the message. User Action: Contact your system administrator. User Action: Mount the required tape.

DVG705I USER NOT CONNECTED TO SPECIFIED RACF DVG702A MOUNT labeltype TAPE volser WITHOUT RING GROUP ON UNIT unit WITH DENSITY density

Explanation: In the access security parameters, Explanation: NetView FTP wants the operator to you specified a RACF group ID to which you are not mount a tape. connected. labeltype Can be one of the following: System Action: Processing continues. SL Standard label User Action: Correct the error and resubmit the NL Unlabeled request. volser Volume serial number of the tape to be mounted. If a value for the volume serial number for an unlabeled tape is not DVG707I DISTRIBUTION-SERVICE COMPONENT WITH specified, the default value is SCRTCH. THE USER ID userid IS UNABLE TO ESTABLISH RACF ENVIRONMENT unit Tape unit name that the tape is to be mounted on. Explanation: In the access security parameters, density Tape density. you either specified an incorrect password, or the System Action: The file-service component that distribution service machine does not have the needs the tape waits until the operator replies to the correct RACF authorization. message. NetView FTP continues processing, but System Action: Processing terminates. cannot display any further NetView FTP console messages until the operator replies to the message. User Action: Correct the error and resubmit the request. User Action: Mount the required tape.

DVG710I INVALID USER ID userid SPECIFIED IN FILE-SERVICE COMPONENT TABLE

Explanation: NetView FTP VM detected a syntax error in the user ID specified for a file service component table. System Action: The user ID is ignored and processing continues. User Action: Contact your system administrator to correct the file service component table-entry.

90 NetView FTP Messages and Codes DVG711I Ÿ DVG717I

User Action: Do one of the following: DVG711I AUTOLOG OF userid WAS UNSUCCESSFUL; Ÿ Contact your system administrator CP RETURN CODE = retcd Ÿ FORCE the indicated user ID.

Explanation: The distribution service component failed to AUTOLOG the file service component DVG714I command COMMAND EXECUTION FAILED; shown in the message. RETURN CODE = retcd retcd Return code returned by CP, see one or more of the following: Explanation: The CMS/CP command shown in the message failed. Ÿ VM/ESA System Messages and Codes for 370 System Action: Processing terminates. Ÿ VM/XA SP System Messages and retcd CMS/CP command return code, see one Codes Reference or more of the following: Ÿ VM/SP System Messages and Ÿ VM/ESA System Messages and Codes. Codes for 370 System Action: NetView FTP VM tries to Ÿ VM/XA SP System Messages and AUTOLOG the next free file service component Codes Reference virtual machine. If running under VM/ESA*, Ÿ VM/SP System Messages and XAUTOLOG is used. Codes. User Action: None. fsmnum Number of file service components. User Action: Contact your system administrator. DVG712I THE MAXIMUM NUMBER OF REQUEST HANDLERS IS rhnum, BUT ONLY fsmnum DVG716A REPLY TO file-server WITH M(OUNTED), FILE-SERVICE COMPONENTS ARE SPECIFIED R(EQUEUE), OR C(ANCEL)

Explanation: There are not enough file service Explanation: This message is preceded by components declared in the file service components message DVG701A or DVG702A. table. file-server rhnum Maximum number of request handlers. The user ID or resource ID of the fsmnum Number of file service components. file-service component. System Action: Processing continues. The System Action: The file service component that number of request handlers is reduced to the number needs the tape waits until the operator replies to the of file-service components. message. NetView FTP continues processing, but User Action: The system administrator can correct cannot display any further NetView FTP console the problem by either: messages until the operator replies to the message. Ÿ Reducing the number of tasks (AVLSESS, User Action: The operator must enter at least the MAXSESS, AVLLRH, and AVLRRH initialization first letter of one of the following: parameters) MOUNTED Indicating that the tape was mounted Ÿ Increasing the number of file service as requested. components in the file service component table. REQUEUE Asking NetView FTP VM to put the file-transfer request back on the DVG713I userid ALREADY LOGGED ON request queue. CANCEL Asking NetView FTP VM to cancel Explanation: An entry in the file service component the request. table has been found but the file service component is already logged on. DVG717I THE USER ID OF THE CHECKPOINT MANAGER userid User ID or resource ID of the file service IS DIFFERENT FROM THE USER ID SPECIFIED component virtual machine. FOR THE CMID INITIALIZATION PARAMETER System Action: Processing continues. The file-transfer request that caused this message is Explanation: You specified a value for the requeued. It remains in the WAITING status until Checkpoint Manager ID (CMID) initialization any of the following happens: parameter but the checkpoint manager does not run Ÿ Another file service component that serves the in the virtual machine you specified. class specified obtains the request and System Action: Processing terminates. processes it User Action: Run the checkpoint manager in the Ÿ The operator solves the problem. virtual machine indicated by the checkpoint manager ID initialization parameter.

Chapter 1. NetView FTP Messages 91 DVG718I Ÿ DVG725I

DVG718I NO ENTRY IN FILE-SERVICE COMPONENT DVG722I NETVIEW FTP release; TABLE FOUND CHECKPOINT MANAGER userid ENDED ON date AT time; Explanation: The distribution-service component RETURN CODE=retcd tried to build the file-service component table, but there is no valid entry in DVGFST MACHINES file. Explanation: This is the termination message of the checkpoint manager. System Action: Server terminates during initialization. release Release level of the transfer program. User Action: Check your file service component userid User ID or resource ID of the checkpoint table definitions. Make sure that the FILEDEF manager virtual machine. command concatenates the correct file to the date Date that the checkpoint manager virtual system. machine stopped: year/month/day. time Time that the checkpoint manager virtual DVG720I FUNCTION function FAILED FOR MACHINE machine stopped: userid hours/minutes/seconds. retcd File-transfer return code. Explanation: An error occurred when one of the System Action: Processing continues. following functions for a checkpoint record was executed by the checkpoint manager: User Action: None. function Can be one of the following functions: Ÿ GET DVG723I message Ÿ PUT Ÿ DELETE. Explanation: This is a VM system message that is userid User ID or resource ID of the file service issued whenever a VM error occurs. For example, component that the checkpoint manager when a CMS command fails, or an OPEN error performed the function for. occurs. System Action: All file transfers currently in System Action: The system action depends on the progress finish. If the error occurred during a GET error. Either processing continues or the function, processing continues. Otherwise, the corresponding component terminates. checkpoint manager terminates. No new request is User Action: If the error is caused by incorrectly obtained. Also all file service components and specified file-transfer parameters, correct the distribution service components terminate. parameters and resubmit the file-transfer request. User Action: Examine the checkpoint manager log file. Look for additional messages that help you to DVG724I NETVIEW FTP CHECKPOINT MANAGER solve the problem. Correct the error and restart all INITIALIZATION FAILED; REASON CODE = terminated NetView FTP components. rsncd

DVG721I NETVIEW FTP release; Explanation: An error occurred while the CHECKPOINT MANAGER userid STARTED ON checkpoint manager was being initialized. date AT time; rsncd Reason code. For more information refer MAINTENANCE LEVEL = mlevel to Chapter 2, “NetView FTP ABEND, Return, and Reason Codes” on page 109. Explanation: This is the startup message of the System Action: The checkpoint manager checkpoint manager. terminates and produces a dump. No file transfer release Release level of the transfer program. can be processed. userid User ID or resource ID of the checkpoint User Action: Check the reason code to identify the manager virtual machine. cause of the failure. date Date that the checkpoint manager virtual machine started: year/month/day. DVG725I QUEUE HANDLER IS NOT ACTIVE time Time that the checkpoint manager virtual machine started: hours/minutes/seconds. Explanation: The operator entered a modify or stop mlevel Program maintenance level information operator command but the queue handler was not maintained by the system administrator. active. System Action: Processing continues. System Action: Processing continues. User Action: None. User Action: None.

92 NetView FTP Messages and Codes DVG726I Ÿ DVG730I

System Action: If this error is detected by: DVG726I SUBCOMMAND ENTERED FOR NETVIEW FTP Ÿ An interface routine, NetView FTP rejects the NOT ACCEPTED request. Ÿ A server, the file transfer ends. Explanation: The operator entered an unknown User Action: Correct the error and resubmit the subcommand or an incorrect abbreviation of a request. subcommand. System Action: Processing continues. DVG729I DISPOSITION VALUE value IS NOT ALLOWED User Action: Enter a valid NetView FTP FOR DATA SET TYPE type FOR THE subcommand. OPERATING SYSTEM opsys

DVG727I REQUEST CONTAINS PARAMETERS NOT Explanation: The value specified for disposition is SUPPORTED BY TRANSFER PROGRAM; not valid for the specified data-set type for the ERROR CODE = error-code corresponding operating system. System Action: If this error is detected by: Explanation: When checking the request, it was Ÿ An interface routine, NetView FTP rejects the detected that parameters were specified by one of request. the following sources: Ÿ A server, the file transfer ends. Ÿ Pre-transfer user exit routine value The value specified for the Disposition Ÿ Request from a remote system. parameter. error-code type The value specified for the Data-Set Type One of the following: parameter. 01 PDS member selection opsys The operating system that the transfer parameter program runs under (MVS, VM, VSE, or 02 PDS member exclusion OS/400). parameter User Action: Correct the error and resubmit the 03 PDS member information request. parameter

04 Encryption parameter DVG730I ERROR DURING COMMUNICATION 05 Sending OS/400 parameter PROCESSING TO resource; COMMUNICATION FUNCTION = function; 06 Receiving OS/400 parameter REASON CODE = rsncd 07 Extended user exit information parameters Explanation: The NetView FTP communication 08 Local job submission data interface detected an error while preparing or 09 Remote job submission data performing an APPC/VM or IUCV function and issued a reason code. 10 Local program call parameter resource Resource ID or User ID. 11 Remote program call parameter function Function from APPC/VM (for VM/SP) or 12 SMS parameter IUCV (for VM/XA). 13 APPC parameter. rsncd File-transfer reason code. System Action: Processing continues. System Action: The NetView FTP component that User Action: None. issued the message ends. User Action: Check the reason code. Refer to Chapter 2, “NetView FTP ABEND, Return, and DVG728I DISPOSITION VALUE value IS NOT ALLOWED Reason Codes” on page 109 for more information. FOR DATA SET TYPE type

Explanation: The value specified for disposition is not valid for the specified data-set type. value The value specified for the Disposition parameter. type The value specified for the Data-Set Type parameter.

Chapter 1. NetView FTP Messages 93 DVG731I Ÿ DVG741I

User Action: For a description of the return code DVG731I ERROR DURING function PROCESSING TO see the following: resource; Ÿ VM/ESA CMS Application Development code-field = error-code Reference for Assembler Ÿ VM/ESA Group Control System Reference for Explanation: An error occurred during APPC/VM or 370 IUCV processing. Ÿ VM/XA SP CMS Application Program Development Reference function One of the following: Ÿ VM/XA SP Group Control System Command Ÿ CONNECT and Macro Reference Ÿ SENDDATA Ÿ VM/SP Application Development Reference for Ÿ SEND CMS Ÿ SENDERR Ÿ VM/SP Group Control System Command and Ÿ RECEIVE. Macro Reference. resource Resource ID or User ID. code-field One of the following: DVG733I OPEN ON FILE DVGAS NOT SUCCESSFUL; Ÿ IPRCODE FTP DEFAULTS WILL BE TAKEN Ÿ IPAUDIT1 Ÿ IPAUDIT2 Explanation: An error occurred while opening the Ÿ IPAUDIT3 file DVGAS. Either, you did not specify a FILEDEF Ÿ Condition code. for the DVGAS file and want to use the defaults, or error-code another open error occurred. The value of the field specified in System Action: Processing continues using the code-field. default values. System Action: The NetView FTP component that User Action: None. issued the message ends. User Action: For a description of the error codes DVG734I NO CONNECTION RECEIVED FROM QUEUE see: HANDLER Ÿ VM/ESA CP Programming Services for 370 VM/XA SP CP Programming Services Ÿ Explanation: To establish an operator path the VM System Facilities for Programming. Ÿ queue handler must connect to the distribution-service component, but the DVG732I ERROR DURING macro function PROCESSING distribution-service component did not receive a TO resource; connect request. RETURN CODE = retcd System Action: The distribution-service component terminates. Explanation: The value of the return code field User Action: Contact your system administrator. describes the completion of the macro issued. After the problem is solved, restart the distribution macro One of the following: service component. Ÿ HNDIUCV Ÿ IUCVINI DVG741I NETVIEW FTP release; DISTRIBUTION-SERVICE Ÿ CMSIUCV COMPONENT userid STARTED ON date AT time; Ÿ IUCVCOM. MAINTENANCE LEVEL = mlevel function One of the following: Explanation: A server started. Ÿ SET Ÿ CONNECT release Release level of transfer program. CLR. Ÿ userid User ID or resource ID of the distribution resource Resource ID or User ID. service component virtual machine. retcd File-transfer return code. date Date that the distribution service machine System Action: The NetView FTP component that started: year/month/day. issued the message ends. time Time that the distribution service machine started: hour:minute:second. mlevel Program maintenance-level information; maintained by your system administrator. System Action: Processing continues. User Action: None.

94 NetView FTP Messages and Codes DVG742I Ÿ DVG801I

DVG742I NETVIEW FTP release; DISTRIBUTION-SERVICE DVG763I ERROR RECEIVING INITIAL CONTROL BLOCKS COMPONENT userid ENDED ON date AT time; FROM DISTRIBUTION-SERVICE COMPONENT; RETURN CODE = retcd FILE TRANSFER TERMINATED

Explanation: A server stopped running. Explanation: An error occurred while a file service component virtual machine received the initial control release Release level of transfer program. blocks from its distribution service component virtual userid User ID or resource ID of the distribution machine. service component virtual machine. System Action: The file transfer is terminated. The date Date that the server distribution service status of the file-transfer request is changed to component virtual machine stopped: finished. year/month/day. User Action: Check that NetView FTP was time Time that the distribution service installed correctly. If the problem is not caused by component virtual machine stopped: your installation, contact your IBM Support Center. hours:minutes:seconds. retcd Distribution service component virtual DVG764I DISTRIBUTION-SERVICE COMPONENT userid machine return code. DID NOT ACCEPT COMMUNICATION PATH The return code shows whether any errors occurred while the distribution service component virtual Explanation: No communication path to the machine was stopping. distribution service virtual machine component virtual System Action: The distribution service component machine is established. virtual machine stops. userid User ID or resource ID of the distribution User Action: If the return code is 0, no action is service virtual machine to which a required. If the return code is not 0, refer to communication path tried to establish. Chapter 2, “NetView FTP ABEND, Return, and System Action: The file service component virtual Reason Codes” on page 109 to find out what it machine terminates. means. User Action: Check if the file DVGAS NAMES in your file service component virtual machine contains DVG761I NO CONNECTION FROM THE FILE-SERVICE the valid user ID or resource ID of the distribution COMPONENT RECEIVED; service component virtual machine that autologged FILE TRANSFER TERMINATED the file service component virtual machine.

Explanation: A subtask in the distribution service DVG800I CURRENTLY, NOT ENOUGH STORAGE IS component virtual machine, which had been attached AVAILABLE AT THE REMOTE SYSTEM to process a file transfer, had still not received a connect from the file service machine after 5 minutes. Explanation: This message is issued if the remote transfer program that processes your request cannot System Action: The status of the file-transfer acquire enough virtual storage to perform the file request is changed to waiting. transfer. User Action: Check that the file service machine System Action: The file transfer terminates. was autologged correctly and that the PROFILE EXEC is correct. User Action: Ask the system administrator at the remote system to correct the error, then resubmit your request. DVG762I DATA TRANSFERRED FROM THE DISTRIBUTION-SERVICE COMPONENT TO THE FILE-SERVICE COMPONENT WAS TRUNCATED DVG801I REMOTE TRANSFER PROGRAM IS NOT ABLE TO PROCESS YOUR REQUEST DUE TO A SYSTEM EXCEPTION Explanation: A remote transfer program sent a File Interchange Unit (FIU) that could not be handled by NetView FTP VM. The file service component virtual Explanation: This message is issued if the remote machine examines the data and then issues a transfer program that processes your request has a message explaining the error. system exception, for example, a bad return code from an operating system macro. System Action: The file transfer ends. System Action: The file transfer terminates. User Action: Contact your system administrator. User Action: Ask the system administrator at the remote system to correct the error, then resubmit your request.

Chapter 1. NetView FTP Messages 95 DVG802I Ÿ DVG809I

DVG802I THERE IS A STORAGE MEDIUM ERROR DVG806I THE PARAMETER WITH THE BATCH JOB KEYWORD keyword IS NOT SUPPORTED Explanation: While accessing a file the remote Or, for NetView FTP V2.2 MVS: file-transfer program that processes your request DVG806I THE PARAMETER parameter IS NOT encountered a storage medium error. SUPPORTED System Action: The file transfer terminates. Explanation: The remote transfer program User Action: Ask the system administrator at the recognized that you specified a parameter that it remote system to correct the error, then resubmit does not support. your request. keyword The batch job interface keyword. parameter The NetView FTP parameter. DVG803I YOU MUST SPECIFY THE PARAMETER WITH THE BATCH JOB KEYWORD keyword System Action: The file transfer terminates. Or, for NetView FTP V2.2 MVS: User Action: Correct the file-transfer request, then DVG803I YOU MUST SPECIFY THE PARAMETER resubmit your request. parameter

DVG807I YOU DID NOT SPECIFY A REQUIRED Explanation: The remote transfer program COMBINATION OF PARAMETERS recognized that you did not specify a required parameter in the file-transfer request. Explanation: The remote transfer program keyword The batch job interface keyword. recognized that a necessary combination of parameter The NetView FTP parameter. parameters were not specified in the file-transfer System Action: The file transfer terminates. request. User Action: Correct the file-transfer request, then This message is accompanied by the message resubmit your request. DVG840I that tells you the parameters to be specified.

DVG804I DO NOT SPECIFY THE PARAMETER WITH THE System Action: The file transfer terminates. BATCH JOB KEYWORD keyword User Action: Correct the file-transfer request, then Or, for NetView FTP V2.2 MVS: resubmit your request. DVG804I DO NOT SPECIFY THE PARAMETER parameter

DVG808I YOU SPECIFIED A COMBINATION OF Explanation: The remote transfer program PARAMETERS THAT IS NOT ALLOWED recognized that you specified a parameter that is not allowed in the file-transfer request. Explanation: The remote transfer program keyword The batch job interface keyword. recognized that a combination of parameters that is parameter The NetView FTP parameter. not allowed were specified in the file-transfer request. System Action: The file transfer terminates. This message is accompanied by the message DVG840I that tells you the parameters not to be User Action: Correct the file-transfer request, then specified together. resubmit your request. System Action: The file transfer terminates.

DVG805I YOU SPECIFIED PARAMETER parameter MORE User Action: Correct the file-transfer request, then THAN ONCE resubmit your request.

Explanation: The remote transfer program DVG809I YOU DID NOT SPECIFY PARAMETERS THAT recognized that you specified the parameter more NEED TO BE SPECIFIED than once, however, this parameter can only be specified once. Explanation: The remote transfer program parameter The corresponding batch job interface recognized that a combination of parameters are keyword or parameter name. missing in the file-transfer request. System Action: The file transfer terminates. This message is accompanied by the message DVG841I that tells you the corresponding batch job User Action: Correct the file-transfer request, then interface keywords and values that are missing. resubmit your request. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then resubmit your request.

96 NetView FTP Messages and Codes DVG810I Ÿ DVG815I

DVG810I YOU SPECIFIED PARAMETERS THAT ARE NOT DVG813I A VALUE FOR THE PARAMETER parameter ALLOWED IN THIS COMBINATION CONTAINS AN INCORRECT CHARACTER char (HEX hex) Explanation: The remote transfer program recognized that a combination of parameters were Explanation: The remote transfer program not allowed in the file-transfer request. recognized that a parameter value contained a character that is not allowed. This message is accompanied by the message DVG841I that tells you the corresponding batch job The characters that NetView FTP supports for this interface keywords and values that are not allowed. parameter depends on the parameter. System Action: The file transfer terminates. keyword The corresponding batch job interface keyword or parameter name (NetView User Action: Correct the file-transfer request, then FTP V2.2 MVS) resubmit your request. char The character that is not supported

DVG811I THE VALUE value FOR THE PARAMETER WITH hex The hexadecimal value of the character THE BATCH JOB KEYWORD keyword IS NOT char. SUPPORTED System Action: The file transfer terminates. Or, for NetView FTP V2.2 MVS: User Action: Correct the file-transfer request, then DVG811I THE VALUE value FOR THE PARAMETER resubmit your request. parameter IS NOT SUPPORTED

Explanation: The remote transfer program DVG814I THE VALUE value IS NOT IN THE RANGE OF recognized that a value has been specified that it ALLOWED VALUES FOR THE PARAMETER does not support. WITH THE BATCH JOB KEYWORD keyword; maximum IS THE MAXIMUM ALLOWED VALUE value Is the value of the parameter Or, for NetView FTP V2.2 MVS: keyword The batch job interface keyword DVG814I THE VALUE value IS NOT IN THE RANGE OF parameter The NetView FTP parameter. ALLOWED VALUES FOR THE PARAMETER parameter; System Action: The file transfer terminates. maximum IS THE MAXIMUM ALLOWED VALUE User Action: Correct the file-transfer request, then resubmit your request. Explanation: The remote transfer program recognized that a parameter contained a value that is not in the range of allowed values. DVG812I YOU SPECIFIED PARAMETER VALUES THAT ARE INCOMPATIBLE value Is the value of the parameter keyword The batch job interface keyword Explanation: The remote transfer program parameter The parameter name recognized that incompatible parameter values were specified. maximum Is the maximum value allowed. This message is accompanied by the message System Action: The file transfer terminates. DVG841I that tells you the corresponding batch job User Action: Correct the file-transfer request, then interface keywords and values that are incompatible. resubmit your request. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then DVG815I YOU ARE NOT ALLOWED TO SPECIFY THE resubmit your request. VALUE value FOR PARAMETER WITH THE BATCH JOB KEYWORD keyword Or, for NetView FTP V2.2 MVS: DVG815I YOU ARE NOT ALLOWED TO SPECIFY THE VALUE value FOR PARAMETER parameter

Explanation: The remote transfer program recognized that a value was specified for this parameter that is not valid. value Is the value of the parameter keyword The batch job interface keyword parameter The parameter name. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then resubmit your request.

Chapter 1. NetView FTP Messages 97 DVG816I Ÿ DVG824I

DVG816I FILE file-id ALREADY EXISTS DVG820I FILE file-id NOT FOUND

Explanation: The remote transfer program Explanation: The remote transfer program recognized that a file that was to be created already recognized that a file to be updated does not exist. exists. file-id Is the file ID of the file to be updated. file-id Is the file ID of the file to be created. System Action: The file transfer terminates. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then User Action: Correct the file-transfer request, then resubmit your request. resubmit your request.

DVG821I MEMBER member-name IN FILE file-id NOT DVG817I MEMBER member-name OF FILE file-id FOUND ALREADY EXISTS Explanation: The remote transfer program Explanation: The remote transfer program recognized that a member of a file to be updated recognized that a member of a file that was to be does not exists. created already exists. file-id Is the file ID of the file that should contain member-name the member. Name of the member in the file. member-name file-id Is the file ID that contains the member. Is the name of the member in the file. System Action: The file transfer terminates. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then User Action: Correct the file-transfer request, then resubmit your request. resubmit your request.

DVG818I RECORD record-key OF FILE file-id ALREADY DVG822I RECORD record-key IN FILE file-id NOT FOUND EXISTS Explanation: The remote transfer program Explanation: The remote transfer program recognized that the record to be updated does not recognized that a record to be added to a file already exist. exists. record-key file-id Is the file ID of the file to be updated. Is the record key of the record to be updated. record-key Is the record key that already exists. file-id Is the file ID of the file to be updated. System Action: The file transfer terminates. System Action: The file transfer terminates. User Action: Correct the file-transfer request, then User Action: Correct the file-transfer request, then resubmit your request. resubmit your request.

DVG819I VOLUME OR MINIDISK volume NOT FOUND DVG823I VOLUME OR MINIDISK volume IS FULL Or, for NetView FTP V2.2 MVS: DVG819I VOLUME, MINIDISK, OR PATH volume NOT Explanation: The remote transfer program FOUND recognized that a volume or minidisk is full. volume Is the name of the volume or minidisk. Explanation: The remote transfer program could not find the volume, minidisk, or path to read from or System Action: The file transfer terminates. write to. User Action: Correct the error and resubmit the Volume Is the volume, minidisk, or path that was request. not found. System Action: The file transfer terminates. DVG824I FILE file-id IS FULL User Action: Correct the file-transfer request, then resubmit your request. Explanation: The remote transfer program recognized that the file that it writes to is full. file-id Is the file ID of the file. System Action: The file transfer terminates. User Action: Correct the error and resubmit the request.

98 NetView FTP Messages and Codes DVG825I Ÿ DVG831I

DVG825I MEMBER member-name IN FILE file-id IS FULL DVG829I YOUR FILE TRANSFER WAS INTERRUPTED BY identifier Explanation: The remote transfer program recognized that a member of a file that it writes to is Explanation: The remote transfer program was full. interrupted. member-name identifier One of the following: Is the name of the member in the file. Ÿ The NetView FTP operator file-id Is the file ID of the file. Ÿ A user-exit routine The request originator System Action: The file transfer terminates. Ÿ Ÿ The NetView FTP administrator. User Action: Correct the error and resubmit the System Action: The file transfer terminates. request. User Action: None.

DVG826I FILE file-id IS IN USE DVG830I FUNCTION function-code NOT SUPPORTED Explanation: The remote transfer program Or, for NetView FTP V2.2 MVS: recognized that a file that it reads from or writes to is DVG830I function NOT SUPPORTED in use. Explanation: The remote transfer program does not file-id Is the file ID of the file. support a required function. System Action: The file transfer terminates. NetView FTP other than NetView FTP V2.2 MVS: User Action: Ensure that the file is not in use then function-code Where the function not supported is resubmit the request. represented by: 01 Data-set organization DVG827I THE REMOTE FILE TRANSFER PROGRAM IS 02 User exits. NOT AUTHORIZED TO ACCESS THE FILE AT THE REMOTE SYSTEM NetView FTP V2.2 MVS: function can be one of the following: Explanation: The remote transfer program Ÿ Data-set organization recognized that it cannot access a file it was to read Ÿ User exits. from or write to. This can happen if the user ID specified in the request is not authorized to access System Action: The file transfer terminates. the file. User Action: None. System Action: The file transfer terminates.

User Action: Correct the access security DVG831I FUNCTION function-code NOT ACTIVE parameters in your file-transfer request, then Or, for NetView FTP V2.2 MVS: resubmit the request. DVG831I function NOT ACTIVE

DVG828I YOUR FILE TRANSFER FAILED TO RESTART Explanation: The remote transfer program cannot perform a required function because it is not active. NetView FTP other than NetView FTP V2.2 MVS: Explanation: The remote transfer program detected an error during restart. function-code Where the function not active is represented by: System Action: The file transfer terminates. 01 User exits User Action: 02 Encryption support NetView FTP V2.2 MVS: 03 SMS support. Check the value of the File Status NetView FTP V2.2 MVS: Option and resubmit the request. function can be one of the following: NetView FTP other than NetView FTP V2.2 MVS: Change the value of the Restart from Ÿ User exits Checkpoint parameter to NO and Ÿ Encryption support resubmit the request. The file transfer is Ÿ SMS support. restarted from the beginning. System Action: The file transfer terminates. User Action: Ask the operator at the remote location to activate the function.

Chapter 1. NetView FTP Messages 99 DVG832I Ÿ DVG842I

User Action: Check the log and report information DVG832I FUNCTION function-code NOT OPERATIONAL of the partner server that was involved in this Or, for NetView FTP V2.2 MVS: transfer, especially for messages in the range from DVG832I function NOT OPERATIONAL DVG803 to DVG815. If both sides show message DVG839I and do not contain further information identifying certain file-transfer parameters that should Explanation: The remote transfer program cannot be specified or omitted, contact your IBM Support perform a required function because it is not Center. operational. NetView FTP other than NetView FTP V2.2 MVS: DVG840I PARAMETER = keyword function-code Where the function not operational is represented by: Explanation: This message informs you about a 02 Encryption support. parameter in error with the corresponding batch job NetView FTP V2.2 MVS: keyword. function is encryption support. keyword Batch job keyword. System Action: The file transfer terminates System Action: See the messages that accompany because an error occurred while invoking the this message. function. User Action: See the messages that accompany User Action: None. this message.

DVG833I ERROR CODE RETURNED BY comp, DVG841I PARAMETER = keyword; VALUE = value CODE VALUE = value. Explanation: This message informs you about the Explanation: The remote transfer program cannot parameter and value in error with the corresponding process your request due to a system exception. batch job keyword. comp Component where the error occurred. It keyword Batch job keyword. can be one of the following: System Action: See the messages that accompany C Runtime this message. NetBIOS OS2 User Action: See the messages that accompany value System code number. this message. System Action: The file transfer terminates. User Action: Ask the system administrator at the DVG842I NAME = protocol-name; ID = protocol-id; LENGTH remote system to correct the error, then resubmit = length; VALUE = value your request. Explanation: This message is for diagnosis purposes only. It is issued when a log of the DVG834I PARAMETER parameter IS NOT SUPPORTED protocol message units is requested or when a BY THE PARTNER SYSTEM protocol violation is detected. If a protocol log is requested, all items of received Explanation: You specified a parameter that is not protocol message units are logged. If a protocol supported by the partner system. violation occurred, all items of the protocol error System Action: The transfer ends and NetView message unit are logged. FTP changes the status of the request to finished. protocol-name The name of the protocol item. User Action: Correct the file-transfer request, then protocol-id The hexadecimal identifier of the resubmit your request. protocol item. length The length of the value of the DVG839I A PROTOCOL VIOLATION OCCURRED protocol item. value The value of the protocol item. If Explanation: The transfer program has detected a the length is zero, nothing is situation that violates the transfer protocol. The printed. Otherwise, the value up transfer reason code shows whether the local or the to a maximum of 100 characters remote transfer program detected the violation. If the is printed, even if the protocol partner system is on a higher NetView FTP level, the item contains more data. violation most likely is caused by a new function that System Action: If a protocol violation occurred, the is not supported by the local system. file transfer terminates. If a protocol log is written, System Action: The file transfer terminates. processing continues. User Action: None.

100 NetView FTP Messages and Codes DVG843I Ÿ DVG904I

DVG843I FILE TRANSFER REQUEST NOT ACCEPTED. DVG850I ERROR MESSAGE RECEIVED FROM REMOTE FILE-TRANSFER PROGRAM: message text Explanation: The file-transfer request is not accepted by the remote transfer partner. If it is a Explanation: This message informs you about temporary problem (reason code 567), probably the errors when the remote transfer program processes transfer limit is exceeded. If it is a permanent your request. problem (reason code 568), probably the APPC message text Conversation Security parameters are missing in Is the message text as created by the your file-transfer request. remote transfer program. System Action: The file transfer does not start and System Action: The file transfer terminates. NetView FTP changes the status of the request to waiting if it is a temporary problem, and to finished User Action: See the message text created by the if it is a permanent problem. remote file-transfer program. User Action: For a temporary error, none. For a permanent error, correct the error and resubmit the DVG903I MODULE modulename; request. FUNCTION function ENTERED; TRACE ACTIVE

DVG844I FILE TRANSFER REQUEST NOT ACCEPTED, Explanation: This message is issued when the RESPONDING WORKSTATION NOT ACTIVE. trace function was activated. modulename Explanation: The file-transfer request is not The name of the module for which the accepted because the responder at the remote trace mask was set. system is not active. function The name of the function that was set. System Action: The file transfer does not start and System Action: Trace output is written, processing NetView FTP changes the status of the request to continues. waiting. User Action: None. User Action: Have the responder started.

DVG904I MODULE modulename; DVG845I FILE NAME DOES NOT CORRESPOND TO THE FUNCTION function EXITED; TRACE ACTIVE; NAMING RULES AT THE RECEIVING SYSTEM. ERROR CODE = error-code

Explanation: You used a file name that does not Explanation: This message is issued when the adhere to the naming rules of the receiving system. trace function was activated. System Action: The file transfer ends and NetView modulename FTP changes the status of the request to finished. The name of the module for which the User Action: Specify a file name that meets the trace mask was set. rules of the receiving system and resubmit the function The name of the trace function that was file-transfer request. set. error-code One of the following: DVG846I ACCESS VIOLATION, FILE IS READ-ONLY. 0 No error 1 Processing continues Explanation: You tried to write to a file that is 2 Request in progress read-only. 3 Request not available 4 Request terminated System Action: The file-transfer ends and NetView 5 System abort reported from FTP changes the status of the request to finished. OSI/File Services User Action: Either use another receiving file or 6 Request completed change the access authority of the file. 8 OSI server function reported general error 10 Access to other filestore missing 11 Access to own filestore missing 12 OSI server function reported severe error 13 Temporary error in OSI/File Services 14 Condition code not found 20 Server terminating

Chapter 1. NetView FTP Messages 101 DVG907I Ÿ DVG913I

21 Request will be skipped This message is issued whenever an OSI server is 23 File entry not registered in started. server filestore, temporary nnn Number of requests to be recovered. entry will be made 24 File entry does not exist System Action: Processing continues. 25 Temporary error in queue User Action: None. handler NONE Specific error code not defined. DVG910I REQUEST reqnum CANNOT BE RECOVERED System Action: Trace output is written, processing AND IS CANCELED continues. User Action: None. Explanation: The request reqnum is marked as uncompleted in the recovery file. The request cannot DVG907I OSI/FS PASSWORD FOR OSI SERVER be finished successfully by the OSI server and is servername IS INVALID therefore canceled. reqnum Name of the request not finished Explanation: The OSI server tried to log on to successfully. OSI/FS. However, the password specified with the System Action: The request is not submitted. OIUSRPWD keyword of the OSI server initialization Processing continues. control statement was not accepted by OSI/FS. The User Action: Resubmit the request. initialization of the OSI server is unsuccessful. servername The job name or STC name under which DVG911I RECOVERY COMPLETED the server was started. System Action: The OSI server terminates. Explanation: All requests stored in the recovery file after an abnormal OSI server termination were User Action: Specify the correct password and completed. restart the OSI server. System Action: Processing continues. User Action: None. DVG908I OSI/FS PASSWORD FOR OSI SERVER servername CHANGED DVG912I USERID userid NOT REGISTERED IN LRD Explanation: The password to log on to OSI/FS has been successfully changed. The new password Explanation: This message is issued if the was specified with the OINUSRPW keyword of the specified user ID is not registered in the local OSI server initialization statement. resource directory. servername userid Name of the incorrect user ID. The job name or STC name under which the server was started. System Action: The request is rejected. System Action: Processing continues. User Action: Specify the correct user ID or get the OSI/File Services administrator to enter it in the local User Action: None. resource directory, and then resubmit the request.

DVG909I RECOVERY FILE READ nnn REQUESTS TO DVG913I ERROR DURING OSI SERVER servername RECOVER INITIALIZATION PHASE

Explanation: This message indicates the number of Explanation: The server is terminating due to an requests to be recovered following termination of the error during the initialization of the OSI server. This OSI server. message is usually preceded by a message When the OSI server terminates due to an error in describing the failure. the queue handler or if OSI/File Services is servername terminated (using the immediate command) by the The job name or STC name under which operator, the recovery file is written. The recovery the server was started. file is read and the number of requests to be recovered is specified by the value nnn. Information System Action: The OSI server is not started. to complete the unfinished request is passed to the User Action: Check the log file for messages that OSI server before it terminates and is kept in the might help you to analyze the problem. After you recovery file. have corrected the problem, restart the server.

102 NetView FTP Messages and Codes DVG914I Ÿ DVG921I

servername DVG914I ACF/LRD SPACE PROBLEMS;RETURN CODE = The job name or STC name under which rc, CONDITION CODE = cc. the server was started. retcd Return code. Explanation: OSI/FS detected space problems on condcd Condition code. Refer to OSI/File the Access Control File or in the Local Resource Services for MVS User’s Guide for an Directory. explanation of the condition codes. rc Return code. System Action: The command is rejected and the cc Condition code. Refer to OSI/File OSI server terminates. Services System /370 User’s Guide for an explanation of the condition codes. User Action: Contact your system administrator. System Action: Depending on the return code, NetView FTP changes the status of the request to DVG921I OSI/FS COMMAND cmd ISSUED BY OSI waiting or to finished. SERVER servername FOR REQUEST reqnum User Action: Delete ACF/LRD entries and resubmit FAILED; the request. RETURN CODE = retcd; CONDITION CODE = condcd

DVG919I UNKNOWN ERROR FROM OSI/FS; Explanation: The OSI server issued a command to FUNCTION func SERVER servername; address the OSI/File Services component for the RETURN CODE = retcd; specified request. The command could not be CONDITION CODE = condcd processed successfully. cmd One of the following: Explanation: OSI/File Services has returned a condition code that cannot be handled by the OSI COPY Copy a file server. It may indicate that a new release of MOVE Move a file OSI/File Services contains new condition codes, and LENT List entry of local resource the current release of the OSI server is not directory compatible with this release of OSI/File Services. LFIR List first entry of local resource directory func Function in which the error occurred. AENT Add entry to local resource servername directory The job name or STC name under which RENT Remove entry from local the server was started. resource directory GTRS Get result retcd Return code. CANC Cancel request. condcd Condition code. Refer to OSI/File servername Services for MVS User’s Guide for an The job name or STC name under which explanation of the condition codes. the server was started. System Action: Depending on the return code, retcd Return code. NetView FTP changes the status of the request to waiting or to finished, or the server terminates. condcd Condition code. Refer to OSI/File Services for MVS User’s Guide for an User Action: Contact your system administrator. explanation of the condition codes. System Action: The command and the request are DVG920I OSI/FS COMMAND cmd ISSUED BY OSI rejected. SERVER servername FAILED; RETURN CODE = User Action: Check the request parameters and retcd; CONDITION CODE = condcd resubmit the request.

Explanation: The OSI server issued a command to address the OSI/File Services component. This command was not successful. cmd One of the following: STR Start of OSI/File Services END Termination of OSI/File Services LENT List entry of local resource directory LFIR List first entry of local resource directory CUPW Change user password.

Chapter 1. NetView FTP Messages 103 DVG922I Ÿ DVG926I

DVG922I REQUEST reqnum TERMINATED DUE TO USER DVG925I OSI SERVER TERMINATING DUE TO AN ERROR; INTERNAL ERROR OF OSI SERVER RETURN CODE = retcd; servername; SIGNAL signal ISSUED CONDITION CODE = condcd Explanation: An OSI server issues this message Explanation: This message is issued when you when an internal server error occurs that causes the submit a request with incorrect parameters, or OSI server to terminate. Normally, this message is insufficient local resource directory entries. preceded by a message describing the failure. reqnum Number of the request. servername The job name or STC name under which retcd Return code. the server was started. condcd Condition code. Refer to OSI/File signal The OSI server containing C programs Services for MVS User’s Guide for an uses the following C/370* supported explanation of the condition codes. signals to handle error conditions: System Action: The request is not submitted. SIGABRT Abnormal termination signal Processing continues. sent by the abend function. User Action: Correct the error and resubmit the SIGFPE Erroneous arithmetic request. exceptions, such as overflow, division by zero, or operation not valid. DVG923I OSI SERVER TERMINATING DUE TO AN SIGILL Function image not valid, ERROR IN OSI/FS such as an object module or operation exception that is not Explanation: This message is issued when the OSI valid. server is terminating due to a severe error in the SIGINT Interactive attention interrupt. OSI/File Services component. Possible reasons may SIGSEGV Access to memory not valid, be: such as protection exception Ÿ OSI/File Services not yet started or addressing exception that Ÿ Lost connection to OSI/File Services is not valid. Ÿ Internal error in OSI/File Services SIGTERM Termination request sent to Ÿ Unexpected shutdown of OSI/File Services. program. Normally, this message is preceded by a message System Action: The OSI server terminates. describing the failure. User Action: A detailed description of the C/370 System Action: The OSI server terminates. signals is provided in the C/370 User’s Guide. User Action: Check the log file for messages that Check the log file for messages that might help you might help you to analyze the problem. After you to analyze the problem. The signal issued might have corrected the problem, restart the server. also provide a clue. After you have corrected the problem, restart the server.

DVG924I USER userid CANNOT CARRY OUT FILE TRANSFER FOR REQUEST reqnum DUE TO DVG926I OSI SERVER TERMINATING DUE TO AN MISMATCH BETWEEN LRD ENTRIES AND UNEXPECTED ERROR REQUEST PARAMETERS Explanation: An OSI server issues this message Explanation: The OSI/File Services server issues when an unexpected error occurred and the OSI this message when it detects a mismatch between server is terminating. Normally, this message is the specifications in the local resource directory and preceded by a message describing the error. the request. System Action: The OSI server terminates. userid User ID that requested the file transfer. User Action: Check the log file for messages that reqnum Number of the file-transfer request. might help you to analyze the problem. After you have corrected the problem, restart the server. System Action: The request is not submitted. Processing continues. User Action: Change the access authority as described in OSI/File Services User’s Guide and resubmit the request.

104 NetView FTP Messages and Codes DVG927I Ÿ DVG990I

DVG927I REQUEST reqnum TERMINATED DUE TO AN DVG931I REQUEST reqnum CANCELED UNEXPECTED ERROR Explanation: The OSI server issues this message Explanation: An unexpected error occurred when a request is canceled. processing the request reqnum. Normally, this reqnum Number of the request that was canceled. message is preceded by a message describing the error. System Action: The request is terminated. Processing continues. reqnum Number of the request submitted. User Action: None. System Action: The request is rejected and the OSI server terminates. User Action: Check the log file for messages that DVG941I CLOSE ON ddname FAILED may help you to analyze the problem. After you have corrected the problem, restart the OSI server Explanation: The OSI server issues this message and resubmit the request. when an internal file cannot be closed. ddname Name of the internal file that could not be DVG928I FUNCTION function RETURNED WITH SEVERE closed. ERROR System Action: The OSI server terminates. User Action: Contact your system administrator. Explanation: This message displays the internal sequence of server functions after an error occurred. Normally this message is preceded by a message DVG942I UNEXPECTED COMPLETION CODE FOR ECB describing the failure. ecb function Name of the function in which the error occurred. Explanation: This message is issued when the OSI server is posted with an event control block but System Action: The OSI server terminates. cannot handle the completion code. It may indicate User Action: Check the log file for messages that inconsistencies between the current versions of the may help you to analyze the problem. After you queue handler and the OSI server. have corrected the problem, restart the OSI server ecb Event control block. and resubmit the request. System Action: The OSI server terminates. User Action: Contact your system administrator. DVG929I OSI/FS COMMAND cmd RETURNED RETURN CODE = retcd; CONDITION CODE = condcd DVG950I REQUEST reqnum WAS NOT AN OSI REQUEST

Explanation: This message is for information only. Explanation: The request is not an OSI request. The return and condition codes are kept in the log file for information. reqnum Number of the request. cmd Name of the OSI/File Services command. System Action: The request is not submitted. retcd Return code. User Action: Check the request class. It must not be a class assigned to an OSI server if an SNA-type condcd Condition code. Refer to OSI/File request is to be submitted. Correct the error and Services for MVS User’s Guide for an resubmit the request. explanation of the condition codes. System Action: Processing continues. DVG990I CLASS/PRIORITY = cl/pr; User Action: None. OSI SERVER NAME = servername; INITIATOR FUNCTION = func; TRANSFER MODE = tranmode; DVG930I REQUEST reqnum TERMINATED DESTINATION EFFECT = destneff

Explanation: The OSI server issues this message Explanation: This message gives information about when a request terminates. the request and the transfer. reqnum Number of the request that finished. cl/pr Server class and request priority of the System Action: The request is terminated. request. User Action: Check the log file for messages that servername may help you analyze the problem. After you have Name of the OSI server. corrected the error, resubmit the request. func Function COPY or MOVE. tranmode Transfer mode, T = To or F = From.

Chapter 1. NetView FTP Messages 105 DVG991I Ÿ DVG993I

destneff Destination effect on the destination file; C System Action: Processing continues. (create), A (append), R (replace), CA User Action: None. (create or append), or CR (create or replace). System Action: Processing continues. DVG993I DOCUMENT TYPE = doctype; UNIVERSAL CLASS = univcl; User Action: None. STRING SIGNIFICANCE = strsig; MAXIMUM STRING LENGTH = maxstrln; FUTURE FILE SIZE = futflsiz DVG991I FILESTORE OWNER = locusid; FILESTORE NICKNAME = fsnn; FILESTORE SUBSET = fssub; Explanation: This message gives information about LOCAL FILE NAME = locflnam the destination file. doctype FTAM document-type of the file. Possible Explanation: This message gives information about values are: the file at the local system. F1 Defined as unstructured text locusid User ID of the filestore owner. F3 Defined as unstructured binary. fsnn Filestore nickname. univcl The universal class parameter is an OSI term that refers to the type of character fssub Filestore subset. string of which the contents of the loclnam Local file name. destination file are composed. Possible System Action: Processing continues. values are: User Action: None. G GeneralString H GraphicString I Ia5String DVG992I LOCAL OSI FILE NAME = locosifn; V VisibleString. LOCAL ACCESS PASSWORDS = locaccpw; For further details see the FTAM REMOTE FILESTORE AET = remfsaet; standards. REMOTE OSI FILE NAME = rosifn; REMOTE ACCESS PASSWORDS = remaccpw strsig The string significance is the record format of the destination file. Possible values are: Explanation: This message gives information about local and remote parameters. F Fixed format. The string length is equal to the maximum string length locosifn Local OSI file name. specified. The file is stored with locaccpw List of YES or NO values (for example, this record format. YYNNNY) indicating how the following U Unbounded format (not significant). passwords are set on the local system: The file may be stored with any Ÿ Read record format. Ÿ Extend V Variable format. The string length Ÿ Replace is equal to, or less than the Ÿ Read attributes maximum string length specified. Ÿ Delete file The file is stored with this record Ÿ Filestore format. Ÿ Create. maxstrln The maximum string length is the logical remfsaet Remote filestore application entity title by record length of the destination file and which the filestore can be identified by must be specified. users at the remote system. futflsiz The future file size is the maximum size, rosifn Remote OSI file name. This is the name expressed in K bytes, to which the file is by which the file can be identified and expected to grow as a result of its future accessed by users at the local and handling. remote system. System Action: Processing continues. remaccpw List of YES or NO values (for example, User Action: None. YYNNNY) indicating how the following passwords are set on the remote system: Ÿ Read Ÿ Extend Ÿ Replace Ÿ Read attributes Ÿ Delete file Ÿ Filestore Ÿ Create.

106 NetView FTP Messages and Codes DVG994I Ÿ DVG996I

DVG994I FILE AVAILABILITY = favail; DVG995I FUNCTION RETURN CODE = funcrc; PERMITTED ACTIONS = permact; FUNCTION CONDITION CODE = funccc; ACCESS CONTROL ELEMENT ACTIONS = REQUEST START = reqstr; aceact; ACTIVITY STATUS = actstat; ACCESS CONTROL ELEMENT PASSWORDS = TRANSFERRED BYTES = bytes acepwds Explanation: This message gives information about Explanation: This message gives information about the function output. the destination file. funcrc Specifies the final return code of the favail Indicates whether or not the file is to be initiator function (COPY or MOVE) related available immediately to users once it is to the transfer request. created on their system. Possible values funccc Specifies the final condition code of the are: initiator function (COPY or MOVE) related I Immediate availability to the transfer request. D Deferred availability. reqstr Date and time the request started. permact Permitted actions is a list of the actions actstat The current status of the transfer request. allowed on the file. Each action can have Possible values are: the value Y = YES, or N = NO, for example, YYYNNY. Possible actions are: INPR The transfer is still in progress. Ÿ Read COMP The transfer is complete. Ÿ Extend ABCO The transfer terminates due to Ÿ Replace an ABORT function request Ÿ Read attributes issued by the console operator. Ÿ Change attributes ABFO The transfer terminates due to a Ÿ Delete file. CANCEL function request issued aceact Access control element actions is the list by the owner of the filestore. of the actions allowed by the access ABIU The transfer terminates due to a control element. Each action can have CANCEL function request issued the value Y = YES, or N = NO, for by the request issuer. example, YYYNNY. Possible actions are: ABSY The transfer terminates due to Ÿ Read the program terminating. Ÿ Extend Ÿ Replace bytes The number of bytes transferred during Ÿ Read attributes the transfer. Change attributes Ÿ System Action: Processing continues. Ÿ Delete file. User Action: None. acepwds Access control element passwords is the list of the passwords related to the actions defined in the access control element DVG996I DIAGNOSTIC: ORIGIN = diagor; actions. Each action can have the value TYPE = diagtyp; Y = YES, or N = NO to indicate whether ERROR IDENTIFIER = diagiden; or not a password is assigned, for SUGGESTED DELAY = diagdel; example, YYYNNY. Possible passwords MESSAGE = diaginfo are: Ÿ Read Explanation: This message gives diagnostic Ÿ Extend information that is optionally provided by the remote Ÿ Replace system. Ÿ Read attributes diagor Diagnostic origin specifies whether the Ÿ Change attributes error was detected by the local system or Ÿ Delete file. by the remote system. Possible values System Action: Processing continues. are: User Action: None. L Locally detected R Remote detected N No categorization possible. diagtyp Diagnostic error type specifies the severity of the error. Possible values are: I Informative message T Transient error P Permanent error.

Chapter 1. NetView FTP Messages 107

diagiden Diagnostic error identifier is a classification of the errors. It is an integer

field that takes one of the values defined in ISO FTAM-IS-Standard Part 3. diagdel Diagnostic suggested delay is an integer value specifying how many minutes the user should wait before restarting the

transfer request. It is meaningful for transient errors only. diaginfo Diagnostic error information is a message in natural language giving further details about the cause of the error. System Action: Processing continues. User Action: None.

108 NetView FTP Messages and Codes

Chapter 2. NetView FTP ABEND, Return, and Reason Codes

This chapter lists and describes the NetView FTP ABEND, return, and reason codes. Note: All return and reason codes in the messages are given in decimal.

NetView FTP ABEND Codes The following ABEND codes are issued by a NetView FTP component when it requests abnormal termination.

Figure 1. NetView FTP ABEND Codes ABEND Code Description Dec Hex 16 10 Wrong library concatenated for DVGMCQI. 17 11 Wrong SVC number specified during link of DVGMCQI. 32 20 NetView FTP request for virtual storage failed. 48 30 A program error occurred during user exit processing. 64 40 A program error occurred during NetView FTP processing. 80 50 An irrecoverable error occurred during request queue initialization.

NetView FTP Return Codes Figure 2 lists the return codes issued by the: Ÿ Queue handler Ÿ Queue handler command Ÿ Server Ÿ Batch job interface Ÿ Interactive interface Ÿ File transfer Ÿ OSI server Ÿ OSI/File Services.

Figure 2 (Part 1 of 2). NetView FTP Return Codes Return Code Description Dec Hex 0 0 One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, the file transfer completed successfully. Ÿ If the function was the termination of the queue handler or a server, the component terminated successfully. Ÿ If the function was a queue handler command, the command was carried out successfully. 1 1 A server running in single mode was stopped by the operator or its termination time expired. A file transfer was never started. 2 2 A server running in single mode was stopped by the operator immediately. A file transfer was in progress. 4 4 One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, the file transfer was carried out successfully but a noncritical error occurred. The error does not affect the security or integrity of the data transferred. Ÿ If the function was a queue handler command, the function was performed but not completed. For example, a QUERY command could not receive all data because of buffer shortage. Ÿ If the function was the termination of the queue handler or a server, the component terminated successfully but a noncritical error occurred. The error does not affect the security or integrity of the data transferred.

 Copyright IBM Corp. 1988, 1994 109

Figure 2 (Part 2 of 2). NetView FTP Return Codes Return Code Description Dec Hex 8 8 One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, the file transfer completed successfully but an error occurred during termination processing. Ÿ If the function was the termination of the queue handler or a server, the component terminated successfully but an error occurred during termination processing. 12 C For one of the following reasons, depending on the function being carried out, processing failed after the initialization phase was successfully completed: Ÿ If the function was a file transfer, the file transfer failed. Ÿ If the function was the normal processing of the queue handler or a server, the component terminated due to an error. 16 10 One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, an error occurred during the initialization of the file transfer. Ÿ If the function was the termination of the queue handler or a server, an error occurred during the component’s initialization. Ÿ If the NetView FTP partition was just started an error occurred during initialization of the NetView FTP partition. 20 14 One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, a program error occurred during the file transfer. Ÿ If the function was the normal processing of a server, the server terminated due to an error. Ÿ A program error occurred during the processing of a NetView FTP partition task. 24 18 A queue handler command error was detected by an interface routine. 28 1C A queue handler command error was detected by the common interface control routine. 32 20 The pre-queuing user-exit routine rejected a queue handler command and issued a reason code. 36 24 A queue handler command error was detected by the SVC routine. 40 28 A queue handler command error was detected by the queue handler. 44 2C An application program passed a queue handler command with an incorrect parameter list to the application program interface routine. 48 30 While carrying out a queue handler command, the batch job interface routine could not find the message definition module. 54 36 This return code is issued by an OSI server. The component terminated successfully but a noncritical error occurred. The error does not affect the security or integrity of the request just processed. 58 3A One of the following occurred, depending on the function being carried out: Ÿ If the function was a file transfer, an error occurred during the request preparation in the OSI server. The request is not passed on to OSI/File Services. Ÿ If the error occurred during the initialization of the component, the OSI server terminates. 74* 4A This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return code passed to the OSI server is 4, indicating a warning. 78* 4E This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return code passed to the OSI server is 8, indicating an error. The request passed to OSI/File Services is rejected due to external conditions. 82* 52 This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return code passed to the OSI server is 12, indicating an error. The request passed to OSI/File Services is rejected because it was incorrect. 86* 56 This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return code passed to the OSI server is 16, indicating a severe error. The request passed to OSI/File Services is rejected because an internal program malfunction is detected. 90* 5A This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return code passed to the OSI server is 20, indicating a catastrophic error. The request passed to OSI/File Services is rejected.

110 NetView FTP Messages and Codes

Note: For the return codes marked with an asterisk, the decimal value of 70 is added to the original function return code value passed from OSI/File Services. An OSI/File Services function condition code accompanies the function return code, and is passed to the OSI server, where it serves as a reason code. For interpretation of the original OSI/File Services function return codes and function condition codes, see OSI/File Services for MVS User’s Guide.

NetView FTP Single Server Return Codes:

Return codes for the termination of servers in single running mode are calculated as follows: (file-transfer return code x 1ðð) + server termination mode server termination mode 0 Server terminated normally, that is, after one session. 1 Server terminated without having established a session. 2 Server terminated while a session was active.

Figure 3. NetView FTP Return Codes from the Interactive Interface Return Description User Actions Code 24 An error occurred during execution of a GETMAIN macro. Check the size of the available region. Not enough space is available to run the program. 28 The ISPF environment is not established. The module Check the library containing ISPLINK. ISPLINK could not be loaded. 32 NetView FTP is unable to load and display panels from the Check the following: panel library. This may be due to one or more of the Ÿ The correct panel library is allocated. following: Ÿ The correct parameter is specified when the The interactive interface was invoked with an incorrect Ÿ interactive interface was invoked. One parameter with language parameter. a length of one character is allowed. This character Ÿ Panel and message libraries are not allocated. specifies the language to be used. Ÿ The panel library is incorrect. Make sure the last Example: If you invoked the interactive interface with the character of the member name is the national parameter F, the first panel you normally see has the language support character. panel ID DVGME00F, where the last character (F) is the language character. The members in the message library Ÿ The message library is incorrect. Make sure the fifth must have the name DVGMFxx. character of the member name is the national language support character. 36 The saved request table could not be closed. Refer to ISPF Dialog Management Services and Examples for actions to be taken.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 111

NetView FTP Reason Codes In NetView FTP the reason codes are issued either from the NetView FTP Partition (VSE), or from file transfers (with return codes 0 to 20), or from queue handler commands (with return codes 0, and 20 to 48).

Figure 4 (Part 1 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 0 0 The file transfer completed successfully. 4 4 Label: RSSTAERR Label: RSNREQM Description: Description: Request accepted but modified by pre-queuing user-exit routine. Temporary allocation error or temporary rejection. The queue handler successfully added the file-transfer One of the following occurred: request to the request queue. This reason code is to Ÿ The server tried to dynamically allocate a data set let the user know that the pre-queuing user-exit routine but the attempt failed because of an allocation changed one or more parameters in the file-transfer error: request before it was added to the request queue. This – The data set was probably being used by reason code usually accompanies the return code 0. another program. – For NetView FTP VSE, the system lock table or system lock file may be too small. Ÿ The pre-transfer user-exit routine temporarily rejected the file-transfer request. The pre-transfer user-exit routine might have passed a message to NetView FTP that explains why the request was rejected. Whether the server changed the status of the corresponding request to waiting or finished depends on the value of the Automatic Transfer Restart parameter. 8 8 Label: RSSPAERR Label: RSNNOFBA Description: Permanent allocation error. Description: No address or length provided for the QRA, QRA too small, or no QSR (Query Status Record) The server tried to dynamically allocate a data set, but provided. the attempt failed because of an allocation error. Probably the parameters of the file-transfer request An application program queried one or more were incorrect. The server changed the status of the file-transfer requests, but did not provide the address or corresponding request to finished, regardless of the the length of the query response area (QRA). The value of the Automatic Transfer Restart parameter. The QRA is the area into which NetView FTP is to write the request is not reprocessed later. information it retrieves. This reason code is also issued if the area provided is too small to contain the status information for at least one file-transfer request. 12 C Label: RSSOPNSE Label: RSNVBCER Description: Error in OPNSEC macro. Description: Incorrect queue handler command. The attempt to establish the ACF/VTAM session One of the following occurred: initiated by a remote server failed with an error in the Ÿ An application program specified an incorrect value OPNSEC macro. for the APLVBC field. Ÿ A batch job specified an incorrect value for the Function parameter. 16 10 Label: RSSVERR Description: Global ACF/VTAM error. The server tried to start an ACF/VTAM session for a file transfer but the attempt failed with an ACF/VTAM error. The ACF/VTAM error was not necessarily caused by the session being established.

112 NetView FTP Messages and Codes

Figure 4 (Part 2 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 20 14 Label: RSSMIKWD Label: RSNMIKWD Description: Mandatory parameter missing. Description: Mandatory parameters missing. The server checked the parameters in the file-transfer The user interfaces checked the file-transfer request request and found that a mandatory parameter was and found that one or more mandatory parameters missing from it. The pre-transfer user-exit routine might were missing from it. The file-transfer request was have changed the file-transfer request and omitted a rejected, that is, it was not added to the request queue. mandatory parameter. 24 18 Label: RSSNAVAI Label: RSNCSERR Description: Remote server temporarily not available. Description: Parameter error. The local server tried to initiate an ACF/VTAM session The user interfaces checked the file-transfer request but the attempt failed because a remote server was and found either a syntactical error or an inappropriate temporarily not available. Common reasons for this are: value. The file-transfer request was rejected, that is, it was not added to the request queue. Ÿ The remote servers were terminating Ÿ No remote servers were started Ÿ All the remote servers were already busy with other file transfers. The server changed the status of the corresponding request back to waiting, regardless of the value of the Automatic Transfer Restart parameter. A server will reprocess the request later. 28 1C Label: RSSUNUS Label: RSNNOCS Description: LU names for remote servers unusable. Description: No parameters found. The local server tried to initiate an ACF/VTAM session. No parameters were specified in the file-transfer The attempt failed because ACF/VTAM replied that the request. The file-transfer request was rejected, that is, LU names used to identify the remote node were it was not added to the request queue. unusable. Probably the LU names were not properly defined in ACF/VTAM. 32 20 Label: RSSQHERR Label: RSNOPERR Description: Queue handler error. Description: Error when opening SYSIN. The server tried to issue a queue handler command to When the batch job interface routine tried to open get or update a file-transfer request. The attempt failed SYSIN, the attempt failed. Probably the appropriate DD because the queue handler signalled that an error statement was missing from the startup job for the occurred. The error is not necessarily related to the batch job interface routine. queue handler command that the server issued. 36 24 Label: RSSREST Label: RSNIOERR Description: Not enough storage to restart transfer of Description: I/O error when reading from SYSIN. PDS. An I/O error occurred when the batch job interface The server tried to restart the transfer of a PDS from a routine tried to read from SYSIN. checkpoint. It found the checkpoint record in the checkpoint data set, but there was not enough storage available to restart the file transfer. Its attempt to use it to restart the transfer failed. 37 25 Label: RSSPOREC Label: RSNAPLE1 Description: Session recovery for a PDS member Description: Incorrect APL control block ID (APLID) failed. specified. Must be '*DVGAPL*' (APLACCR). A server tried to recover a session during which a PDS member was being transferred. The server retrieved, from the checkpoint data set, the number of the record with which it was to continue the transfer. While searching through the member for that record, end of member (EOM) was reached and the record was never found.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 113

Figure 4 (Part 3 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 38 26 Label: RSSPORST Label: RSNAPLE2 Description: Transfer restart for a PDS member failed. Description: Incorrect APL length specified in field APLLNGTH. Must be one of the values defined in the A server tried to restart the transfer of a PDS member. APL length fields in macro DVGAPL. The server retrieved, from the checkpoint data set, the number of the record with which it was to continue the transfer. While searching through the member for that record, end of member (EOM) was reached and the record was never found. 40 28 Label: RSSRRDS Description: VSAM Cluster type not supported. The server opened a VSAM data set for a file transfer. This data set turned out to have a record organization that is not supported by NetView FTP. 44 2C Label: RSSTSESS Description: Error during session termination. The server tried to terminate an ACF/VTAM session at the end of a file transfer but could not. Probably, the session had already been terminated by ACF/VTAM when NetView FTP issued the session termination request. This reason code does not necessarily indicate that the file transfer was not successful. 48 30 Label: RSSRECOV Description: Session recovery not successful. During a file transfer, the server detected an ACF/VTAM session interrupt and tried to automatically recover the session. However, this attempt failed. Probably, whatever caused the interrupt prevented the server from recovering the session. 52 34 Label: RSSIMMED Description: Immediate termination during session recovery. During a file transfer, the server detected an ACF/VTAM session interrupt and tried to automatically recover the session. However, this attempt failed because the termination of the current file transfer was requested. Possible reasons are: Ÿ A user deleted the file-transfer request. Ÿ The operator stopped the server on which the file-transfer request was running. Ÿ The queue handler encountered an error and ordered all servers to terminate immediately. 56 38 Label: RSSUXFH Description: Error in a user-written file handler. The file-transfer request indicated that NetView FTP was to use a user-written file handler to gain access to a data set. An error occurred during the running of the file handler.

114 NetView FTP Messages and Codes

Figure 4 (Part 4 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 60 3C Label: RSSVNCON Label: RSNVNCON Description: Incompatible parameters. Description: Parameter values not compatible. The server checked the parameters in the file-transfer A user interface checked the file-transfer request and request and found an incorrect combination of found at least one parameter value that was parameters or parameter values. Probably, the incompatible with others. The file-transfer request was pre-transfer user-exit routine modified the file-transfer rejected, that is, it was not added to the request queue. request incorrectly. If you are using the interactive interface, check the contents of the additional parameters panels. If you do not find any incompatible values, add the file-transfer request to the request queue again; NetView FTP might have changed one or more incompatible default values when it displayed the additional panels. 64 40 Label: RSSDALER Label: RSNNRCX Description: Deallocation error. Description: Pre-queuing user-exit routine not found. The server dynamically allocated a data set for a file Before passing a file-transfer request on to the queue transfer. After the file transfer, the server tried to handler, the user interfaces always pass control to the deallocate the data set, but the attempt failed. Possibly, pre-queuing user-exit routine. This routine was not a system error occurred. found. The routine must be loadable from one of the current link-list libraries. Probably an error was made during installation. 68 44 Label: RSSABAX Description: Abnormal termination of server subtask or, for VSE, any NetView FTP subtask. A NetView FTP subtask terminated abnormally. A server subtask terminated abnormally. Possible reasons are: Ÿ The operator canceled the server Ÿ A NetView FTP program error. 69 45 Label: RSSABAM Description: Abnormal termination of server (MVS) or the NetView FTP maintask (VSE). A server terminated abnormally. The reason for the abnormal termination was not necessarily related to a specific file transfer. Possible reasons are: Ÿ The operator canceled the server Ÿ A NetView FTP program error. 72 48 Label: RSSDSNER Label: RSNDSNER Description: Data-set names do not match. Description: The length of at least one data-set name (file ID) exceeds the maximum length. Both a data-set name and a ddname were specified in the file-transfer request. The data-set name specified in In NetView FTP there is a maximum length allowed for the DD, DLBL, or TLBL statement that corresponds to file IDs. For more information about maximum length the ddname was different from the data-set name refer to NetView FTP Parameter Reference. specified in the file-transfer request. 76 4C Label: RSSREINC Description: Higher FTP level required. A file-transfer request required a server to do something for which its FTP level is too low. For more information about FTP levels, refer to the Operation and Administration for your transfer program.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 115

Figure 4 (Part 5 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 80 50 Label: RSSNOLUN Description: No LU name found. A server group was specified in the file-transfer request. The server asked the queue handler to provide the LU names for the server group but the queue handler could not provide any names. Probably, the server group table was modified and the queue handler was restarted after the file-transfer request was added to the request queue. The queue handler only provides LU names that have the correct server running mode. 92 5C Label: RSSCRER Description: I/O error in the checkpoint data set. When looking for a checkpoint record, the server encountered an I/O error in the checkpoint data set. 96 60 Label: RSSCRNFD Description: Checkpoint not found in data set being transferred. The server tried to restart an interrupted file transfer from a checkpoint. It found the checkpoint record in the checkpoint data set, but its attempt to use it to restart the transfer failed. Possible reasons are: Ÿ Not enough storage was available to restart the file transfer of a PDS member Ÿ The server could not find the checkpoint in the data set being transferred because that data set has been modified since the checkpoint record was written. 100 64 Label: RSSDSNEM Label: RSNQIQNR Description: Error with KSDS option ADDBEG. Description: Queue handler not ready. The file-transfer request specified the value ADDBEG A user interface routine issued a queue handler for the KSDS option, but the receiving data set already command but the queue handler was not started or had contained records. This is not allowed with the value not yet finished its initialization processing. The queue ADDBEG. The server at the receiving node broke off handler command was not carried out. the file transfer. 104 68 Label: RSSCRINV Label: RSNSTQUI Description: Incorrect checkpoint record found or Description: Delayed termination of queue handler in checkpoint data set full. progress. Ÿ NetView FTP uses different formats for the A user interface routine issued a queue handler checkpoint records used with user-written file command. However, because the queue handler was handlers and with NetView FTP file handlers. The in a state of delayed termination, the queue handler server obtained a checkpoint record of the wrong could not carry out the command. format. This is probably due to an integrity problem. Ÿ The server could not write a new checkpoint data set. The file transfer continues. Refer to the Installation, Operation, and Administration guide for your NetView FTP. 108 6C Label: RSNSTIMM Description: Immediate termination of queue handler in progress. A user interface routine issued a queue handler command. However, because the queue handler was in a state of immediate termination, the queue handler could not carry out the command.

116 NetView FTP Messages and Codes

Figure 4 (Part 6 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 112 70 Label: RSNAREJT Description: Request queue is full. The file-transfer request cannot be added to the request queue because there is no free space for it. No request can be added to the queue until one or more requests are deleted from it. 116 74 Label: RSNSQBLD Description: Queue handler presently rebuilding the request queue. The queue handler cannot carry out the queue handler command because it is rebuilding the request queue. When it has finished rebuilding the queue, the queue handler can again carry out queue handler commands. The amount of time the queue handler needs to rebuild the request queue depends on the size of the queue. 120 78 Label: RSSRCTER Label: RSNSSLFE Description: Mismatch in record or byte count. Description: Queue handler error. After two servers successfully transfer a data set, they The queue handler cannot carry out the queue handler compare the number of records or bytes each recorded, command because, due to a NetView FTP program sent or received. The comparison resulted in a error, no resources are available to it. mismatch. This problem might indicate a NetView FTP program error. 124 7C Label: RSSRINER Label: RSNSPSTE Description: Error in building an RACF environment. Description: Communication error. The server tried to use the values of the security The SVC routine was not able to establish parameters in the file-transfer request to build a communication between the queue handler and the temporary RACF environment, but the attempt failed. NetView FTP component that issued the queue handler Probably, the values specified were incorrect. command. This code indicates a NetView FTP installation error or an error in the system parameter definition. 128 80 Label: RSSRDLER Description: Error in deleting an RACF environment. The server transferred a data set under the control of a previously built RACF environment. The attempt to delete this environment and reestablish the original authorization failed. This is probably due to a system error or a NetView FTP program error. 132 84 Label: RSSOPTRM Description: Operator termination. The file transfer was interrupted, due to one of the following: Ÿ The operator at the local system terminated one of the following: – The server that was transferring the file – The queue handler (MVS,VM) – The NetView FTP partition (VSE). Ÿ An irrecoverable error in the queue handler caused it to terminate immediately. Ÿ An irrecoverable error in the NetView FTP partition caused it to terminate immediately (VSE).

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 117

Figure 4 (Part 7 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 136 88 Label: RSSTIMEX Label: RSNNFND Description: Processing period elapsed. Description: Request not found. The server obtained a file-transfer request from the A user interface routine issued a queue handler request queue. However, the not-after time specified in command to delete, query, or modify a specific the file-transfer request had already elapsed. The file-transfer request, but the queue handler could not server did not carry out the file-transfer request. find this request in the request queue. 140 8C Label: RSSSEND Label: RSNQOFLW Description: ACF/VTAM error while sending data. Description: Request queue is full; queue rebuild started. The server encountered an ACF/VTAM error when it tried to send data. The data could have been either A user interface routine tried to add a request to the parts of the data set to be transferred or NetView FTP queue but there was no space left in the queue. The internal control information. queue handler started to rebuild the request queue, that is, the queue handler started to delete successfully finished requests that have been in the queue longer than the delay time set by the system programmer. If the queue handler finds any such requests, there will be free space in the queue again. 144 90 Label: RSSRECV Label: RSNNOID Description: ACF/VTAM error while receiving data. Description: Server group not found in server group table. The server encountered an ACF/VTAM error when it tried to receive data. The data could have been either A file-transfer request specified a remote server group, parts of the data set to be transferred or NetView FTP but this server group was not found in the server group internal control information. table. Possible reasons are: Ÿ The file-transfer request contained the incorrect server group. Ÿ The server group table is not up to date. Ÿ The queue handler has not been started since the server group table was last updated. 148 94 Label: RSSINVAL Label: RSNINVAL Description: Incorrect parameter found. Description: Request contains incorrect parameters or parameter values. The server checked the parameters in the file-transfer request and found an incorrect parameter or an A user interface routine checked the file-transfer incorrect value for a parameter. Probably, the request and found an incorrect parameter or an pre-transfer user-exit routine modified the file-transfer incorrect value for a parameter. This code indicates a request incorrectly. user error. 152 98 Label: RSSINOPS Label: RSNINOPS Description: Parameter not compatible with operating Description: Parameter not compatible with operating system. system. The server checked the file-transfer request and found A user interface routine checked the file-transfer that one or more of the parameters were incompatible request and found one or more values that were with the operating system under which the server incompatible with the operating system of the node for operates. which they were specified. Possible reasons are: Ÿ The user specified incorrect values when creating the file-transfer request Ÿ The wrong operating system was specified for a node in the server group table. 156 9C Label: RSNNNDT Description: Server group table not found. A file-transfer request contained a value that requires that the queue handler loaded the server group table during its initialization. However, during its initialization, the queue handler did not find the server group table and started without it. This error is probably due to an error during installation.

118 NetView FTP Messages and Codes

Figure 4 (Part 8 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 160 A0 Label: RSNNAUTH Description: Master password missing or incorrect. A user interface routine issued A queue handler command to query, delete, or modify the file-transfer request of another originator. However, the master password was either not specified or was incorrect. 162 A2 Label: RSNNORES Description: Request is not available for restart. A user interface routine issued a queue handler command to restart a file-transfer request. The request is not available for restart processing for one of the following reasons: Ÿ The file-transfer request does not exist. Ÿ The file-transfer request has the status waiting. Ÿ The file-transfer request has the status active. Ÿ The file-transfer request has finished successfully. Ÿ The file-transfer request has finished unsuccessfully but is not manually restartable. 164 A4 Label: RSNNENTR Description: No request found for the originator specified. A user interface routine issued a queue handler command to delete or query file-transfer requests that were submitted by a specific originator. However, no request was found for this originator or no request at all was found in the request queue. This reason code usually accompanies the return code 0. 168 A8 Label: RSNNDEL Description: Not all requests to be deleted were deleted. A user interface routine issued a queue handler command to delete one or more file-transfer requests from the request queue. However, at least one of the file-transfer requests could not be deleted because: Ÿ The file-transfer request was protected with a password that was not specified with the queue handler command. Ÿ The file-transfer request was unsuccessfully finished and can only be deleted with the FORCEDEL command. This reason code usually accompanies the return code 0. 170 AA Label: RSNRSTBL Description: Request available for restart processing. An active file-transfer request was interrupted with the DELETE command. The status of the file-transfer request is changed to finished. The file-transfer request is available for restart.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 119

Figure 4 (Part 9 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 172 AC Label: RSNSAACT Description: Server already in server table. A server tried to connect to the queue handler but a server with the same job or started-task name was already in the queue handler’s server table. This is probably because the server did not disconnect from the queue handler the last time it terminated. This can happen when the operator cancels a server. When the queue handler encounters this problem, it removes the entry from the server table. When the server is then started again, it should be able to connect without any problem. 176 B0 Label: RSNMAXSV Description: Maximum number of servers reached. A server tried to connect to the queue handler. However, the maximum number of servers that can connect to the queue handler has already been reached. This number is specified in an initialization parameter for the queue handler. 180 B4 Label: RSNNDREQ Description: No request available for processing. A server tried to obtain a file-transfer request to process but the queue handler could not find one available for processing. 184 B8 Label: RSNSVNFD Description: Server name not found in server table. A server issued a queue handler command but the queue handler could not find an entry for that server in its server table. The queue handler did not carry out the queue handler command. This code indicates a NetView FTP program error. 186 BA Label: RSNNOIL Description: Incorrect type of NOTIFY queue handler command. The server attempted to use a queue handler command that is not allowed for the request specified. 196 C4 Label: RSNFBASH Description: More information retrieved than fits in buffers. A user interface routine queried one or more requests. The queue handler retrieved more information than fits into the buffers and there is still more information to obtain. If the application program interface issues this reason code, the buffers provided by the application program are too small. If the batch job interface routine or the interactive interface routine issues this reason code, a NetView FTP program error has occurred.

120 NetView FTP Messages and Codes

Figure 4 (Part 10 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 200 C8 Label: RSNABEND Description: Abnormal termination of queue handler. The queue handler abnormally terminated while processing a queue handler command. This probably happened because of a NetView FTP program error but can also happen when the operator cancels the queue handler. 204 CC Label: RSSRKSDS Label: RSNRKSDS Description: Incorrect KSDS option. Description: Incorrect VSAM KSDS option. The server found an incorrect value for the KSDS A user interface routine checked the file-transfer Option parameter. Probably, the pre-transfer user-exit request and found an incorrect value for the VSAM routine modified the file-transfer request incorrectly. KSDS option. This code indicates a user error. 208 D0 Label: RSSRDEN Label: RSNRDEN Description: Incorrect tape density. Description: Incorrect tape density. The server found an incorrect value for the Tape A user interface routine checked the file-transfer Density parameter. Probably, the pre-transfer user-exit request and found an incorrect value for the Tape routine modified the file-transfer request incorrectly. Density parameter. This code indicates a user error. 212 D4 Label: RSSREXPD Label: RSNREXPD Description: Incorrect expiration date. Description: Incorrect expiration date or retention period. The server found an incorrect value for the Expiration Date parameter. Probably, the pre-transfer user-exit A user interface routine checked the file-transfer routine modified the file-transfer request incorrectly. request and found an incorrect value for the Expiration Date or Retention Period parameter. This code indicates a user error. 216 D8 Label: RSSVMLIN Label: RSNVMLIN Description: Incorrect VM link parameters. Description: Incorrect VM link parameters. The server found at least one of the following: A user interface routine checked the file-transfer request and found at least one of the following: Ÿ An incorrect combination of VM link parameters Ÿ An incorrect value for a VM link parameter. Ÿ An incorrect combination of VM link parameters Probably, the pre-transfer user-exit routine modified the Ÿ An incorrect value for a VM link parameter. file-transfer request incorrectly. 220 DC Label: RSSVOLSE Label: RSNVOLSE Description: Missing volume serial number. Description: Missing volume serial number. Specifying a volume serial number is mandatory for this A user interface routine checked the file-transfer file transfer, but the server found that a volume serial request and found that a volume serial number was number was not specified. Probably the pre-transfer required but missing. user-exit routine modified the file-transfer request This code indicates a user error. incorrectly. 224 E0 Label: RSSINCOM Description: Incompatible transfer program at remote node. After a local server established an ACF/VTAM session with a remote server, it discovered that the transfer program at the remote node: Ÿ Had an FTP level that was incompatible with its FTP level, or Ÿ Had an insufficient service level, or Ÿ Had an NetView FTP level that does not perform an LU 6.2 protocol type conversation, or Ÿ Was some program other than FTP V2 or NetView FTP. It did not begin the file transfer.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 121

Figure 4 (Part 11 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 228 E4 Label: RSNNANBI Label: RSNNANBI Description: Not-before or not-after time or date Description: Not-before or not-after time or date incorrect. incorrect. A not-before or not-after time or date is incorrect. A not-before or not-after time or date is incorrect. Possible reasons are: Possible reasons are: Ÿ The not-after time and date is earlier than the Ÿ The not-after time and date is earlier than the not-before time and date, or than the current time not-before time and date, or than the current time and date and date Ÿ The specified time or date was not valid (for Ÿ The specified time or date was not valid (for example, 25:00 or 32 December). example, 25:00 or 32 December). This indicates a user error. This indicates a user error. 230 E6 Label: RSNINRAC Description: Incorrect security parameter specification. The request contained an * that was incorrectly specified. Refer to the NetView FTP User’s Guide for information about how to specify values for security parameters correctly. 248 F8 Label: RSSREJTR Description: File-transfer request rejected by pre-transfer user-exit routine. Before the file transfer starts, the server passes the file-transfer request to the pre-transfer user-exit routine. This routine rejected the file-transfer request, that is, it told the server not to carry out the file transfer. 252 FC Label: RSSRECL Description: Record length not correct. The receiving server received a data record that did not fit into the I/O buffers. The receiving data set was not defined to contain records that are as long as those that were sent. 260 104 Label: RSSUXNF Description: Error while loading a user-written file handler. The file-transfer request indicated that NetView FTP was to use a user-written file handler to gain access to a data set. The load module name for the file handler was specified in the file-transfer request, but the server was not able to load the routine. Possible reasons are: Ÿ The load module name specified in the file-transfer request was wrong Ÿ The server did not have access to the correct load libraries. 264 108 Label: RSSCONTU Description: The file-transfer request was rejected because no connection was received by the distribution-service machine from the file-service machine within 5 minutes after it was autologged.

122 NetView FTP Messages and Codes

Figure 4 (Part 12 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 302 12E Label: RSSLIO Label: RSNLIO Description: I/O error in data set. Description: I/O error while carrying out queue handler command. While gaining access to a data set, a server encountered a logical or physical I/O error. Possible The queue handler encountered an I/O error while reasons are: carrying out a queue handler command. The command was not carried out. This might be due to a hardware Ÿ The values of the parameters for the data set were problem. incorrect Ÿ All extents of a data set were full Ÿ A device error occurred. 303 12F Label: RSSADDK Description: Error with KSDS option ADDKEY. The file-transfer request specified the value ADDKEY for the KSDS option, but a record that was to be written to the receiving data set had the same key as a record that was already in the receiving data set, and the contents of the two records were not the same. This is not allowed with the value ADDKEY. The receiving server broke off the file transfer. 304 130 Label: RSSCBM Label: RSNCBM Description: VSAM macroinstruction error. Description: VSAM macroinstruction error. The server uses the VSAM macros MODCB, TESTCB, The queue handler uses the VSAM macros SHOWCAT, and SHOWCB when working with VSAM control blocks. MODCB, TESTCB, and SHOWCB when working with One of the macros returned an error. This is probably a VSAM control blocks. One of the macros returned an NetView FTP program error. error. This is probably because the VSAM file does not exist or because of a NetView FTP program error. 305 131 Label: RSSOPN Label: RSNOPN Description: Error returned from OPEN or CLOSE Description: Error during OPEN or CLOSE. macro. The queue handler uses the OPEN macroinstruction to The server uses the OPEN macroinstruction to make a make the request queue available for accessing, and data set available for access during a file transfer, and the CLOSE macroinstruction to finish the accessing. the CLOSE macroinstruction to end the access. One of One of these macros returned an error. the macros returned an error. If the error was returned by: OPEN The server did not begin the file transfer. CLOSE The server completed the file transfer, which might have been successful. VM only: You have tried to process a tape that might not be mounted. 306 132 Label: RSSSPMIS Description: Security parameters missing. The server that processed the request requires one of the following: Ÿ Security parameters were specified in the file-transfer request Ÿ The server is able to retrieve security parameters automatically (MVS). Refer to message DVG159I for more information.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 123

Figure 4 (Part 13 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 307 133 Label: RSSRACF Description: RACF authorization error. When the server attempted to open the sending or receiving data set, using the specified or default security parameter values, it encountered a system ABEND code of 913. This indicates that the specified or default user is not authorized to access the data set. VM only: You do not have authorization to link the specified minidisk. CP returns code 298. 308 134 Label: RSSRPNR Description: RACF parameters cannot be retrieved. The transfer program failed to retrieve the RACF password or group ID, or both, as specified in the request. Check the return and reason code from the RACXTR macro for more information about the error. This can be found in the transfer report file or the server log file. 309 135 Label: RSSOPNE Description: Nonexistent PDS member specified. The server tried to make a single member available for file transfer, but this member does not exist. 310 136 Label: RSSREPK Label: RSNREPK Description: Error with KSDS option REPKEY. Description: Request not found on the request queue. The file-transfer request specified the value REPKEY The queue handler tried to update a file-transfer for the KSDS Option parameter, but a record was to be request on the request queue but could not find the written and another record with the same key did not request. This code can indicate either a NetView FTP already exist in the receiving data set. This is not program error or incorrect installation of the request allowed with the value ADDBEG. The receiving server queue. broke off the file transfer. 311 137 Label: RSSDSNR Label: RSNDSNR Description: Error while retrieving a data-set name. Description: Error while retrieving a data-set name. NetView FTP tried to retrieve the name of a data set to NetView FTP tried to retrieve the name of a data set be transferred from the job file control block, but the from the job file control block, but the attempt failed. attempt failed. If NetView FTP was using dynamic This is probably due to missing disk-label information allocation, this is probably due to a NetView FTP for the NetView FTP work file catalog. program error. If NetView FTP was using job allocation, this is probably due to a user error (the wrong ddname was probably specified in the file-transfer request).

124 NetView FTP Messages and Codes

Figure 4 (Part 14 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 312 138 Label: RSNLOGER Description: Error with KSDS option ADDKEY or DELKEY. One of the following occurred: Ÿ The file-transfer request specified the value ADDKEY for the KSDS option. A record with the same key as one of the records being sent already existed in the receiving data set, but the two records were identical. Ÿ The file-transfer request specified the value DELKEY for the KSDS option, but none of the records to be deleted existed in the receiving data set. These situations do not cause the file transfer to be broken off, but because they are unusual and might be of interest to you, FTP V2 and NetView FTP issue this reason code for your information. The file transfer continues normally. 313 139 Label: RSSRALOC Description: RACF allocation error. NetView FTP attempted to dynamically allocate a data set that has an RACF profile for which the user or NetView FTP are not authorized. 314 13A Label: RSSNOTX Description: Nonexistent member specified in the member selection or exclusion list. A PDS member that could not be found in the sending PDS was selected or excluded. 315 13B Label: RSSPDSC Description: PDS option in conflict. A PDS option was specified that conflicts with the presence, or absence of the member in the receiving PDS. 316 13C Label: RSSGVSER Description: Error while requesting virtual storage. The operating system did not satisfy the server’s or another NetView FTP component’s request for a block of virtual storage, probably because: Ÿ The server was run in too small an address space (MVS). Ÿ The server was run in too small a virtual machine (VM). Ÿ NetView FTP was run in too small a partition, the GETVIS area was too small (VSE). 320 140 Label: RSSRVSER Description: Error while releasing virtual storage. The operating system did not satisfy the server’s request to release a block of virtual storage. Probably, there was either a system error or a NetView FTP program error.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 125

Figure 4 (Part 15 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 324 144 Label: RSSFCERR Description: Error while retrieving attributes of the sending data set. The server tried to retrieve the attributes of the sending data set so that they could be used when defining the receiving data set. However, the attempt failed. Probably, there was a system error. 328 148 Label: RSSV2ER Description: Error on a remote FTP V2 node. The transfer program at the remote node is FTP V2. An error occurred on the remote node, and the FTP V2 at that node informed the server at the local node about the error. This reason code is issued for all the different kinds of errors that can occur at an FTP V2 node, because reason codes for specific errors are not supported by FTP V2. 330 14A Label: RSSDELET Label: RSNDELET Description: File transfer interrupted by request Description: File transfer interrupted by request deletion. deletion. A user deleted a file-transfer request that corresponded A user deleted a file-transfer request that corresponded to a file transfer that was in progress. The server broke to a file transfer that was in progress. The server broke off the file transfer. off the file transfer. 334 14E Label: RSNFORCE Description: File transfer interrupted by forced request deletion. A user deleted a file-transfer request that corresponded to a file transfer that was in progress. The server broke off the file transfer. 384 180 Label: RSSFTYP Description: Ÿ File type in DD statement and in request do not match. Both a data-set type and a ddname were specified in the file-transfer request. The data-set type specified in the DD, DLBL, or TLBL statement that corresponds to the ddname was different from the data-set type specified in the file-transfer request. Ÿ No data-set type was specified in the request and the server could not retrieve the DSORG. 388 184 Label: RSSDCERR Description: Error during definition of receiving VSAM cluster. The receiving VSAM cluster could not be defined. Possible reasons are: Ÿ The cluster had a cluster, data, or index name that already existed. Ÿ Incorrect password or passwords were specified in the file-transfer request. Ÿ An incorrect catalog was specified in the file-transfer request. Ÿ Insufficient suballocation data space. Ÿ Insufficient space to allocate the cluster.

126 NetView FTP Messages and Codes

Figure 4 (Part 16 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 392 188 Label: RSSIPO Description: Attributes of PDS not supported by BPAM. The PDS being transferred has attributes that are not supported by BPAM. Possible reasons are: Ÿ Its record format is variable spanned (VS) or variable blocked spanned (VBS). Ÿ The attributes of the sending and receiving data sets are incompatible. Ÿ There is more than one note list TTR for one member. Ÿ Two members have the same TTR but both are real members. 396 18C Label: RSSTPO Description: PDS transfer error. A PDS could not be transferred, probably because it is defined as being unmovable, that is, it has the data-set type PO. 400 190 Label: RSNQHNEC Description: Request cannot be modified. A request cannot be modified because: Ÿ Its status is not waiting. Ÿ It was already modified by the pre-queuing user-exit routine. Ÿ It is blocked. 404 194 Label: RSNQHGTE Description: GETMAIN error occurred. An error occurred when a conditional storage allocation was done. The problem may be temporary. If it occurs often, notify your system programmer; it indicates a potential CSA space problem. The limiting factor in determining the maximum additional CSA size for one request (the CSAELIM queue handler initialization parameter or the maximum request queue record length) might be too high. If the error occurs when a user interface issues the ADD queue handler command, the file-transfer request is rejected. Submit the request again later. If the error occurs when a server issues the OBTAIN queue handler command, the file-transfer request is marked as being deferred. A server will try again later to process the request. 408 198 Label: RSNQHSHD Description: All servers are on hold. All servers are on hold, so no request can be processed.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 127

Figure 4 (Part 17 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 412 19C Label: RSNQHRTL Description: CSA too small to accommodate RXB. A server tried to obtain a request from the queue. The RCB extension (RXB) needs more CSA storage than is available. The request is blocked. Probably, the request was added to the queue at a time when more space was available. In the meantime, the queue handler was stopped and later restarted, but with less CSA storage than before (the value for the CSAELIM initialization parameter was smaller than before). The request is blocked, and cannot be processed until the queue handler is stopped and restarted with more CSA storage. 416 1A0 Label: RSNINRXB Description: Incorrect RCB extension. This code indicates a NetView FTP program error. Contact your system programmer. 420 1A4 Label: RSNRXBSM Description: Single member and member selection specified. A user interface checked the request and found that both a member list and the name of a single member were specified. Specify either one or the other and resubmit the request. 424 1A8 Label: RSNLDSNC Description: Data set not found in catalog. Because a volume was not specified in the file-transfer request, a user interface routine tried to locate a data set in the catalog. The return code from the CAMLIST macroinstruction indicated that the data set could not be found in the catalog. Before you can transfer the data set, you must do one of the following: Ÿ Catalog the data set. Ÿ Specify the type of the data set. Ÿ Specify the volume on which the data set resides.

128 NetView FTP Messages and Codes

Figure 4 (Part 18 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 426 1AA Label: RSNLDSAC Description: Data set already cataloged. Before the file transfer was started, the receiving server found the name of the new data set already in the catalog. The receiving data set was not allocated, the file transfer did not take place. Before you can transfer the data set, you must do one of the following: Ÿ Uncatalog the existing data set Ÿ Delete the existing data set Ÿ For NetView FTP V2.2 MVS, change in the request the value of the File Status option from MUSTNOTEXIST to MUSTEXIST and the value of the End-of-Processing option for the successful case from CATLG to KEEP and check if you must remove parameters not relevant for this disposition. Ÿ For NetView FTP other than NetView FTP V2.2 MVS, change the disposition parameter in the request from CAT to OLD and check if you must remove parameters not relevant for this disposition. 428 1AC Label: RSNODSNF Description: Data set not found during retrieval of DSCB information. A user interface routine tried to obtain DSCB information for a data set. The volume containing the data set was either pointed to by the catalog entry or specified in the file-transfer request. The return code from the CAMLIST macroinstruction indicated that the volume pointed to or specified does not contain the data set. 432 1B0 Label: RSNVOLNM Description: Volume not mounted. A user interface routine tried to obtain DSCB information for a data set. The return code from the CAMLIST macroinstruction indicated that the catalog entry points to a volume that is not mounted. Ask the operator to mount the volume. 436 1B4 Label: RSNLOCEC Description: Error from CAMLIST while locating data set. Because a volume was not specified in the file-transfer request, a user interface routine tried to locate a data set in the catalog. However, the return code from the CAMLIST macroinstruction indicates that the data set could not be found in the catalog. 440 1B8 Label: RSNOBTEC Description: Error from CAMLIST while obtaining DSCB information. A user interface routine tried to obtain DSCB information for a data set. However, the return code from the CAMLIST macroinstruction does not indicate that the volume pointed to or specified does not contain the data set, or that the catalog entry points to a volume that is not mounted.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 129

Figure 4 (Part 19 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 444 1BC Label: RSNNOLU Description: LU name not found in server group table. A server group table is in use at the local node but the LU name specified in the file-transfer request was not found in the server group table. Because most users rarely need to specify LU names other than those contained in the server group table, it is possible that the LU name specified is incorrect. If the LU name specified is: Ÿ Correct, press the ENTER key Ÿ Incorrect, correct it and press the ENTER key. If you do not want to have to verify the LU name each time you specify it, have your system programmer add it to the server group table. 446 1BE Label: RSNLUMOD Description: Correct LU running modes not found. No LUs with the correct running mode (continuous or single) could be found for the server group specified. 448 1C0 Label: RSNAFFVS Description: Remote node does not support VSAM cluster definition. The interactive interface checked the server group table for information about the transfer program at the remote node. It found that the transfer program at the remote node is not capable of defining a new VSAM cluster. 452 1C4 Label: RSNAFFPO Description: Remote node does not support PDS member list processing. The interactive interface checked the server group table for information about the transfer program at the remote node. It found that the transfer program at the remote node is not capable of processing a PDS member list. 456 1C8 Label: RSNRXBUS Description: Not enough storage for parameters for a user-written file handler. A file-transfer request specifies that a user-written file handler is to be used. This request requires more storage than is presently available. The problem is due to one of the following: Ÿ Not enough CSA storage is available to pass the request to the queue handler Ÿ The records of the request queue are too small to accommodate the request. Contact your system programmer.

130 NetView FTP Messages and Codes

Figure 4 (Part 20 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 460 1CC Label: RSNRXBVS Description: Not enough storage for parameters used for VSAM cluster definition. A file-transfer request contains parameters for the definition of a VSAM cluster. This request requires more storage than is presently available. The problem is due to one of the following: Ÿ Not enough CSA storage is available to pass the request to the queue handler Ÿ The records of the request queue are too small to accommodate the request. Contact your system programmer. 464 1D0 Label: RSNRXBPO Description: Not enough storage for a PDS member list. A file-transfer request contains a list of PDS members. This request requires more storage than is presently available. The problem is due to one of the following: Ÿ Not enough CSA storage is available to pass the request to the queue handler Ÿ The records of the request queue are too small to accommodate the request. Contact your system programmer. 468 1D4 Label: RSNMBRPO Description: Too many PDS members specified. The interactive interface routine detected that more members were selected or excluded than NetView FTP can fit in one request. Instead of creating one request, create several. 472 1D8 Label: RSNGDGCO Description: GDG model ID and user catalog ID specified. You can specify either a GDG model ID or a user catalog ID. 476 1DC Label: RSNSVMOD Description: Running mode of the server different to the one specified in the request. A file-transfer request specified the LU name of a server. The running mode of that server does not match the running mode specified for that server in the request. 480 1E0 Label: RSNRXBWT Description: Incorrect APX type specified. The application program interface routine checked the file-transfer request and found an APX type other than SELECT or EXCLUDE. Correct the APX type and resubmit the request.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 131

Figure 4 (Part 21 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 484 1E4 Label: RSNMBRLN Description: Member name or relative generation number too long. The application program interface routine or batch job interface routine checked the request and found that one of the following was more than 8 characters long: Ÿ The name of a PDS member Ÿ The relative generation number of a data set that is a member of a GDG. 488 1E8 Label: RSNMBRCT Description: More than 999 members were specified. 492 1EC Label: RSNGDGMR Description: Member name was specified twice. The application program interface routine or batch job interface routine checked the file-transfer request and found that the name of a PDS member was specified both as part of the data-set name and as the value of the Member Name parameter. Only one of these specifications is allowed. 496 1F0 Label: RSNRXBT Description: Incompatible parameters specified. The application program interface routine or batch job interface routine checked the file-transfer request and found at least two of the following: Ÿ VSAM cluster parameters Ÿ A PDS member list Ÿ User-written file handler parameters. Only one of these is allowed in a single request. 500 1F4 Label: RSNMIPAR Description: Member name not specified. The batch job interface routine checked the request and found the MEMBER control statement, but no member name was specified. 504 1F8 Label: RSNMBRNO Description: Parentheses found in data-set name but no member name or relative GDG specified. The application program interface routine or batch job interface routine checked the file-transfer request and found opening and closing parentheses in the data-set name, but the name of a PDS member or a relative GDG was not specified. Either remove the parentheses or add the name of the missing member or relative GDG and resubmit the request. 508 1FC Label: RSNOPBRK Description: Only opening parenthesis in data-set name. The application program interface routine or batch job interface routine checked the file-transfer request and found an opening parenthesis in the data-set name. Remove the parenthesis and resubmit the request.

132 NetView FTP Messages and Codes

Figure 4 (Part 22 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 512 200 Label: RSNCLBRK Description: Only closing parenthesis in data-set name. The application program interface routine or batch job interface routine checked the file-transfer request and found a closing parenthesis in the data-set name. Remove the parenthesis and resubmit the request. 516 204 Label: RSNPIOER Description: Permanent I/O error encountered during OBTAIN. A user interface routine performed an OBTAIN on a data set and encountered a permanent I/O error. Ask the operator to check the volume and data set. 520 208 Label: RSNLOCMI Description: LOCATE error; data set has been migrated. The interactive interface could not locate the data set specified in the request because the data set was migrated. Have HSM recall the data set, then submit the request again. 524 20C Label: RSNATLST Description: User lost authorization to modify this request. A user’s attempt to modify a request failed because either the administrator or the operator already modified it. After the administrator or the operator modifies a request, only they can modify it further. 528 210 Label: RSNSVHLD Description: Server set to hold. The operator has set the server to hold. It cannot process any requests. 532 214 Label: RSNOBTUD Description: Error encountered during OBTAIN; unsupported data-set type. A user interface routine automatically retrieved the type of a data set. The data set is of a type not supported by NetView FTP, that is, does not have the type VSAM, PO, PS, LAB, or UNLAB. Ask your system support personnel to check the data set. 536 218 Label: RSNAPXEN Description: No APX entries specified. The application program interface routine checked the file-transfer request and found that the user supplied an APX but did not specify any entries in the APXENT field. Specify a value for APXENT and submit the request again. 540 21C Label: RSNHSMAL Description: Failed allocation. During a recall of a migrated data set, the allocation failed.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 133

Figure 4 (Part 23 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 544 220 Label: RSNHSMDE Description: Failed deallocation. During a recall of a migrated data set, the deallocation failed. 548 224 Label: RSNUNTPN Description: Transaction program name not supported. A remote program tried to establish a conversation with NetView FTP but used a transaction program name that is not supported by NetView FTP. 550 226 Label: RSNPVERR Description: The server has encountered an ACF/VTAM error that is regarded as being permanent. The request is not requeued automatically. 551 227 Label: RSNNOREQ Description: The request is not requeued by the post-transfer user-exit routine. 552 228 Label: RSNRXBSE Description: The RXB cannot be processed because not enough space is available. Possible reasons are: Ÿ The maximum record size defined for the request queue is too small Ÿ MVS only: the maximum size of CSA space defined for NetView FTP is too small or is not available. For more information, refer to the appropriate Installation, Operations, and Administration Guide. 553 229 Label: RSNJOERR Description: Error during post-transfer job submission. During processing of the post-transfer job submission, a server encountered an error. The problem may be due to one of the following: Ÿ An error occurred during the dynamic allocation of the data set containing the job Ÿ An I/O error occurred while the transfer program was processing the job submission via QSAM Ÿ The specified job library data set or the member could not be found Ÿ The data set containing the post-transfer job is not partitioned organized. 554 22A Label: RSNSYSEX Description: The server cannot continue processing due to a system problem. 555 22B Label: RSNDPKWD Description: A keyword that can only be specified once has been specified more than once. 556 22C Label: RSNEXOJ Description: An object (file or member) already exists.

134 NetView FTP Messages and Codes

Figure 4 (Part 24 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 557 22D Label: RSNNEXOJ Description: An object (file or member) does not exist. 558 22E Label: RSNFULOJ Description: An object (file or volume) is full. 559 22F Label: RSNIUSOJ Description: An object cannot be accessed because it is already in use. 560 230 Label: RSNUNSFC Description: A function is not supported by the local transfer program. 561 231 Label: RSNNACFC Description: A function is not active at the remote transfer program. 562 232 Label: RSNNOPFC Description: A function is not operational at the remote transfer program. 563 233 Label: RSNPRTER Description: A protocol violation has been detected. The local transfer program detected a violation of the rules described in the file-transfer protocol. The violation has been caused by the partner transfer program. A dump of the Error Message Unit sent to the remote file transfer program is taken. Contact your IBM Support Center. 564 234 Label: RSNCRYLB Description: The specified encryption label is not known to PCF. Correct and resubmit the request. 565 235 Label: RSNCRYNA Description: PCF is not active. Start PCF and resubmit the request.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 135

Figure 4 (Part 25 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 566 236 Label: RSNCRYER Description: PCF returned a serious error. The following are possible reasons: 1. At the sending location: Ÿ The Cross key has bad parity Ÿ I/O error reading PCF CKDS Ÿ Error reading time-of-day clock, or time-of-day clock was inoperative Ÿ Internal PCF error during key translation (RETKEY macro). 2. At the receiving location: Ÿ The server program was either not APF authorized, not in supervisor state, or not under protection key 0..7 Ÿ The Cross key has bad parity Ÿ I/O error reading PCF CKDS Ÿ Internal PCF error during key translation (RETKEY macro). For more information see OS/VS1 OS/VS2 MVS Programmed Cryptographic Facility: Installation Reference (GENKEY, RETKEY, and CIPHER macro description). 567 236 Label: RSNTEMP Description: A temporary problem occurred during processing of a file-transfer request. If the request originator allowed requeuing of the request, the request is scheduled again later. Additional information about the problem can be found in the server’s log and the report data set. 568 237 Label: RSNPERM Description: A permanent problem occurred during processing of a file-transfer request. The transfer request will not be scheduled again, no matter what the request originator specified. Additional information about the problem can be found in the server’s log and the report data set. 569 239 Label: RSNAPSEC Description: The remote server did not accept the APPC security parameters specified in the request. The conversation did not start. 570 23A Label: RSNPTPER Description: Error during post-transfer program call. 590 24E Label: RSNVBOER Description: Verb code error, not valid OSI function request. The requested function is valid for an SNA request, but not for an OSI request. 591 24F Label: RSNINMBR Description: You specified a receiving member name but did not specify the corresponding file ID.

136 NetView FTP Messages and Codes

Figure 4 (Part 26 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 592 250 Label: RSNREQUE Description: A post-conversation user exit routine forced the status of the request to WAITING. Both not-before and not-after date and time may have been changed by the exit routine. If the your exit routine provided a message, this message can be found in the transfer report file and in the server’s log file. The new status of the file-transfer request is WAITING. 602 25A Label: RSNTCTRM Description: Access Authorization already held by a NetView FTP VSE subtask. This reason code is defined for internal purposes only and does not appear during normal processing. 603 25B Label: RSNENABD Description: Access Authorization already enabled for another VSE SV subtask. 604 25C Label: RSNNASPP Description: Security parameters have been specified but could not be verified. Refer to message DVG154I for more information. 605 25D Label: RSNNAFTP Description: Security parameters were not specified and NetView FTP does not have authorization to access the file. Refer to message DVG155I for more information. 606 25E Label: RSNNAUSR Description: Security parameters were specified but the specified user ID does not have authorization to access the file. Refer to message DVG155I for more information. 607 25F Label: RSNUPWLN Description: Security parameters were specified but the specified user ID or password is the wrong length. Refer to message DVG150I and DVG151I for more information. 609 261 Label: RSNGRPSP Description: The security parameter Group ID was specified but is ignored by a VSE system. Refer to message DVG152I for more information. 610 262 Label: RSNNOAUT Description: Error during validation of access control user ID and password. Refer to message DVG149I for more information. 611 263 Label: RSNDINOE Description: Request to free access authorization but access authorization is not yet held by NetView FTP VSE subtask. This reason code is defined for internal purposes only and does not appear during normal processing. 612 264 Label: RSNSUBNO Description: SUBSID/NOTIFY failed.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 137

Figure 4 (Part 27 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 613 265 Label: RSNCPCOM Description: Operator message output via CPCOM macro failed. 614 266 Label: RSNATT Description: Attach of subtask failed. 615 267 Label: RSNCDLD Label: RSNCDLD Description: The CDLOAD macro indicated an error Description: The CDLOAD macro indicated an error when loading the module. Refer to message DVG638I when loading the module. Refer to message DVG638I for more information. for more information. 618 26A Label: RSNCPLD Description: The load of the parser module failed. This module is an essential module for the NetView FTP partition. 619 26B Label: RSNIPERR Description: NetView FTP initialization parameter error. During initialization of the NetView FTP partition a syntactical or logical error was detected with the initialization parameters for the NetView FTP partition or servers. The initialization stopped. 620 26C Label: RSNTDFER Description: Tape definition table error. During initialization of the NetView FTP partition a severe error occurred when loading the tape definition table (DVGTDF). The initialization stopped. 622 26E Label: RSNRQCAR Description: Error in request queue characteristics was found during initialization of the queue handler. The initialization stops. The NetView FTP administrator must analyze the problem and may need to redefine the request queue. 623 26F Label: RSNUIBPN Description: Report transmission needs VSE/POWER PNET which is not available. 624 270 Label: RSNUIBOP Description: VSE/POWER SAS open error. 626 272 Label: RSNFVER Description: FREEVIS macro failed. 627 273 Label: RSNSUBIN Description: SUBSID/INQUIRE macro failed. 628 274 Label: RSNRQLK Description: One of the following applies: Ÿ Error in locking the request queue. Ÿ The DVGWFUC label was omitted or incorrectly specified. Therefore the request queue data set could not be found. Processing stops. Your system administrator must analyze the problem.

138 NetView FTP Messages and Codes

Figure 4 (Part 28 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 629 275 Label: RSNRQDLK Description: Error defining a lock for the request queue. 630 276 Label: RSNRQULK Description: Error in unlocking the request queue. Processing stops. Your system administrator must analyze the problem. 631 277 Label: RSNITAIU Description: Requested tape unit currently in use. 632 278 Label: RSNITANA Description: Requested tape unit not available. Check that your Tape Definition Table corresponds to your hardware environment. Refer to NetView FTP VSE Installation, Operation, and Administration for more information. 633 279 Label: RSNITAD1 Description: Tape device type, density and track number, mismatch. Check that your Tape Definition Table corresponds to your hardware environment. Refer to NetView FTP VSE Installation, Operation, and Administration for more information. 634 27A Label: RSNITAD2 Description: Tape device type TAPE unlabeled but density not specified. 635 27B Label: RSNITAI1 Description: Invalid tape device type specified (characters 1...4). 636 27C Label: RSNITAI2 Description: Invalid tape device type suffix specified (characters 5, 6). 637 27D Label: RSNITAI3 Description: Tape device: track number, density mismatch. 638 27E Label: RSNRNFD Description: Record not found. 639 27F Label: RSNEOF Description: End of file reached. 640 280 Label: RSNRQICP Description: Request queue incomplete. At least one request number, between one and maximum request number, in the queue is missing. Processing stops. Your system administrator must analyze the problem. 641 281 Label: RSNNDELA Description: A user tried to delete an active request but active requests cannot be deleted by users or administrators at VSE systems.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 139

Figure 4 (Part 29 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 642 282 Label: RSNNCLP Description: Because another NetView FTP partition is active or a NetView FTP user interface is updating the request queue, no clean-up of the request queue takes place during the startup of the NetView FTP partition. 643 283 Label: RSNICON Description: A request found via the alternate key is different from the request found via the primary key. Your NetView FTP request queue administrator must analyze the problem. 644 284 Label: RSNRLERR Description: Request status fields in conflict due to a logic error. Processing stops. Your NetView FTP request queue administrator must analyze the problem. 645 285 Label: RSNDLNTA Description: Dynamic allocation not active for this server task but a request for deallocation has been received. This reason code is defined for internal purposes only and does not appear during normal processing. 646 286 Label: RSNTMCNC Description: Operator has canceled transfer of a tape file. 647 287 Label: RSNTMREQ Description: Operator has requeued the transfer of a tape file. 648 288 Label: RSNDLALA Description: Dynamic allocation is already active for this server task. 649 289 Label: RSNNDTE Description: At least one invalid record found in the server group table during initialization of NetView FTP. The initialization stops. Your NetView FTP request queue administrator must analyze the problem and redefine the server group table. 650 28A Label: RSNTSKNR Description: A task asked for a service from another task but the posted task was not ready. This reason code is defined for internal purposes only and does not appear during normal processing. 651 28B Label: RSNLRSRG Description: SAM ESDS logical record size out of range. (1 to 32 761). 652 28C Label: RSNSAMS Description: Spanned SAM ESDS files not supported. 653 28D Label: RSNLRSFB Description: A logical record size was specified for a SAM ESDS with a record format that was not FB.

140 NetView FTP Messages and Codes

Figure 4 (Part 30 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 654 28E Label: RSNSAM Description: SAM ESDS was specified for a non-VSE system. 655 28F Label: RSNSAMRF Description: A record format was specified for an indexed VSAM file. 656 290 Label: RSNNOSAS Description: No VSE/POWER SAS support available. 657 291 Label: RSNNOUNO Description: The transfer of a tape file is not possible at an unattended node. Refer to message DVG648I for more information. 700 2BC Label: RSNOPNLG Description: An error occurred while opening the log file. 701 2BD Label: RSNIOELQ Description: An I/O error occurred for the log file. 702 2BE Label: RSNNOCON Description: No connection occurred during a constant wait time. 703 2BF Label: RSNVASER Description: The APPC/VM interface routine indicated a SENDERR (communication partner issued APPCVM/SENDERR). 704 2C0 Label: RSNSTAER Description: Error during ESTAE macro setup. 705 2C1 Label: RSNVKPRE Description: Bad return from VKPREP. 706 2C2 Label: RSNVAPAT Description: Specific path to communication partner no longer exists. 707 2C3 Label: RSNVATIM Description: Function not complete, time exceeded. 708 2C4 Label: RSNVAAPE Description: APPC/VM error occurred. 709 2C5 Label: RSNVANOC Description: No more connections. 710 2C6 Label: RSNVAERR Description: APPC/VM interface routine logic error. 711 2C7 Label: RSNVAPTS Description: Path table shortage. 712 2C8 Label: RSNVAIOE Description: I/O error occurred while accessing the DVGAS NAMES file. 713 2C9 Label: RSNVASHT Description: Receive area shortage.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 141

Figure 4 (Part 31 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 714 2CA Label: RSNVAUNX Description: Program logic error during communication processing. 715 2CB Label: RSNVARTS Description: SENDDATA is not valid from the receiving system. 716 2CC Label: RSNIOELG Description: I/O error in log file. 717 2CD Label: RSNINFIL Description: Invalid CMS file ID. 718 2CE Label: RSNTAPER Description: Tape processing failed. Operator canceled request. 719 2CF Label: RSNNODEV Description: Device is not a DASD, no device found, or SFS not available. 720 2D0 Label: RSNPTHSV Description: Path to CP message services severed. 721 2D1 Label: RSNDSKIU Description: Disk already in use. 722 2D2 Label: RSNOPNOC Description: Operator task terminated without receiving a connect from the queue handler. 723 2D3 Label: RSNOLDIS Description: RTDISP=OLD or RSTATOPT=MUSTEXIST specified but file does not exist. 724 2D4 Label: RSNEWDIS Description: RTDISP=NEW or RSTATOPT=MUSTNOTEXIST specified but file already exists. 725 2D5 Label: RSNINVAC Description: Insufficient access mode. Receiving disk must be in access mode ‘M.’ 726 2D6 Label: RSNNOFML Description: No free file mode is available. 727 2D7 Label: RSNRXBSF Description: SFS not available because not enough space for RXB on request queue. 728 2D8 Label: RSNUSRXB Description: RXB contains sections not supported by VM or VSE. 730 2DA Label: RSNSUBDI Label: RSNSUBDI Description: SFS subdirectory parameters must be Description: SFS subdirectory parameters must be filled in contiguously. filled in contiguously.

142 NetView FTP Messages and Codes

Figure 4 (Part 32 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 731 2DB Label: RSNAPXNV Description: Existing APX is not allowed for VM or VSE. 732 2DC Label: RSNTAREQ Description: The operator requeued the request. Either, because the tape is temporarily not available, or because the tape unit is currently not available. 733 2DD Label: RSNTACAN Description: The operator canceled a tape mount request. This may be because the required tape does not exist, or because you are not authorized to use the tape. 734 2DE Label: RSNVAMRJ Description: An IUCV message was sent and rejected by the communications partner. 735 2DF Label: RSNMIFTY Label: RSNMIFTY Description: The file type must be specified if the Description: The file type must be specified if the sending system is the remote system. sending system is the remote system. 736 2E0 Label: RSNTPLAB Description: One of the following occurred: Ÿ 'xFTYPE=LAB' was requested and an unlabeled tape was loaded Ÿ 'xFILEORG=PS' and 'xLABEL=SL' were requested and an unlabeled tape was loaded Ÿ 'xFTYPE=UNLAB' was requested and a labeled tape was loaded Ÿ 'xFILEORG=PS' and 'xLABEL=NL' were requested and a labeled tape was loaded. Specify 'xFTYPE=LAB' or 'xFILEORG=PS' and 'xLABEL=SL' for a labeled tape and 'xFYTPE=UNLAB' or 'xFILEORG=PS' and 'xLABEL=NL' for an unlabeled tape. 800 320 Label: RSNNDCON Description: Type of data conversion is not supported. 801 321 Label: RSNEXCON Description: Data conversion exception. 804 324 Label: RSNDCAEX Description: Output area for data conversion too small. 808 328 Label: RSNNRVIO Description: Naming rule violation. 812 32C Label: RSNACVIO Description: Access violation.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 143

Figure 4 (Part 33 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 1000 3E8 Label: None Label: None Description: This reason code is issued when the Description: Queue handler command rejected by remote system does not issue reason codes. For pre-queuing user-exit routine; incorrect reason code example, if a request to a remote NetView FTP/400 passed to NetView FTP. system is rejected, the remote system issues return The pre-queuing user-exit routine rejected the queue code 16; but no reason code. NetView FTP sets the handler command but passed an incorrect reason code reason code in the server log to 1000. to NetView FTP. NetView FTP set the reason code to 1000. There is probably an error in the pre-queuing user-exit routine. 1nnn Label: None Label: None Description: Error occurred on remote server. Description: Queue handler command rejected by pre-queuing user-exit routine. The local server was informed by the remote server that an error occurred at the remote system The reason The pre-queuing user-exit routine rejected the queue code for the error at the remote system is represented handler command and passed the code nnn to NetView by the number nnn, which is one of the other reason FTP. codes in this table. 2000 7D0 Label: RSOSNOSI Description: The RCE control block is not marked valid for an OSI request (the field RCESVTA has not been set). It is possible that an SNA file-transfer request has been sent to the OSI server. 2001 7D1 Label: RSOSSNAV Description: The RXB control block that is passed to the OSI server does not contain an OSI section. It is possible that an SNA file-transfer request has been sent to the OSI server. 3000 668 Label: RSOSURAC Description: SAF permission for user violated. You do not have sufficient SAF authority to process the specified file-transfer request. Contact your SAF system administrator. 3010 6C2 Label: RSOSORAC Description: SAF permission for OSI/File Services violated. Either the OSI server or OSI/File Services do not have sufficient authority to process the file-transfer request. Contact your SAF system administrator. 3020 6CC Label: RSOSUCAP Description: You are not allowed to perform the transfer on the specified filestore because the capability of the filestore does not match that of the request. The request demands more capability than the filestore can provide. Contact your system administrator. 3030 6D6 Label: RSOSUFAC Description: You are not allowed to perform the transfer on the specified filestore because of the value specified by the filestore access parameter that is configured in the local resource directory. Contact your system administrator.

144 NetView FTP Messages and Codes

Figure 4 (Part 34 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 3032 6D8 Label: RSOSMFLE Description: File entry missing and cannot be added. The local resource directory entry for the specified file is not recorded in the local resource directory and cannot be temporarily entered by the OSI server. 3100 C1C Label: RSOSACCP Description: The access control specified is not sufficient for COPY. The access control action elements do not allow sufficient access rights to perform the read or read attributes transfer actions for the COPY function. Refer to OSI/File Services for MVS Programming Guide for further details. 3110 C26 Label: RSOSACMV Description: The access control specified is not sufficient for MOVE. The specified access-control-action elements do not allow sufficient access rights to perform read, read attributes, or delete transfer actions for the MOVE function. Refer to OSI/File Services for MVS Programming Guide for further details. 3120 C30 Label: RSOSSTMS Description: The contents of the String Significance and Maximum String Length parameters do not match. Refer to OSI/File Services for MVS Programming Guide for further details. 3130 C3A Label: RSOSDOCT Description: The value specified for the Document Type parameter is incorrect. 3140 C44 Label: RSOSMSTR Description: The value specified for the Maximum String Length parameter is incorrect. 3150 C4E Label: RSOSSSIG Description: The value specified for the String Significance parameter is incorrect. 3160 C58 Label: RSOSUCLA Description: The value specified for the Universal Class parameter is incorrect. 4100 1004 Label: RSOSCANR Description: The cancel request cannot be performed because of the internal status of the request. 4832 12E0 Label: RSOSDTUC Description: The contents of the Document Type and Universal Class parameters do not match. Refer to OSI/File Services for MVS Programming Guide for further details. 4846 12EE Label: RSOSPAMM Description: The Permitted Actions and Access Control parameters do not match. 5010 1392 Label: RSODSNA Description: The requested file is not available.

Chapter 2. NetView FTP ABEND, Return, and Reason Codes 145

Figure 4 (Part 35 of 35). Reason Codes from File Transfers and Queue Handler Commands

Reason Code From File Transfers or Partition From Queue Handler Commands Dec Hex (Issued with Return Codes 0 to 20) (Issued with Return Codes 0 and 24 to 48) 5100 13EE Label: RSOSRNOF Description: The action on the request failed because it is not available in OSI/File Services. 5200 1450 Label: RSOSRTRM Description: The request has already terminated and cannot be canceled.

146 NetView FTP Messages and Codes

Glossary

This glossary defines many of the terms and abbreviations Advanced Function Feature. A set of extra functions that used with NetView FTP. If you do not find the term you are extend the capabilities of the NetView FTP V1 MVS base looking for, refer to the Dictionary of Computing, New York: product. McGraw-Hill, 1994. advanced peer-to-peer networking. Data communications Access Method Services. A utility program that defines support that routes data in a network between two or more VSAM data sets and allocates space for them, converts APPC systems that are not directly attached. indexed sequential data sets to key-sequenced data sets with indexes, modifies data set attributes in the catalog, advanced program-to-program communication. An facilitates data set portability between operating systems, implementation of the SNA/SDLC LU 6.2 protocol that allows creates backup copies of data sets and indexes, helps make interconnected systems to communicate and share the inaccessible data sets accessible, and lists data set records processing of programs. and catalog entries. AET. Application Entity Title. ACF/VTAM. Advanced Communications Function for the AFF. Advanced Function Feature. Virtual Telecommunications Access Method. alias. An alternative name for a member of a partitioned active request. A request that is presently being scheduled data set. or for which the corresponding file transfer is in progress. AMS. Access Method Services. adaptive compression. A method by which the amount of storage required for data can be reduced by replacing APAR. Authorized program analysis report. character strings that are repeated with references to a directory of such character strings. APF. Authorized Program Facility. added request. A request that has been added to the APL. Application program parameter list. request queue. APPC. Advanced program-to-program communication. administrator query command. A type of command that causes NetView FTP to retrieve information about the Application Entity Title. The name by which an OSI request queue or the requests in it; the information retrieved application (and filestore) can be addressed by remote users. is intended for the NetView FTP administrator. Contrast with By contrast, the local name of the filestore is the filestore user query command. nickname. administrator query record. A record containing the application program parameter list. A control block used information NetView FTP retrieves when an administrator by application programs to pass parameter values to issues an administrator query command. Contrast with user NetView FTP. query record. application program parameter list extension. A control adopted authority. When a program is created, it can block used by application programs to pass parameter values specify that the program always runs under the program to NetView FTP; a supplement to the application program owner’s user profile. A user does not need authority parameter list. specifically given to him for the objects used by the program, but uses (adopts) the program owner’s authority. The user APPN. Advanced peer-to-peer networking. has authority for the objects used by the program only when APX. Application program parameter list extension. he is running the program and other programs called by the program. attended mode. An operating mode of NetView FTP for Workstations that assumes that a user at a workstation Advanced Communications Function for the Virtual expects to be informed about the success of transfers and is Telecommunications Access Method. An IBM licensed available to load devices such as diskettes or tapes. program that controls communication and the flow of data in Contrast with unattended mode. an SNA network. It provides single-domain, multiple-domain, and interconnected network capability. VTAM runs under automatic logon retry. NetView FTP’s method for MVS, VSE, and VM/SP, and supports direct control eventually establishing a conversation with a remote system. application programs and subsystems such as NetView FTP It is used when a server cannot initiate a conversation with a and VSE/POWER. server at a remote system because:

 Copyright IBM Corp. 1988, 1994 147

Ÿ All the servers at the remote system are busy with other callback. In the AIX operating system, a procedure that is transfers called if and when certain specified conditions are met. This is accomplished by specifying the procedure in a callback Ÿ None of the servers at the remote system has been list. started Ÿ ACF/VTAM is temporarily unable to find a path between callback list. (1) A list of procedures that are called if and the two servers. when certain specified conditions are met. (2) In the program IBM AIXwindows Environment/6000, individual The server at the local system automatically changes the widgets can define callback lists. status of the request from active back to waiting, and goes on to process the next request in the request queue (MVS, CCB. Command control block. VSE, or VM) or request database (OS/400). Later, NetView FTP tries again to process the request. It keeps trying until it CCI. Common control block insertion. succeeds in initiating a conversation. CCSID. Coded character set identifier. automatic transfer restart. NetView FTP’s method for automatically restarting a file transfer that was interrupted. In CCW. Channel command word. the following situations, NetView FTP is not able to recover a conversation: CDC. Character data conversion.

Ÿ The queue handler or server at either system is CDRA. Character Data Representation Architecture. terminated CDRM. Cross-domain resource manager. Ÿ The server at either system cannot allocate the file being transferred CDRS. Cross-domain resource. Ÿ A pre-transfer user-exit routine at either system rejected the file transfer character data. Data in the form of letters, numbers, and special characters, such as punctuation marks, that can be There is a severe or prolonged conversation outage. Ÿ read by the human eye. However, when you create a request you can specify that if one of these situations arises, NetView FTP is to change the Character Data Representation Architecture. An IBM status of the request back to waiting. The servers at your architecture that defines a set of identifiers, services, system then periodically reprocess the request until one of supporting resources, and conventions to achieve a them succeeds in restarting the transfer. consistent representation, processing, and interchange of graphic character data in SAA environments. basic partitioned access method. An access method that can be used to create program libraries in direct-access character literal. A symbol, quantity, or constant in a storage for convenient storage and retrieval of programs. source program that is itself data, rather than a reference to data. basic sequential access method. An access method for storing or retrieving data blocks in a continuous sequence, checkpoint. A point at which information about the status of using either a sequential access or a direct access storage a file transfer is recorded. If the file transfer is interrupted, device. NetView FTP can use this information to resume the file transfer from a point near where the interruption occurred BIND. Bind Session. instead of from the beginning of the file.

Bind Session. In SNA, a request to activate a session checkpoint data set. A data set that contains information between two logical units. about the current status of an active file transfer. If the file transfer is interrupted, NetView FTP can use this information blocked request. A waiting request that is trapped in the to resume the file transfer from a point near where the queue. The request was passed to the queue handler at a interruption occurred instead of from the beginning of the file. time when there was enough CSA storage available to NetView FTP to do so. However, in the meantime, the limit checkpoint file. A synonym for checkpoint data set. of the amount of CSA storage available to NetView FTP was reduced and is not enough to allow the queue handler to checkpoint record. A record of a checkpoint data set or pass the request to a server for processing. The request file. One checkpoint record contains the information needed cannot be processed until the limit of the amount of CSA to restart one file transfer from a checkpoint. storage available to NetView FTP is raised. checkpoint/restart data set. A deprecated term for BPAM. Basic partitioned access method. checkpoint data set.

BSAM. Basic sequential access method. checkpoint/restart record. A deprecated term for checkpoint record.

148 NetView FTP Messages and Codes

class. See server class. CP. Control point. client. On a local area network, a workstation that requests CP-CP sessions. The parallel sessions between two service from a server workstation. control points, using LU 6.2 protocols.

CLIST. Command list. Cross-domain resource. In VTAM programs, synonym for other-domain resource. Coded character set identifier. In NetView FTP, an identifier that represents a set of graphic characters and their Cross-domain resource manager. The functions of the code point assignment. The coded character set identifier system services control point (SSCP) that control initiation defines how characters are mapped to decimal values. and termination of cross-domain resources. command control block. A control block that contains cryptographic key. A value used to encrypt and decrypt details of the queue handler command to be carried out. data transmitted in an LU-LU session that uses cryptography. command list. A list of commands and control statements cryptography. The transformation of data to conceal its that is assigned a name. When the name is invoked (as a meaning. command) the commands in the list are executed. CSA. Common service area. common service area. In MVS, a part of the common area that contains data areas that are addressable by all address current request. The request currently being created or spaces. During use, these areas are protected by the key of changed by the user of the NetView FTP panels. the requester. daemon. In the AIX operating system, a program that runs completion user exit. Deprecated term for post-transfer unattended to perform a standard service. user exit. daemon process. In the AIX operating system, a process compression. A technique for converting data into a form begun by the root user or the root shell that can be stopped that requires less storage space and less transmission time only by the root user. Daemon processes generally provide than its original form. Contrast with decompression. See services that must be available at all times. also SNA compaction and SNA compression. DASD. Direct-access storage device. condition code. A 4-digit decimal value derived from the data control block parameters. The following parameters: value a server places in register 15 before returning control Record Format, Logical Record Length, and Physical Block to the operating system. The digits of the condition code Size. consist of the server return code and, for a server running in single mode, the file-transfer return code. data set control block. A control block containing specifications for data sets that are to be created. continuous mode. A server running mode in which a server continues running after it has transferred a file. data transfer message unit. The message unit used to send the data object. control language. The set of all commands with which a user requests system functions. DCB parameters. Data control block parameters. control point. A component of an APPN or LEN node that decompression. A technique for converting compressed manages the resources of that node. In an APPN node, the data back into its original form. Contrast with compression. CP is capable of engaging in CP-CP sessions with other APPN nodes. In an APPN network node, the CP also default first qualifier. Server initialization parameter. provides services to adjacent end nodes in the APPN Sometimes referred to as the GID initialization parameter. network. The server uses this parameter as the first qualifier when it creates a name for the data set. control statement. A statement that controls or affects the running of a program. For example, default value. The value that is assigned to a parameter by NOTAFTER=(‘21:34’,‘94/12/25’) is a control statement that a program if no value is specified by a user. assigns the value (‘21:34’,‘94/12/25’) to the parameter represented by the keyword NOTAFTER. deferred request. A waiting request that is temporarily trapped in the queue. CSA storage was obtained for conversation. In SNA, a connection between two NetView FTP, but not enough for the queue handler to pass transaction programs over an LU-LU session that lets them the request to a server for processing. The request is communicate with each other while processing a transaction. processed later, when more CSA storage is available to NetView FTP.

Glossary 149

delay time. The amount of time a finished request stays in Exit(n) Message Unit. The message unit used to convey the request queue before rebuilding the request queue information provided by the Post-Transfer User Exit routine n causes it to be deleted automatically. (where n is 1 or 2) of the sender to the receiver. direct transfer. Transfer of data from one file to another file extended specify task abnormal exit. A macroinstruction without first storing the data in an intermediate file. that allows a user to intercept a scheduled abnormal termination. direct-access storage device. A storage device for which access time is effectively independent of the location of the FAT. File allocation table. data being accessed. FBA. Feedback area. directory file. In the AIX operating system, a file that contains information the system needs to access all types of feedback area. An area of storage containing information files. related to a queue handler command. For example, an FBA can contain a request control block, a query data area, or a distribution-service component. A component of NetView server data area. FTP VM that handles communication with the queue handler (such as retrieving requests to be processed), and with the file allocation table. A table used by DOS and OS/2 to network (such as establishing conversations and transferring allocate space on a disk for a file and to locate and chain files). In NetView FTP VM, each server consists of one together parts of the file that may be scattered on different distribution-service component and up to 32 file-service sectors so that the file can be used in a random or components. sequential manner. distribution-service machine. With NetView FTP VM, a file group. One or more files that reside on one system. virtual machine in which a distribution-service component For example, all files that are stored in the same directory or runs. whose file names consist of partly matching character strings are considered a file group. DSCB. Data set control block. file pool. A collection of minidisks managed by SFS. It DTMU. Data transfer message unit. contains user files and directories and associated control information. Many user’s files and directories can be dynamic allocation. The allocation of a file when it is contained in a single file pool. needed, not in advance. Contrast with job allocation. file transfer. The sending and receiving of the contents of a encrypt. To scramble data or convert data to a secret code file. that masks the meaning of the data to any unauthorized recipient. File Transfer Access and Management. A set of programs, such as OSI/File Services, which conforms to entry sequence. The order in which records are physically FTAM standards to manage and transfer files over an OSI arranged in auxiliary storage. network. entry-sequenced data set. A data set whose records are file-service component. A component of NetView FTP VM loaded without respect to their contents, and whose relative that handles file access and the taking of checkpoints. In byte addresses cannot change. NetView FTP VM, each server consists of one distribution-service component and up to 32 file-service ESDS. Entry-sequenced data set. components. ESTAE. Extended specify task abnormal exit. file-transfer completion message. A message, sent by a server to a user after a file transfer, which describes the exceptional checkpointing. To take a checkpoint when outcome of a file transfer. certain types of errors occur. file-transfer report. A file, sent by a server to a user after a exchange identification. The ID that is exchanged with the file transfer which describes the outcome of a file transfer. remote physical unit when an attachment is first established. file-transfer request. A list of parameters and their values exclude members. To choose those members of a PDS that tell NetView FTP (1) that it is to transfer a file from one that are not to be transferred. Contrast with select members. system to another, and (2) about the file transfer and the exit. A point in a program at which control is passed to sending and receiving data sets. another program. filestore. See local filestore and remote filestore. exit routine. A routine that receives control when a specified event occurs.

150 NetView FTP Messages and Codes

filestore nickname. The name of the filestore at the local hierarchic direct access method. A database access level. It is defined by the filestore owner when registering method that uses algorithmic addressability of records in a the filestore in the LRD, and is used by authorized local hierarchic direct organization. users to access that filestore. hierarchic indexed sequential access method. A filestore owner. The single user, local or remote, who has database access method that uses indexed access to created the filestore and who controls the passwords for records in a hierarchic sequential organization. accessing it and the filestore accessibility. Each OSI/File Services user owns one filestore. High Performance File System. A file organization available under OS/2. filestore subset. A subdivision of the local filestore. It is the first qualifier of the MVS data-set name. Each local file is HISAM. Hierarchic Indexed Sequential Access Method. registered in the LRD under a related filestore subset, which HPFS. High Performance File System. in turn belongs to a local filestore. ICCF. Interactive computing and control facility. filter. In the AIX operating system, a command that reads standard input data, modifies the data, and sends it to the ICF. Intersystem communications function. display screen. IMS/VS. Information Management System/Virtual Storage. finished request. A request for which the corresponding file transfer has finished, whether successfully or unsuccessfully. independent LU. A logical unit (LU) that does not receive an ACTLU over a link. Such LUs can act as primary logical FIU. File Interchange Unit. units (PLUs) or secondary logical units (SLUs) and can have one or more LU-LU sessions at a time. FTAM. File Transfer Access and Management. INI file. See initialization file. FTP level. A character that represents the level of sophistication of an FTP or NetView FTP program. initialization file. A file that contains parameters that determine how NetView FTP for Workstations starts running. FTP V2. File Transfer Program Version 2 Release 2. input field. An area on a panel in which data is entered. FSB. NetView FTP shared block. instance. In the AIX operating system, the concrete FSBX. NetView FTP shared block extension. realization of an abstract object class. An instance of a GDG. Generation data group. widget or gadget is a specific data structure that contains detailed appearance and behavioral information that is used generation data group. A collection of data sets kept in to generate a specific graphical object on-screen at run time. chronological order; each data set is a generation data set. Internet. A wide area network connecting thousands of generation data set. One generation of a generation data disparate networks in industry, education, government, and group. research. The Internet network uses /IP as the standard for transmitting information. GETVIS area. Storage space within a partition or the shared virtual area, available for dynamic allocation to Internet Protocol. A protocol used to route data from its programs. source to its destination in an Internet environment.

GID initialization parameter. See default first qualifier. Intersystem communications function. Communications between application programs on an AS/400 system and an GUI. The graphical user interface of NetView FTP for application program on a remote system are accomplished Workstations. using the AS/400 system intersystem communications function (ICF) and the underlying support. handle. (1) In the Advanced DOS and OS/2 operating systems, a binary value created by the system that identifies IP. Internet Protocol. a drive, directory, and a file so that the file can be found and opened. (2) In the AIX operating system, a data structure ISPF. Interactive System Productivity Facility. that is a temporary local identifier for an object. JCL. Job control language. HDAM. Hierarchic direct access method. JES. Job entry subsystem. hex. Abbreviation of hexadecimal. job allocation. The allocation of a file by a server startup job. The allocation takes place when a server is started,

Glossary 151

which is before (sometimes long before) the file transfer logical unit name. A name used to represent the address takes place. Contrast with dynamic allocation. of a logical unit. job control language. A control language used to identify a LRD. Local Resource Directory. job to an operating system and to describe the job’s requirements. LU. Logical unit. key sequence. In VSAM, the collating sequence of data LU name. Logical unit name. records as determined by the value of the key field in each LU 0 conversation. The type of conversation NetView FTP record. uses for file transfers between a node where NetView FTP key-sequenced data set. A VSAM data set whose records V2.1 MVS, NetView FTP V1 VM, or NetView FTP V1 VSE is are loaded in key sequence and controlled by an index. installed and a node where NetView FTP V1 MVS or FTP V2 is installed. keyword. A part of a control statement that consists of a specific character string. LU-LU session. In SNA, a session between two logical units (LUs) in an SNA network. KSDS. Key-sequenced data set. manual transfer restart. NetView FTP’s method for LAN. Local area network. allowing a user to restart a file transfer that was interrupted by submitting a restart request for that file transfer. LAN gateway. A functional unit that connects a local area network with another network using different protocols. master password. A password, set by the NetView FTP system programmer that lets those who specify it query, LDS. Linear data set. modify, or delete any request in the request queue, regardless of whether or not it is password-protected, and LEN node. Low-entry networking node. That is a node that regardless of who added it to the queue. provides a range of end-user services, attaches directly to other nodes using peer protocols, and derives network message area. The area of storage to which NetView FTP services implicitly from an adjacent APPN network node, that writes the messages it issues to an application program. is, without the direct use of CP-CP sessions. mode. The session limits and common characteristics of the linear data set. A VSAM data set that contains data but no session associated with advanced program-to-program control information. A linear data set can be accessed as a (APPC) devices managed as a unit with a remote location. byte-string in virtual storage. A linear data set has no records and a fixed control interval size of 4096 bytes. mode description. A system object created for advanced program-to-program (APPC) devices that describes the local. Refers to one’s own system. session limits and the characteristics of the session, such as the maximum number of sessions allowed, maximum number local area network. A data network located on the user's of conversations allowed, and other controlling information for premises in which serial transmission is used for direct data the session. communication among workstations. MVS node. A node with MVS as its operating system. local filestore. A collection of local files. Each local filestore is registered in the LRD with a filestore nickname for MVS system. A system with MVS as its operating system. local access, and a filestore AET for remote access. NETBIOS. Network Basic Input/Output System. An Local Resource Directory. The file containing information operating system interface for application programs used on on local users, local filestores, filestore subsets, and local IBM personal computers that are attached to the IBM files necessary for OSI/File Services to run initiator and Token-Ring Network. responder functions. NetView FTP administrator. Someone who knows the local-request handler. A server subtask that can process a master password. A NetView FTP administrator can query, request submitted at the local system and can initiate a delete, modify, hold, or release any request regardless of conversation. whether it is password-protected, and regardless of who submitted it. log file. A file to which a NetView FTP component writes messages. NetView FTP AIX. NetView File Transfer Program Server for AIX and NetView File Transfer Program Client for AIX. logical unit. In SNA, a port through which an end user accesses an SNA network. Each NetView FTP server is a NetView FTP application program. An application program logical unit. that adds, queries, modifies, or deletes a request, or that retrieves information about NetView FTP.

152 NetView FTP Messages and Codes

NetView FTP batch job. A batch job that adds, queries, not-before time. The time before which NetView FTP is not modifies, or deletes a request, or that retrieves information to process a request. about NetView FTP. numeric literal. A numeric character or string of numeric NetView FTP Client for DOS and Windows. NetView File characters whose value is implicit in the characters Transfer Program &clw.. themselves; for example, 777 is the literal as well as the value of the number 777. NetView FTP MVS. NetView File Transfer Program for MVS. octal. Pertaining to a selection, choice, or condition that has eight possible different values or states. NetView FTP OS/2. NetView File Transfer Program Server/2 and NetView File Transfer Program Client/2. OEM. Original equipment manufacturer.

NetView FTP/400. NetView File Transfer Program for Open Systems Interconnection. The seven-layer OS/400. communications architecture used for the definition of protocol standards for networks. NetView FTP partition. A VSE partition that contains the main components of NetView FTP VSE. operation mode. See attended mode and unattended mode. NetView FTP shared block. An area of CSA storage that is used to pass data between the components of NetView FTP. operational key. Deprecated term for cryptographic key. Any data that does not fit in the FSB is put in the NetView FTP shared block extension. Original equipment manufacturer. A manufacturer of equipment that may be marketed by another manufacturer. NetView FTP shared block extension. An area of ECSA storage that is used to pass data between the components of originator ID. A string of characters that identifies the job, NetView FTP. It contains any data that does not fit in the started task, or user that added a request to the request NetView FTP shared block. queue.

NetView FTP VM. NetView File Transfer Program for VM. OSI. See Open Systems Interconnection.

NetView FTP VSE. NetView File Transfer Program for VSE. other-domain resource. A recommendation for a logical unit that is owned by another domain and is referenced by a network. An interconnected group of nodes. symbolic name, which can be qualified by a network identifier. network drive. With NetView FTP, it is a shared resource that can be accessed from each workstation in the LAN. panel. A predefined image displayed on a terminal screen. network job entry facility. A facility that uses the network panel flow. The way in which panels are chained together job-interface (NJI) protocols to allow a computer system to so that a user can move from one to another. communicate with other computer systems in a network. panel layout. The way in which the text and the input fields NFTP directory. The directory that contains the NetView on a panel are arranged. FTP/2 product files. partitioned data set. A data set in direct access storage NFTPWORK directory. The directory that contains all that is divided into partitions, called members, each of which NetView FTP/2 work files, for example, the NetView FTP can contain a program, part of a program, or data. message and log files. PCF. Programmed Cryptographic Facility. NJE. Network job entry. PDS. Partitioned data set. NJI. Network job-interface. path information unit. In SNA, a message unit consisting node. An endpoint in a link, or a junction common to two or of a transmission header (TH) alone, or a TH followed by a more links in a network. A deprecated term for server group. basic information unit (BIU) or a BIU segment. node ID. Deprecated term for server group. phase. The smallest unit of executable code that can be loaded into virtual storage. node ID table. Deprecated term for server group table. ping. The use of the ping command to send an echo not-after time. The time after which NetView FTP is not to request to a network host or gateway. process a request. port. With NetView FTP, the communication end point in TCP/IP. A port is identified by a port number.

Glossary 153

port number. In TCP/IP, a 16-bit number used to queued sequential access method. An extended version communicate between TCP/IP and a higher-level protocol or of the basic sequential access method (BPAM). When this application. method is used, a queue is formed of (1) input data blocks that are awaiting processing or (2) output data blocks that post-conversation user exit. A user exit that passes have been processed and are awaiting transfer to auxiliary control to a routine at the system at which the file-transfer storage or to an output device. request originated. This routine is to run just after the servers terminate their conversation. raw device. In the AIX operating system, a device that treats data I/O as a continuous stream, without consideration post-transfer user exit. A user exit that passes control to a for the data’s logical structure. For example, I/O for fixed routine that is to run just after a server closes a file that has disks and streaming tapes occurs in units of bytes that have been transferred. no relationship to characters. pre-queuing user exit. A user exit that passes control to a RCB. Request control block. routine that is to run just after a request is submitted to NetView FTP and just before NetView FTP adds the request RCE. Request control element. to the queue. RDF. Request definition file. pre-transfer user exit. A user exit that passes control to a routine that is to run just before a server opens a file that is reason code. A value issued by a program that gives to be transferred. additional information about a situation described by a return code. preparation user exit. Deprecated term for pre-transfer user exit. receiving data set. A data set in which a copy of a file that has been sent using NetView FTP has been placed. process (a request). To obtain and try to carry out (a Contrast with sending data set. request). receiving file. A data set in which a copy of a file is placed program temporary fix. A temporary solution to bypass of that has been sent using NetView FTP. Contrast with a problem diagnosed by IBM as resulting from a defect in a sending file. current unaltered release of a program. receiving system. The NetView FTP system that receives PTF. Program temporary fix. the file being transferred.

PUBX. Physical Unit Control Block Extension. regular checkpointing. To take a checkpoint at specified regular intervals. QDA. Query data area. regular file. In the AIX operating system, a file that contains QRA. Query response area. data. A regular file can be a text file or a binary file. Text files contain information readable by the user. This QSAM. Queued sequential access method. information is stored in ASCII. Binary files contain information readable by the computer. QSR. Query Status Record. relative record data set. In VSAM, a data set whose query (a request). To ask for information about (a request). records are loaded into fixed-length slots and are query data area. The area of ECSA storage into which represented by the relative-record numbers of the slots they NetView FTP places either user query records or occupy. administrator query records. remote. Pertaining to a system other than one’s own. query response area. The area of storage into which remote filestore. A collection of remote files. OSI/File NetView FTP places information it retrieves for an application Services users can access a file residing in a remote system program. only if they specify the filestore AET of the remote filestore, queue handler. A NetView FTP component that controls and the OSI file name of the related file. access to the request queue. In NetView FTP MVS, the remote-request handler. A server subtask that can accept queue handler also controls all other NetView FTP a conversation initiated by a local-request handler at a components and all communication with the operator. remote system. queue handler command. A command that a component report. Synonym for file-transfer report. of NetView FTP issues to the queue handler when it wants the queue handler to do something. report recipient. A user to whom a server sends a file-transfer report.

154 NetView FTP Messages and Codes

request. Synonym for file-transfer request. indefinite number of file transfers, however, these file transfers must all be initiated by servers at remote systems. request class. A deprecated term for server class. responding system. The system responding to a request control block. A control block that contains some file-transfer request. or all of a file-transfer request. Data that does not fit in the RCB is put in the request control block extension. return code. A value issued by a program that describes the outcome of an operation performed by that program. request control block extension. A control block that contains data that does not fit in the request control block. root. In the AIX operating system, the user name for the system user with the most authority. request control element. An element of the request queue directory. RRDS. Relative record data set. request database. In NetView FTP/400, the database in RTM. Recovery Termination Manager. which NetView FTP stores all requests. RU. Request unit. request definition file. A file containing NetView FTP control statements, that is, all NetView FTP parameters with RXB. Request control block extension. their appropriate values that are necessary for a file transfer. SAF. System authorization facility. request handler. A server subtask. See also SAM. Sequential access method. remote-request handler. SAS. Spool Access Services. request number. A number that the queue handler assigns to a request when it adds the request to the request queue saved request. A request that has been created with the and that is used to identify the request. NetView FTP panels and that has then been saved in an ISPF table data set. request password. A character string, assigned by a user to a request, that prevents users sharing that user’s scheduling a request. Determining which request is to be originator ID from deleting or modifying that user’s waiting obtained, obtaining it, and passing it to a server. and active requests. If a user specifies a request password for a request, another user with the same originator ID must scroll amount. The amount that the list on a panel is specify either the request password or the master password scrolled up or down when you enter the UP or DOWN to be able to delete or modify the request while it is waiting, command. or to delete the request while it is active. SDA. Server data area. request priority. A number, assigned by a user to each request, that determines the order in which a server is to SDMU. Source description message unit. process it. When a server is ready to process a request and several requests are eligible, the server processes the SDWA. System Diagnostic Work Area. request with the highest priority first. select members. To choose those members of a PDS that request queue. In NetView FTP for MVS, VSE, or VM, the are to be transferred. Contrast with exclude members. file in which NetView FTP stores requests that have been sending data set. A data set, a copy of which is to be submitted for processing. transferred using NetView FTP. Contrast with receiving data request queue directory. A directory of the contents of the set. request queue. sending file. A file of which a copy is to be transferred request unit. A message unit that contains control using NetView FTP. Contrast with receiving file. information, end-user data, or both. sending system. The NetView FTP system stores the file request-queue user exit. Deprecated term for pre-queuing that will be transferred to the receiving system. user exit. sequential access method. See basic sequential access requesting system. The system where the file-transfer method. request has been initiated. server. (1) A NetView FTP component that establishes or resident session partner. An FTP V2 MVS or FTP V2 accepts conversations and that transfers files. (2) With VSE server that runs continuously and can perform an NetView FTP for Workstations, a NetView FTP Server program that serves as a gateway for one or more NetView FTP Client programs.

Glossary 155

server class. A number or letter, assigned by a user to a socket. In the AIX operating system: (1) A unique host request, that specifies which servers can process that identifier created by the concatenation of a port identifier with request. a TCP/IP address. (2) A port identifier. (3) A 16-bit port number. (4) A port on a specific host; a communications end server data area. The area of ECSA into which NetView point that is accessible through a protocol family’s addressing FTP places information about a server or servers. mechanism. A socket is identified by a socket address. See also socket address. server group. A group of servers (logical units). socket address. In the AIX operating system, a data server group table. A data set that specifies which servers structure that uniquely identifies a specific communications make up each server group, and that contains information end point. A socket address consists of a port number and a about each server. network address. It also specifies the protocol family. server modification area. An area of storage that contains SRMU. Statistics report message unit. the modifications to a server’s session parameters. special file. In the AIX operating system, a file that defines session. In SNA, a logical connection between two a FIFO (first-in, first-out) file or a physical device. network-addressable units. SSCP. System Services Control Point. SFS. Shared file system. statistics report message unit. A message unit sent by SFS directory. A group of files. SFS directories can be the target (receiver of the file), at the end of the file transfer. arranged to form a hierarchy in which one directory can contain one or more subdirectories as well as files. status. The state of a request in the request queue (MVS, VSE, or VM) or request database (OS/400). In NetView FTP shared file pool. See file pool. for MVS, VSE, or VM, the possible statuses are waiting, active, and finished. In NetView FTP/400, the possible shared file system. A part of CMS that lets users organize statuses are held, waiting, active, finished, and failed. their files into groups known as directories, and selectively share those files and directories with other users. status data area. The area of ECSA into which NetView FTP places details of the status of a server or servers. single mode. A server running mode in which a server stops running after it has transferred a file (or attempted to Storage Management Subsystem. An MVS subsystem transfer a file and failed). that helps automate and centralize the management of DASD storage. SMS provides the storage administrator with slot. A space in the request queue directory that is able to control over data class, storage class, management class, hold a request control element (RCE). storage group, and ACS routine definitions. SMA. Server modification area. submit (a request). To give (a request) to NetView FTP so SMF. System management facilities. that NetView FTP can add it to the request queue.

SMS. Storage Management Subsystem. superuser. In the AIX operating system, the user who has unrestricted authority to access and modify any part of the SNA. Systems Network Architecture. operating system, usually the user who manages the system.

SNA compaction. The transformation of data by packing supervisor call instruction. An instruction that interrupts a two characters in a byte that normally would only hold one running program and passes control to the supervisor so that character. the supervisor can perform the service indicated by the instruction. SNA compression. The replacement of a string of up to 64 repeated characters by an encoded control byte to reduce SVA. Shared Virtual Area. the length of the string. SVC. Supervisor call instruction. SNA network. In SNA, the part of a user-application network that conforms to the formats and protocols of symbolic constant. A data item that has an unchanging, Systems Network Architecture. It enables reliable transfer of predefined value. data among end users and provides protocols for controlling system authorization facility. At an MVS or VM location, a the resources of various network configurations. The SNA generic interface to security products that is provided by the network consists of network addressable units, boundary operating system. In this way, an installation has the function components, and the path control network. possibility to run a security program, such as IBM RACF. SNA node. A node that supports SNA protocols.

156 NetView FTP Messages and Codes

System management facilities. An optional control unused slot. A slot that does not contain a request control program for MVS that provides the means for gathering and element (RCE). recording information that can be used to evaluate system usage. user exit. A point in an IBM-supplied program at which a user-exit routine is given control. system services control point. In SNA, a focal point within an SNA network for managing the configuration, coordinating user interface. Hardware, software, or both that allows a network operator and problem determination requests, and user to interact with and perform operations on a system or providing directory support and other session services for program. end users of the network. Several SSCPs, cooperating as user query command. A type of command that causes peers, can divide the network into domains of control, with NetView FTP to retrieve information about the requests in the each SSCP having a hierarchical control relationship to the request queue; the information retrieved is intended for users physical units within its domain. of NetView FTP. Contrast with administrator query Systems Network Architecture. The description of the command. logical structure, formats, protocols, and operating sequences user query record. A record containing the information for transmitting information units through, and for controlling NetView FTP retrieves when a user issues a user query the configuration and operation of, networks. The layered command. Contrast with administrator query record. structure of SNA allows the origin and ultimate destination of information to be independent of and unaffected by the SNA user-exit routine. An exit routine written by a user. network services and facilities used to transfer that information. user-written file handler. An exit routine, written by a user, that gains access to a file and passes its records to NetView table display panel. A panel that contains a scrollable list. FTP, or that retrieves the records from NetView FTP and writes them to a file. Target Information Message Unit. A message unit sent by the receiving node after it receives an SDMU. A TIMU virtual storage access method. An access method for updates the original request, to inform the sender where to indexed or sequential processing of fixed- and variable-length start or restart sending, and, to convey statistical information. records on direct-access storage devices. The records in a VSAM data set can be organized (1) in logical sequence by TCP. Transmission Control Protocol. means of a key field (key sequence), in the physical TCP/IP. Transmission Control Protocol/Internet Protocol. A sequence in which they are written in the data set (entry set of communication protocols that support peer-to-peer sequence), or (2) by means of a relative-record number. connectivity functions for both local and wide area networks. Virtual Telecommunications Access Method. See TIMU. Target Information Message Unit. Advanced Communications Function for the Virtual Telecommunications Access Method. token-ring network. A network that uses a ring topology, in which tokens are passed in a circuit from node to node. A VM node. A node with VM as its operating system. node that is ready to send can capture the token and insert VM system. A system with VM as its operating system. data for transmission. VSAM. Virtual storage access method. Transfer Request Message Unit. A message unit used to send or receive a file, or to restart a previously interrupted VSE node. A node with VSE as its operating system. file transfer. VSE system. A system with VSE as its operating system. Transmission Control Protocol. A communications protocol used in Internet and in any network that follows the VTAM. Virtual Telecommunications Access Method. See U.S. Department of Defense standards for inter-network Advanced Communications Function for the Virtual protocol. TCP provides a reliable host-to-host protocol Telecommunications Access Method. between hosts in packet-switched communications networks and in interconnected systems of such networks. It assumes waiting request. A request that is waiting to be processed. that the Internet protocol is the underlying protocol. WAN. Wide area network. TRMU. Transfer Request Message Unit. Wide area network. A network that provides unattended mode. An operating mode of NetView FTP for communication services to a geographic area larger than that Workstations that assumes that a user is not available at the served by a local area network and that may use or provide workstation, for example, to load devices such as diskettes public communication facilities. or tapes. Contrast with attended mode.

Glossary 157

wildcard character. Either a question mark (?) or an WTO. Write-to-operator. asterisk (*) used as a variable in a file name or file name extension when referring to a particular file or group of files. XID. Exchange identification.

XnMU. Exit(n) message unit.

158 NetView FTP Messages and Codes

Bibliography

The NetView FTP Library NetView File Transfer Program Server for AIX, NetView File Transfer Program Client for AIX: This manual is part of a library of publications that describe NetView FTP for Workstations: AIX Installation and NetView FTP and explain how to use it. The publications in User’s Guide, SH12-6187 this library are: NetView FTP Parameter Reference, SH12-6052 NetView File Transfer Program for VSE: NetView File Transfer Program Server/2, NetView File Transfer Program Client/2 NetView FTP Licensed Program Specifications, NetView File Transfer Program Client for DOS and GH12-5485 Windows: NetView FTP VSE User’s Guide, SH12-5673 NetView FTP VSE Installation, Operation, and NetView FTP for OS/2, DOS, and Windows Administration, SH12-5674 Workstations: Installation and User’s Guide, NetView FTP Customization, SH12-5482 SH12-6080 NetView FTP Messages and Codes, SH12-5483 NetView FTP Parameter Reference, SH12-6052 NetView FTP Parameter Reference, SH12-6052 The unlicensed manuals with prefix SH are also available as NetView File Transfer Program for VM: softcopy on the following collection kits: NetView FTP General Information, GH12-5480 IBM Networking Softcopy Collection Kit, SK2T-6012 NetView FTP Licensed Program Specifications, IBM Online Library Omnibus Edition: MVS Collection, GH12-5485 SK2T-0710 NetView FTP VM User’s Guide, SH12-5675 IBM Online Library Omnibus Edition: VM Collection, NetView FTP VM Installation, Operation, and SK2T-2067 Administration, SH12-5676 IBM Online Library Omnibus Edition: VSE Collection, NetView FTP Customization, SH12-5482 SK2T-0060 NetView FTP Messages and Codes, SH12-5483 IBM Online Library Omnibus Edition: AIX Collection, NetView File Transfer Program for OS/400: SK2T-2066 NetView FTP General Information, GH12-54801 NetView FTP V1 for OS/400 Licensed Program Specifications, GH12-5777 Related Publications NetView FTP V3 for OS/400 Licensed Program ISO FTAM-IS-Standard Part 3, ISO 8571-3 Specifications, GH12-6176 NetView FTP V1 for OS/400 Installation and User’s ISPF V3 for MVS Dialog Management Services and Guide, SH12-5776 Examples, SC34-4215 NetView FTP V3 for OS/400 Installation and User’s ISPF Dialog Management Services and Examples, Guide, SH12-6177 SC34-4156 NetView File Transfer Program Version 2 for MVS: ISPF V3 for VM Dialog Management Services and NetView FTP Licensed Program Specifications, Examples, SC34-4223 GH12-5485 MVS/DFP V3: Macro Instructions for VSAM Data Sets, NetView FTP V2 MVS User’s Guide, SH12-5656 SC26-4569 NetView FTP V2 MVS Installation, Operation, and MVS/DFP V3: Macro Instructions for Non-VSAM Data Administration, SH12-5657 Sets, SC26-4558 NetView FTP Customization, SH12-5482 NetView FTP Messages and Codes, SH12-5483 MVS/DFP V3.3: System Programming Reference, NetView FTP Parameter Reference, SH12-6052 SC26-4567 MVS/DFP V3.3: Managing Catalogs, SC26-4555 MVS/ESA System Codes, GC28-1664 MVS/ESA System Management Facilities (SMF), GC28-1628 MVS/ESA SPL: Application Development Guide, GC28-1852

1 NetView FTP/400 V1 only.

 Copyright IBM Corp. 1988, 1994 159

MVS/ESA Application Development Reference: Services MVS/XA VSAM Administration: Macro Instruction for Assembler Language Programs, GC28-1642 Reference, GC26-4152 MVS/XA Data Administration: Macro Instruction Reference, GC26-4141 MVS/XA System Codes, GC28-1157 MVS/XA SMF, GC28-1153 MVS/XA System Macros and Facilities Volume 1, GC28-1150 MVS/XA Supervisor Services and Macros, GC28-1154 MVS/XA Catalog Administration Guide, GC26-4138 OSI/File Services for MVS User’s Guide, SH19-6638 OSI/File Services for MVS Programming Guide, SH19-6640 OS/VS1 OS/VS2 MVS Programmed Cryptographic Facility: Installation Reference, SC28-0956 VM/ESA CMS Application Development Reference for Assembler, SC24-5453 VM/ESA CP General User Command Reference for 370, SC24-5433 VM/ESA CP Programming Services for 370, SC24-5435 VM/ESA Group Control System Reference for 370, SC24-5426 VM/ESA System Messages and Codes for 370, SC24-5437 VM/SP Application Development Reference for CMS, SC24-5284 VM/SP CP General User Command Reference, SC19-6211 VM/SP Connectivity Programming Guide and Reference, SC24-5377 VM/SP Group Control System Macro Reference, SC24-5250 VM/SP System Messages and Codes, SC19-6204 VM/SP System Facilities for Programming, SC24-5288 VM/XA SP CP Command Reference, SC23-0358 VM/XA SP CMS Application Program Development Reference, SC23-0402 VM/XA SP CP Programming Services, SC23-0370 VM/XA SP System Messages and Codes Reference, SC23-0376 VM/XA SP Group Control System Command and Macro Reference, SC23-0433 VSE/Advanced Functions 4.1.1 Macro Reference, SC33-6356 VSE/ESA Version 1.3 System Macros Reference, SC33-6516 VSE/ESA Version 1.3 Messages and Codes, SC33-6507 VSE/POWER 4.1 Application Programming, SC33-6374

160 NetView FTP Messages and Codes

VSE/System Package Messages and Codes Version 4 VTAM Programming for LU 6.2, SC31-6410 Volume 1, SC33-6407 VTAM Programming, SC31-6409 Using VSE/VSAM Commands and Macros, SC24-5144

Bibliography 161

Your comments, please ...

NetView File Transfer Program Version 2 for MVS Version 1 for VSE and VM Messages and Codes Publication No. SH12-5483-07

Use this form to tell us what you think about this manual. If you have found errors in it, or if you want to express your opinion about it (such as organization, subject matter, appearance) or make suggestions for improvement, this is the form to use. To request additional publications, or to ask questions or make comments about the functions of IBM products or systems, you should talk to your IBM representative or to your IBM authorized remarketer. This form is provided for comments about the information in this manual and the way it is presented. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. If you mail this form to us, be sure to print your name and address below if you would like a reply. You can also send us your comments using: Ÿ A FAX machine. The number is: +49–7031–166609. Ÿ Internet. The address is: [email protected]. Ÿ IBMLink. The address is: SDFVM1(GADLID). Ÿ IBM Mail Exchange. The address is: DEIBM3P3 at IBMMAIL. Please include the title and publication number (as shown above) in your reply.

Name Address

Company or Organization

Phone No. Your comments, please ... Cut or Fold Along Line SH12-5483-07 IBM

Fold and Tape Please do not staple Fold and Tape

PLACE POSTAGE STAMP HERE

IBM Deutschland Entwicklung GmbH Information Development, Dept. 0446 Postfach 1380 71003 Boeblingen Germany

Fold and Tape Please do not staple Fold and Tape

Cut or Fold SH12-5483-07 Along Line

IBM

Program Numbers: 5686-013 (VSE) 5684-048 (VM) 5685-108 (MVS)

Printed in Denmark by IBM Danmark A/S

SH12-5483-ð7