Messages & Codes

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 usingthe 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 addressbelow.

IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you may address yourcomments to the following address:

IBM Deutschland Entwicklung GmbHInformation 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 appropriatewithout 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 forthin GSA ADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vTrademarks and Service Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWhat Is in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

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

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

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159The NetView FTP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Related 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 IBMintends to make these available in all countries in which IBM operates. Any reference to anIBM 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 servicethat does not infringe any of IBM’s intellectual property rights may be used instead of theIBM product, program, or service. Evaluation and verification of operation in conjunction withother products, except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter in thisdocument. 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 MarksThe following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBMCorporation in the United States or other countries or both:

ACF/VTAM AIX C/370IBM NetView OS/2OS/400 RACF VM/ESAVM/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 TransferProgram (abbreviated to NetView FTP in this book). This book is intended for all users ofNetView FTP. The reader should be familiar with NetView FTP and the operating system itis running under.

What Is in This BookThis book contains information on all messages and codes issued by NetView FTP and itscomponents.

Chapter 1, “NetView FTP Messages”Describes the type of messages issued by NetView FTP and provides a listof all messages issued, together with a description of the message, systemresponse, and required user action.

Chapter 2, “NetView FTP ABEND, Return, and Reason Codes”Lists and describes the ABEND, return, and reason codes for all NetViewFTP components.

Glossary Contains a list of the terms and abbreviations used in the NetView FTPlibrary.

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 (abbreviatedto NetView FTP in this book), and provides a list of all messages stored in the text area ofthe storage dump.

Message FormatThe message format is: DVGnnnc messagetext, where nnn is the message number and cis 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 occupymore than one line. If a message occupies more than one line, NetView FTP repeats thenumber 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 issplit into two or more output lines. A delimiter (comma or blank) breaks each line of amessage 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 isidentical.

Special Characters in MessagesThe following special characters, which can appear in the text of a message, indicate eitherincorrect message changes for national language support, or NetView FTP program errors:

+ Variable name was too long, no blank within 8 characters; variable has beentruncated.

# Variable identifier not numeric in second and third characters.

? Variable in model message not passed to generating module; this charactersubstituted for the variable.

*** Message text exceeds the maximum of 1024 characters; NetView FTPtruncates the message to 1024 characters and substitutes these charactersfor the last three characters in the truncated message.

variables NetView FTP adds variables that are passed to the message generator, butwhich 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, notnecessarily in the form in which they appear in this book.

Copyright IBM Corp. 1988, 1994 1

DVG001I � DVG003I

Changing Message TextYou 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 bookthat applies to your operating system and transfer program.

List of Messages

DVG001I NETVIEW FTP release;SERVER srvname STARTED ON yy/mm/dd AThh:mm:ss;MAINTENANCE LEVEL = mlevel

Explanation: A server started.

release Release level of transfer program.

srvname Server name (MVS or VSE), or user ID orresource ID of the file service component(VM).

yy/mm/dd Date that the server started: yy=year,mm=month, dd=day.

hh:mm:ss Time that the server started: hh=hour,mm=minute, ss=second.

mlevel Program maintenance-level information;maintained by your system administrator.

System Action: Processing continues.

User Action: None.

DVG002I NETVIEW FTP release;SERVER srvname ENDED ON yy/mm/dd AThh:mm:ss;RETURN CODE = retcd

Explanation: A server stopped running.


srvname Server name (MVS or VSE), or user ID orresource ID of the file service component(VM).

yy/mm/dd Date that the server stopped: yy=year,mm=month, dd=day.

hh:mm:ss Time that the server stopped: hh=hour,mm=minute, ss=second.

retcd Server return code.

The server return code shows whether any errorsoccurred while the server was stopping.

System Action: The server stops.

User Action: If the return code is 0, no action isrequired. If the return code is not 0, refer toChapter 2, “NetView FTP ABEND, Return, andReason Codes” on page 109 to find out what itmeans. To help you find out what caused the error,look at all the messages NetView FTP issued. Afteryou find the messages that correspond to the error,take the user actions they prescribe.

DVG003I FILE TRANSFER ENDED FOR REQUESTNUMBER identifierON yy/mm/dd AT hh:mm:ss;RC = retcd;RSN = rsncd

Explanation: A server issues this message at theend of a file transfer.

identifier Request number or name. This can bezero if there is no valid file-transferrequest when the message is issued.

yy/mm/dd Date that the file transfer ended: yy=year,mm=month, dd=day.

hh:mm:ss Time that the file transfer ended: hh=hour,mm=minute, ss=second.

retcd File-transfer return code.

rsncd File-transfer reason code.


User Action: If the file-transfer return code is 0, noaction is required. If the return code is not 0, refer toChapter 2, “NetView FTP ABEND, Return, andReason Codes” on page 109 to find out what itmeans.

The return code 1000 is issued when the remotesystem does not issue reason codes. For example,if a request to a remote NetView FTP/400 system isrejected, the remote system issues return code 16;but no reason code. NetView FTP sets the reasoncode in the server log to 1000. If the return code is> 1nnn, an error occurred on the remote server. Thelocal server was informed by the remote server thatan error occurred at the remote system. The reasoncode for the error at the remote system isrepresented by the number nnn , which is one of thereason codes listed in “NetView FTP Return Codes”on page 109.

To help you find out what caused the error, look atall the messages NetView FTP issued. After youfind the messages that correspond to the error, takethe user actions they prescribe.

2 NetView FTP Messages and Codes

DVG004I � DVG008I

DVG004I FILE TRANSFER STARTED ON LOCALREQUEST HANDLERFOR REQUEST NUMBER reqnumON yy/mm/dd AT hh:mm:ss

Explanation: A server obtained a file-transferrequest from the request queue. The serveractivates a local-request handler to carry out the filetransfer.

reqnum Request number.

yy/mm/dd Date that the file transfer started: yy=year,mm=month, dd=day.

hh:mm:ss Time that the file transfer started:hh=hour, mm=minute, ss=second.


User Action: None.

DVG006I OPEN ON name WAS NOT SUCCESSFUL

Explanation: A NetView FTP component could notopen one of the files necessary for its processing.

name ddname (for MVS) or file name (for VSE)of the file in error.

System Action: If the server group table is opened,processing continues. Otherwise, the NetView FTPcomponent terminates.

User Action: Correct the error and restart theNetView FTP component. Refer to the systemmessages in the failed component’s job log.

DVG008I ERROR DURING SERVER INITIALIZATIONPARAMETER HANDLING;ERROR CODE = error-code

Explanation: An error occurred when a serverprocessed its initialization control statements duringstartup.

error-codeOne of the following:

01 No server initialization controlstatements were specified.

02 No LUNAME parameter wasspecified; this is mandatory.

03 Duplicate class values werespecified in the CLASSparameter.

04 The RUNUMCR, BYTECR, andTIMECR parameters are mutuallyexclusive. You can specify onlyone of these parameters.

05 The value specified for theAVLSESS parameter exceededthe value specified in theMAXSESS parameter or theMAXSESS default parameter.

06 The value specified for theAVLLRH or AVLRRH parameterexceeded the value specified forthe AVLSESS parameter or theAVLSESS default value.

07 If the value specified forSRVMODE is SINGLE, then theserver can hold only one sessionat a time. Therefore the valuesspecified for the AVLSESS andMAXSESS parameters must be1.

08 If ALL is specified for theNVEVENT parameter, no otherNVEVENT values can bespecified.

09 Duplicate events were specifiedfor the NVEVENT parameter.

10 If you use parametersPRETRAN, POSTTRAN, or both,you must not use the PPEXITparameter.

11 To start a partition, serverinitialization control statementsfor at least one server must bespecified.

12 You must specify serverinitialization control statementsfor at least those servers youspecified in the STARTSRVparameter of the partitioninitialization control statement.

13 Duplicate numbers werespecified for the STARTSRVparameter.

14 A SRVSUF parameter mustprecede other server parameters.

100 LRD filestore entry for the OSIserver is missing.

System Action: The server or partition that theserver runs in stops.

User Action: Correct the error and restart theserver or partition.

Chapter 1. NetView FTP Messages 3

DVG009I � DVG009I

DVG009I ERROR DURING FILE-TRANSFER REQUESTVALIDATION;ERROR CODE = error-code

Explanation: An error occurred when NetView FTPprocessed one of the parameters of a file-transferrequest.

Note: If a parameter is not coded, the default usedmight be incompatible with other coded parameters.


01 No file-transfer requestparameters found.

02 You must identify a remotelocation by specifying either anLU name or the name of a servergroup, but not both. Neither wasspecified.

03 You must identify a remotelocation by specifying either anLU name or the name of a servergroup, but not both. Both werespecified.

04 You must specify either adata-set name or a ddname forthe sending data set.

05 You specified a remote LU nameand a local LU name and bothhad identical values.

06 Incorrect disposition found for thesending data set.

07 The disposition MOD or REG isvalid only for a single PDSmember.

08 Only dispositions OLD or NEWare valid for unlabeled tapes atthe receiving location.

09 A not-after date and time mustbe greater than thecorresponding not-before dateand time.

10 If you specify data-set typeUSER, you must also specify thename of a user-written filehandler.

11 Only dispositions OLD and NEWare valid for VSAM data sets.For MVS, CAT and SHR are alsovalid.

12 If you specify space units to beCYL or TRK, then:

� You must also specify aprimary space quantity.

� You cannot specify anaverage length.

13 If you specify space units to beBLK, then:

� For non-VSAM files at MVSlocations, you must alsospecify an average lengthand a primary spacequantity.

� For VSAM at VSE and VMlocations, you must alsospecify a primary spacequantity. The averagelength is ignored.

14 You can specify an averagelength, a primary space quantity,a secondary space quantity, or anumber of directory blocks only ifa space unit is specified.

15 You can specify spaceparameters only if the dispositionof the receiving data set is notOLD, MOD, or SHR.

16 If you specify space units asREC, then:

� For non-VSAM files on anMVS system with SMSactive, you must also specifya primary space quantity andan average length.

� For VSAM files, you mustalso specify a primary spacequantity.

� For non-VSAM files at VMand VSE systems, thisspecification is not valid.

� If a file type is not specified,you must specify a primaryspace quantity.

17 Some of the parameters youspecified when trying to modify arequest were incorrect ormissing. When modifying asubmitted request, you canchange the server class orrequest priority, or you can holdor release the request. Youmust not hold or release anentire class by omitting therequest number.

18 If you specify the name of aVSAM catalog, you must alsospecify a VSAM password forthat catalog (MVS).

19 If a non-VSAM data set is to betransferred to a new VSAMKSDS, you must specify the keylength for the receiving data set.

20 For new VSAM receiving datasets, you must specify at least amodel cluster or a volume serialnumber.


DVG009I � DVG009I

21 The sum of the key length andkey offset exceeds the maximumrecord size.

22 The specification for the sendingor receiving data set isincompatible in one of thefollowing ways:

� The receiving data-set typeis not PO and the sendingdata set is PO, but you didnot specify a single membernotation for the sending dataset, for example,SFILEID='PDS.DATA.SET(MEMBER)'.

� The sending data-set type isnot PO and the receivingdata set is PO, but you didnot specify a single membernotation for the receivingdata set, for example,RFILEID='PDS.DATA.SET(MEMBER)'.

If more than one member of aPDS is to be transferred, thedata-set type of both the sendingand receiving data sets must bePO.

If more than one member of aPDS is to be transferred, thedata-set type of both the sendingand receiving data sets must bePO.

23 If several members of a PDS areto be transferred, the data-settype of both the sending andreceiving data sets must be PO.

24 Parameters for user-written filehandlers are valid only for datasets with the data-set typeUSER.

25 VSAM parameters are valid onlyfor VSAM data sets.

26 If you specify record format VSor VBS for one data set, youmust specify record format VS orVBS for the other data set.

27 The space units BLK are notvalid for VSAM data sets onMVS.

28 The parameters specified wereincompatible. One of thefollowing combinations wasspecified:

� User-written file handlerparameters and a fileorganization other thanUSER

� VSAM cluster parametersand a file organization otherthan VSAM

� Several PDS members anda file organization other thanPO.

With the exception of thefollowing, these parameters mustnot be mixed:

� VSAM cluster parameterswith SFS Directory Accessparameters (sending)

� SFS Directory Accessparameters (sending) withSFS Directory Accessparameters (receiving).

29 File Process Option MERGE isvalid only for PDS, VSAM KSDS,or VSAM RRDS.

30 Either retention period orexpiration date is allowed, butnot both.

31 Record delimiter and End-of-fileoption are valid only forrecord-oriented files.

32 Name of a member to beselected or excluded is missing.

33 Either selection or exclusion ofmembers is allowed, but notboth.

34 Specify a VSAM catalog for adata set at an MVS location onlyif a new VSAM cluster is to bedefined at that location.

35 The file type specified wasincorrect.

36 Specify either a GDG model IDor a user catalog ID, but notboth.

37 Specification of receiving SFSdirectory access parameters isonly allowed for physicalsequential data set stored on aDASD.

38 Specification of sending SFSdirectory access parameters isonly allowed for physicalsequential data set stored on aDASD.

39 Incorrect tape device typespecified for the first fourcharacters.

40 Incorrect tape device type suffixspecified (char-position 5,6).

41 The specified tape device type,TAPEDC, is not allowed.

42 The Tape Device Typeparameter specified an unlabeledtape that requires thespecification of the Tape Densityparameter.


DVG009I � DVG009I

43 Track Number and Tape Densityfor the specified tape device typeare inconsistent.

44 For a receiving file to be SAMESDS the receiving node mustbe a VSE system.

45 For a receiving file to be SAMESDS the data organization mustbe nonindexed.

46 For a receiving file to be SAMESDS with the specified logicalrecord size the record formatmust be fixed blocked.

47 If XMODE=FROM is specified,specify the sending data-settype.

48 KSDS option REPKEY is notvalid for file status optionMUSTNOTEXIST.

49 SFS subdirectories must bespecified continuously. Forexample, you cannot specifysubdirectories 1 to 3, then leavesubdirectory 4 blank, and thenspecify subdirectory 5.

50 If GENERIC is specified, SMSSecurity Model must also bespecified.

51 You cannot specify both SMSREFDD and SMS LIKEparameters.

52 The following parameters are notvalid with SMS:

� Receiving DISP = OLD� Receiving file status option

MUSTEXIST (NetView FTPV2.2 MVS)

� Receiving ddname.

53 Do not specify average recordmultiplier if space units otherthan REC are specified.

54 Specify both APPC user ID andpassword parameters.

55 Specify both Data Encryption andEncryption Label parameters.

56 If the parameter specifies aLinear Data Set (LDS), theaverage and maximum recordlength, if specified, must be4096.

57 Specify a secondary spacequantity only if you also specify aprimary space quantity.

58 An OSI parameter was specifiedfor an SNA request.

59 For the CHANGEPW function,both the old and new passwordsmust be specified.

60 Specify Coded Character SetIdentifiers (CCSIDs) only ifcharacter data conversion isrequested.

61 The end-of-processing optionDELETE is not valid for thefollowing:

� File access option SHARED� Single member processing.

62 A file ID for the receiving filemust be specified if the file statusoption is MUSTEXIST and thesending file ID cannot be used togenerate a file ID.

63 Workstation ID is mandatory forremote AIX*.

100 String significance and maximumstring length incompatible.

101 Document type and universalclass incompatible.

102 Access control action elementvalue not allowed.

103 The specified access controlaction elements do not allowsufficient access rights toperform the read or read attributetransfer option for COPYfunction.

104 The specified access controlaction elements do not allowsufficient access rights toperform the read, read attribute,or delete transfer option forMOVE function.

105 Document type is not valid.

106 Maximum string length is notvalid.

107 String significance is not valid.

108 Universal class is not valid.

109 Permitted actions do not match.

110 Data-set name is not valid.

120 Data set is not available.

130 Data set I/O error.

200 User has insufficient RACF*authority. This code may alsoindicate that the file does notexist.

210 OSI/File Services has insufficientRACF authority. This code mayalso indicate that the file doesnot exist.

300 A request that has already beenterminated cannot be canceled.

310 Request temporarily returned tothe queue handler.

500 User filestore capabilityinsufficient.


DVG010I � DVG010I

510 Filestore access rights violated.

540 Specified document type doesnot correspond to LRD entry.

550 Maximum string length does notcorrespond to LRD entry.

560 String significance does notcorrespond to LRD entry.

570 Universal class does notcorrespond to LRD entry.

580 Filestore capability is insufficient.

590 Filestore access is not allowed.

600 File missing in LRD and it cannotbe added.

System Action: If this error is detected by:

� An interface routine, NetView FTP rejects therequest.

� A server, the file transfer ends and NetView FTPchanges the status of the request to finished .

User Action: Correct the error and resubmit therequest.

DVG010I PARAMETER ERROR;RECORD FORMAT = recfm;BLOCK SIZE = blk;LOGICAL RECORD LENGTH = lrecl.INVALID COMBINATION OF DCB PARAMETERSSPECIFIED;PARAMETER TYPE = type;ERROR CODE = error-code

Explanation: There is an error in the parameterslisted in this message.

blk Physical block size.

lrecl Logical record length.

recfm Record format.

type One of the following:

S Parameter applies to sendinglocation.

R Parameter applies to receivinglocation.


01 A record format was specified,but neither a physical block sizenor a logical record length wasspecified.

02 For fixed-block records, physicalblock size and logical recordlength must be specified so thatthe physical block size is equalto or a multiple of the logicalrecord length.

03 For fixed unblocked records,specify either a logical recordlength and no physical blocksize, or both a physical blocksize and a logical record lengththat are equal to each other.

04 For variable and variable-blockedrecords, the physical block sizemust be at least 4 bytes greaterthan the logical record length.The logical record length can beany integer from 5 to 32 756(MVS and VM) or 5 to 32 763(VSE).

05 Specify a logical record lengthand physical block size only ifyou specify a record format.

06 The logical record length for VSor VBS records and the physicalblock size for VBS records canbe any integer value from 5 to32 756.

07 You must specify a logical recordlength and physical block size forVBS and VS records.

08 The file transfer was notsuccessful because:

� If the record format of thereceiving data set is F or FB,the length of each record ofthe sending data set mustequal that of each record ofthe receiving data set.

� If the record format of thereceiving data set is not F orFB, the logical record lengthof the sending data set mustbe equal to or less than thatof the receiving data set.






DVG011I � DVG011I

DVG011I PARAMETER WITH KEYWORD keyword INERROR;ERROR CODE = error-code

Explanation: The keyword shown in this messagecorresponds to a parameter. Either that parameteror its value was in error. If NetView FTP is not ableto determine which parameter is in error, it leaveskeyword blank.


01 Program error.

02 Program error.

03 More values than are allowedwere specified for a parameter.The end-of-data delimiter may bemissing from a batch job.

11 A program error occurred in theNetView FTP batch job interfaceroutine. Contact your systemadministrator.

12 A keyword contains a characterthat is not A to Z, or 0 to 9.Check for errors in the coding ofkeywords, or errors that cancause something to be wronglyidentified as a keyword.

13 The keyword is not followed byany value.

14 The keyword is not a NetViewFTP keyword.

15 The same keyword or its aliaswas already coded.

16 The parameter has not exactlyone operator.

17 If more than one value isspecified, the values must beenclosed in parentheses.

18 No keyword found before theoperator.

19 Opening parenthesis or closingparenthesis or comma isspecified before the operator.Only a keyword is allowed beforethe operator.

21 A program error occurred in theNetView FTP batch job interfaceroutine. Contact your systemadministrator.

Check for unpaired quotes orother errors in coding.

22 A parameter value that is notcoded within single quotescontains a character that is notone of the following: A to Z, 0 to9, @, #, $. Check for missingquotes or other errors in coding.

23 No comma was coded after aparameter value in a list ofvalues enclosed in parentheses.The list of parameters is followedby a blank. Check for unpairedquotes or other errors in coding.

24 A blank immediately followed theequal sign of a NetView FTPcontrol statement.

25 Unmatched quotes. Parametervalues cannot contain an oddnumber of quotes.

26 Number of opening parenthesesnot equal to number of closingparenthesis.

27 A numeric parameter exceedsthe range of allowed values.

28 A parameter value is incorrect.

29 Opening parenthesis notimmediately behind the operator.

30 A parameter value was codedwith an incorrect length or acomma was missing.

Note: NetView FTP checks forthe correct length of a valuebefore checking the correctnessof the value. For example,coding the keywordXMODE=RECEIVER causesNetView FTP to issue a returncode of 30 rather than 28.NetView FTP also issues returncode 30 when a hexadecimalvalue is coded with an oddnumber of characters.

31 A parameter value that must becoded within single quotes wasnot.

32 Too many values were coded fora parameter, or a closingparenthesis was missing.

33 Closing parenthesis followsimmediately after openingparenthesis.

34 A closing parenthesis wasmissing or a blank was in thewrong place.

35 At least one parameter value toolow.

36 At least one parameter value toohigh.

37 At least one parameter length toolow.

38 At least one parameter length toohigh.

39 Parameter length not correct (notpart of a list of correct length).

40 Closing parenthesis beforeopening parenthesis.


DVG012I � DVG013I

41 A parameter value was codedwith an opening quote but noclosing quote.

42 Number of value too high or low.

43 Program error.

44 NetView FTP stores parameterinformation in tables. The size ofthe tables is adequate forcorrectly specified parameters.An error caused the tables to befilled before NetView FTP couldcheck all the parameters.

45 A parameter value that must becoded within single quotes wasnot.

46 At least one parameter value notpart of a list of valid values.

47 At least one parameter value notnumeric.

50 Hexadecimal notation of a valueincorrect: at least one digit not ato f,A to F,0 to 9.

51 Program error.

52 Syntax error. If you cannot findthe reason for the error and if theerror persists, contact your IBM*Support Center.

61 File ID contains both blanks andperiods.

62 The sequence of opening andclosing parentheses is incorrect.

63 The file ID must end with aclosing parenthesis.

65 A part of the file ID containsmore than 8 bytes.

66 The file ID ends with a separatorsign.

67 The file ID contains blanks.

68 The file ID contains anonalphanumeric character.

69 The GDG number is too long.

70 The GDG number is too short.

71 The GDG number is not numeric.

72 Invalid notation of a member or aGDG.

73 The value begins with anonalphanumeric character.

75 Invalid CMS notation: one ormore parts of a file ID containmore bytes than allowed.Maximum length is:

8 bytes For file name

8 bytes For file type

2 bytes For file mode.

255 Program error.

System Action:

NetView FTP V2.2 MVSNetView FTP rejects the request. Allother parameters are checked too.

NetView FTP other than NetView FTP V2.2 MVSIf the error code is 1, 2, 3, 11, 21, 24,34, 41, 43, 44, 51, 52, or 255, NetViewFTP rejects the request without checkingany further parameters. If the error codeis another number, NetView FTP checksthe other parameters in the requestbefore it rejects the request.

User Action:

NetView FTP V2.2 MVSFor error codes other than 1, correct theerror and resubmit the request. Forerror code 1 contact your IBM SupportCenter.

NetView FTP other than NetView FTP V2.2 MVSFor error codes other than 1, 2, 43, 51,and 255, correct the error and resubmitthe request. For error codes 1, 2, 43,51, and 255, contact your IBM SupportCenter.

DVG012I KEYWORD keyword1 NOW REPLACED BYKEYWORD keyword2; BUT STILL ACCEPTED

Explanation: With NetView FTP V2.2 MVS, thekeyword indicated by keyword1 has been replacedby the keyword indicated by keyword2. keyword1 isstill accepted.


User Action: None. You might, however, want tochange your file-transfer requests accordingly.

DVG013I PARAMETER WITH KEYWORD keyword IS NOTPERMITTED FOR THE FILE ORGANIZATION =type

Explanation: A request specified at least oneparameter that is incorrect for the file organization itspecified. Either the parameter whose keyword isshown in the message, or the file organizationspecified in the request, is in error.


keyword The batch job interface keyword.

type File organization can be one of thefollowing:

VSAM VSAM data set

PS Physical sequential data set

PO Partitioned organized dataset.


DVG014I � DVG015I





DVG014I PARAMETER INCOMPATIBILITY;PARAMETER TYPE = type;ERROR CODE = error-code

Explanation: A parameter for the data set indicatedby type has the incompatibility indicated byerror-code.


S Parameter applies to sendingdata set.

R Parameter applies to receivingdata set.


01 Unless dynamic allocation is tobe used, NetView FTP ignoresthe Volume Serial Numbersparameter for MVS locations.

02 NetView FTP ignores the DCBparameters specified for PDSmembers with dispositions OLDor MOD.

03 Specify DCB parameters for thesending data set only if it is at aVSE location or if it is stored onunlabeled tapes at an MVSlocation. Otherwise, NetViewFTP ignores the DCB parametersyou specify.

04 Unless dynamic allocation is tobe used, NetView FTP ignoresany DCB parameters youspecified for data sets at MVSlocations.

05 NetView FTP ignores anydisposition specified other thanOLD or NEW for filetype VSAMat a VSE node.

06 NetView FTP ignores any keylength, key offset, or KSDSoption you specify for non-KSDSVSAM data set.

07 NetView FTP ignores theparameters for a new VSAM fileunless the disposition of thereceiving data set is NEW.

08 NetView FTP has internallychanged the server runningmode value from single tocontinuous. A VM system onlyrecognizes continuous servers.

09 If you specify only a user ID andno password, NetView FTPignores the security parameters.Specify only the securityparameter user ID without apassword if the remotefile-transfer program is FTP V2.2VSE. This transfer program usesthe specified user ID to notify anICCF user at the end of a filetransfer.

10 NetView FTP ignores the valuefor the PDS option if:

� A single member of a PDSis specified

� A member selection list of aPDS is specified.



DVG015I PARAMETER WITH KEYWORD keyword IS NOTPERMITTED FOR THE TYPE typeOr, for NetView FTP V2.2 MVS:

DVG015I PARAMETER WITH KEYWORD keyword IS NOTPERMITTED FOR THE FILE ORGANIZATION =type; LABEL TYPE = lab-type

Explanation: A request specified at least oneparameter that is incorrect for the data-set type itspecified. Either the parameter whose keyword isshown in the message, or the data-set type specifiedin the request, is in error.



type Data-set type or file organization can beone of the following:

VSAM VSAM data set

PS Physical sequential data setstored on DASD (other thanNetView FTP V2.2 MVS)Physical sequential data setstored on DASD or tape(NetView FTP V2.2 MVS); thelabel type of the tape isindicated by lab-type

PO Partitioned organized data set

LAB Physical sequential data setstored on labeled tape

UNLAB Physical sequential data setstored on unlabeled tape.

lab-type Label type of the tape (NetView FTP V2.2MVS)

SL Labeled tape

NL Unlabeled tape.


DVG016I � DVG018I





DVG016I FUNCTION function IS NOT PERFORMEDBECAUSE OF INCORRECT INPUT

Explanation: A queue handler command wasissued and the Function parameter had the valuefunction. However, at least one of the NetView FTPcontrol statements in your request was in error.

function The value of the Function parameter, asused with the batch job interface.Possible values are:

� ADD � DELETE � MODIFY � QRYADM � QUERY � QRYALL � DELALL � DELFIN � FORCEDEL � RESTART � CHANGEPW (VSE) � REBUILD (VSE).

System Action: The function is not performed.

User Action: This message is accompanied byother messages indicating the control statement inerror. When you have corrected the error, reissuethe queue handler command.

DVG017I FUNCTION function IS NOT PERFORMEDBECAUSE OF TEST RUN

Explanation: A queue handler command wasissued and the Function parameter had the valuefunction.



System Action: The file-transfer request ischecked, but not processed, because you specifiedTESTRUN=YES in your request.

User Action: To have the file-transfer requestprocessed, specify TESTRUN=NO.

DVG018I PARAMETER ERROR;PARAMETER TYPE = type;ERROR CODE = error-code

Explanation: Self-explanatory.


S Parameter applies to the sendingdata set.

R Parameter applies to thereceiving data set.


01 If the data-set type is PO, arequest must specify either amember name or a ddname, butnot both. You did not specifyeither a member name or addname.

02 If the data-set type is PO, arequest must specify either amember name or a ddname, butnot both. You specified both amember name and a ddname.

03 A request specified an incorrectcombination of VM Linkparameters. The specification ofthe internal address and filemodeis only valid for FTP V2.2 for VM.

04 If a request specifies a node IDfor the recipient of a file-transferreport, it must also specify a userID. The user ID is missing.

05 A request must specify a volumeserial number for a data set thatis to be dynamically allocatedwhen one of the following is true:

� The file to be sent is storedon tape.

� The file to be received on aVSE system is stored on alabeled tape.

� The file to be sent orreceived on an MVS systemis not cataloged.

� The file to be received on atape on a VM system existsalready (disposition = OLD).

� The file to be received is anew VSAM cluster for whichno model name or SMSparameter (MVS) isspecified.


DVG018I � DVG018I

06 A request must specify a volumeserial number for a data set thatis to be dynamically-allocated,has the disposition NEW or CAT,and is stored on a tape at anMVS location.

07 A request specified an incorrectrelative generation number for ageneration data set.

08 Record formats VS and VBS arenot valid for the data-set typespecified in the request.

09 The relative generation numberor member name specified aspart of the data-set name had anincorrect length.

10 The data-set name includedparentheses, but no relativegeneration number or membername.

11 You cannot specify both thefollowing:

� Parentheses as part of thevalue of the Data-Set Nameparameter. This indicatesthat you are specifying arelative generation numberor a member name as partof the data-set name.

� A member name for theMember Name parameter.

12 A relative generation number ormember name was specified aspart of the data-set name, but isnot allowed for the data-set typespecified in the request.

13 The data-set name included anopening parenthesis but noclosing parenthesis.

14 The data-set name included aclosing parenthesis but noopening parenthesis.

15 You can specify either the nameof a single PDS member or a listof PDS members, but not both.

16 You specified a combination ofaccess security parameters thatis not valid. You cannot specifya value for one access securityparameter (for example, user ID)and have NetView FTP retrieveanother parameter (for example,password or group ID) byspecifying an asterisk. Refer tothe NetView FTP ParameterReference for more informationabout access securityparameters.

17 A model DSCB is valid only forGDGs, so the data-set type mustbe PS or LAB.

18 If OS/400* is sending, you mustspecify the library name, filename, and member name.

19 For one data set you cannotspecify both OS/400 fileparameters and MVS data-setparameters.

20 If OS/400 member name or filetype is specified, you must alsospecify library name and filename.

21 If Post-Transfer Job library nameis specified, you must alsospecify the job name.

22 If Post-Transfer Program isspecified (APX section created),you must specify Post-TransferProgram Name APXPGNME.

23 If Post-Transfer Programdata-area length is greater thanzero, you must also specify theprogram name and parameterdata area.

24 For non-VSAM files, only onevolume serial number can bespecified for a VM node.

25 Specify library name, file name,and member name when youspecify OLD for a receivingOS/400 file.

26 Specify the APPC user ID andpassword when you transfer afile to or from OS/400.

27 Shared file parameters are notallowed for VM/XA*.

28 If you specify a member name,you must also specify a filename.

29 The end-of-processing optionDELETE is not valid for the fileaccess option SHARED.

30 The end-of-processing optionDELETE is not valid for singlemember processing.






DVG019I � DVG025I

DVG019I FILE TRANSFER STARTED ON REMOTEREQUEST HANDLERON yy/mm/dd AT hh:mm:ss

Explanation: A server received and accepted asession initiation request from a remote server. Theserver activates one of its remote request handlers toperform the file transfer.

yy/mm/dd Date that the file transfer started: yy=year,mm=month, dd=day.

hh:mm:ss Time that the file transfer started:hh=hour, mm=minute, ss=second.


User Action: None.

DVG020I text string

Explanation: This message is used by NetViewFTP to print text string.

text stringOne of the following:

� Parameter input, read by NetViewFTP, passwords suppressed.

� Separator lines to improve readabilityof NetView FTP message output.


User Action: None.

DVG021I SERVER FAILED TO RECOVER A SESSION;ERROR CODE = error-code

Explanation: The session with a remote server wasinterrupted by an ACF/VTAM* event. The localserver tried to start the session again, but failed forthe reason indicated by error-code.


01 The session could not beestablished during the timeinterval that allows automaticsession recovery.

02 An ACF/VTAM event occurredwhich makes it impossible torecover the session.

03 The transfer was terminated,because either the user deletedthe file-transfer request or theserver was stopped.

04 The server tried to recover thesession, but the remote serverwas no longer active for thistransfer.

System Action: The transfer ends. The status thatNetView FTP gives the request depends on thevalue of the Automatic Transfer Restart parameterfor that request:

� If the value is YES, NetView FTP gives therequest the status waiting ; the request isreprocessed later.

� If the value is NO, NetView FTP gives therequest the status finished ; the request is notreprocessed later.

User Action: If the status of the file-transfer requestis:

� Waiting , no action is required.

� Finished and you want the file transfer to bereestablished, correct the error and resubmit thefile-transfer request.

� Finished and you do not want the file transfer tobe reestablished, no action is required.

DVG023I REQUEST-UNIT SIZE OF oldsize IS REDUCEDTO newsize

Explanation: The Request Unit (RU) size specifiedfor a server is one of the following:

� Not an acceptable value, but is between twoacceptable values.

� Not a value that can be handled by your networkresources.

oldsize RU size specified for servernewsize RU size used by NetView FTP.

System Action: The server changes the valuespecified to the next lower acceptable value.Processing continues. If the change was made dueto SNA RU size inconsistencies, the change remainsin force until the end of the server’s processing. Ifthe change was made due to network resourceshortages, the change applies only for the current filetransfer; after the file transfer ended, NetView FTPreestablishes the original value.

User Action: None.

DVG025I SERVER serverid READY

Explanation: The server with the specified serverID is ready to obtain requests.

serverid One of the following:

� The job name of the procedure(MVS)

� The server prefix plus the serversuffix (VSE)

� The user ID of the distribution servicemachine (VM).


User Action: None.


DVG026I � DVG028I

DVG026I SESSION NOT STARTED WITH luname;REMOTE SERVER WAITING FOR RECOVERY

Explanation: When trying to start a new session, aserver detected that the remote server was waitingfor recovery of an interrupted session.

luname LU name of the remote server.

System Action: If the file-transfer request specifiesthe name of a server group, NetView FTP tries toestablish a session with another logical unit in theserver group. If there are no more untried logicalunits left in the server group or if the requestspecified a remote LU name, NetView FTP changesthe status of the file-transfer request to waiting .

User Action: None.

DVG027I SESSION NOT STARTED WITH luname;RETURN CODE IN RPL = rcrpl;FEEDBACK FIELD IN RPL = fdbk;SENSE CODE IN RPL = sensecode

Explanation: When starting a session, the remoteserver is found to be temporarily not available.Possibly, the remote server was not started.

luname LU name of the server at the remotelocation.

rcrpl ACF/VTAM return code in RPL.

fdbk ACF/VTAM feedback code in RPL.

sensecode ACF/VTAM sense code in RPL.

For more information about the return, feedback, andsense codes, see the VTAM Programming book.

System Action: If the session was beingestablished for the first time, and if the file-transferrequest specifies the name of a server group,NetView FTP tries to establish a session withanother logical unit in the server group. If there areno more untried logical units left in the server groupor if the request specified a remote LU name,NetView FTP changes the status of the file-transferrequest to waiting .

If the session was being reestablished duringautomatic session recovery, the transfer ends. Thestatus that NetView FTP gives the request dependson the value of the Automatic Transfer Restartparameter for that request.





DVG028I SESSION NOT STARTED WITH luname;LOGICAL UNIT NAME IS UNUSABLE;RETURN CODE IN RPL = rcrpl;FEEDBACK FIELD IN RPL = fdbk;SENSE CODE IN RPL = sensecode

Explanation: The server tried to establish a sessionwith the logical unit named in the message but thename was permanently not available. Possibly theLU name is not defined in ACF/VTAM.

luname LU name, as specified in the file-transferrequest or retrieved from the servergroup table.




For more information about the return, feedback, andsense codes, see the VTAM Programming book.

System Action: If the session was beingestablished for the first time and if the file-transferrequest specifies the name of a server group,NetView FTP tries to establish a session withanother logical unit in the server group. If there areno more untried logical units left in the server groupor if the request specified a remote LU name,NetView FTP changes the status of the file-transferrequest to finished .

If the session was being reestablished duringautomatic session recovery, the transfer ends. Thestatus that NetView FTP gives the request dependson the value of the Automatic Transfer Restartparameter for that request:








DVG029I � DVG033I

DVG029I SESSION STARTED WITH luname AT hh:mm:ssUSING AN LU TYPE 0 SESSION

Explanation: A server established an SNA sessionwith a remote server using an LU type 0 session.

luname LU name of the remote server

hh:mm:ss Time that the session started: hh=hour,mm=minute, ss=second.


User Action: None.

DVG031I SESSION NOT STARTED WITH luname;NO STORAGE FOR REQUEST UNIT AVAILABLEAT REMOTE SYSTEM

Explanation: The remote server was unable to getvirtual storage for the RU to be transferred.


System Action: If the session was beingestablished for the first time and:

� If the file-transfer request specifies the name ofa server group, NetView FTP tries to establish asession with another logical unit in the servergroup.

� If there are no more untried logical units left inthe server group or if the request specified aremote LU name, NetView FTP changes thestatus of the file-transfer request to waiting .






If the problem persists, ask your systemadministrator to check the messages at the remotelocation.

DVG032I SESSION NOT STARTED WITH luname;REMOTE SERVER COULD NOT ACCEPTANOTHER SESSION

Explanation: The remote server cannot accept thesession because it already reached its limit forremotely initiated sessions. It is either busy withother file transfers, or is already in a terminationstate because it reached its termination time, orbecause an operator intervened. The remote serveris regarded as temporarily not available.












DVG033I SESSION NOT STARTED WITH luname;REMOTE SERVER WAS RUNNING IN SINGLEMODE AND COULD NOT ACCEPT ANOTHERSESSION

Explanation: The remote server is running in singlemode. It cannot accept the conversation because itis already in a session, or is not available forremotely initiated sessions.





DVG035I � DVG038I









Note: Before the request is rescheduled, check withyour system administrator to make sure that theremote server is restarted and is ready to servesessions initiated at remote locations.

DVG035I AUTOMATIC SESSION RECOVERY INPROGRESS AT hh:mm:ss WITH luname

Explanation: ACF/VTAM notified the server that thesession with the remote server was interrupted. Thelocal server attempts to recontact the remote server.

hh:mm:ss Time that session recovery started:hh=hour, mm=minute, ss=second.


System Action: The server will try to restart thesession with the remote server. If successful, the filetransfer continues from the point at which the breakoccurred. If not successful, the file transfer ends.

User Action: None.

DVG036I SESSION NOT STARTED WITH luname;INCOMPATIBLE NETVIEW FTP LEVEL

Explanation: A server issues this message if itdetects that the remote server has an incompatibleNetView FTP level.

luname LU name of the remote server

System Action: NetView FTP does not start thesession, rejects the file-transfer request and changesthe status of the request to finished .

User Action: Check that the location that wascontacted is at least either a NetView FTP V2 MVS,NetView FTP V1 VM, NetView FTP V1 VSE,NetView FTP/400, or NetView FTP for Workstationslocation. If it is not, correct and resubmit therequest. If it is, contact your system administrator.

DVG037I REMOTE REQUEST HANDLER IS PROCESSINGREQUEST NUMBER reqnumOr, for NetView FTP V2.2 MVS:

DVG037I REMOTE REQUEST HANDLER IS PROCESSINGREQUEST NUMBER = reqnum; REQUEST NAME= reqname

Explanation: The remote request handler subtaskof the server is processing the file-transfer requestwith the number reqnum and the request namereqname. Blanks instead of reqnum or reqnameindicate that the corresponding value is not available.The request was obtained by a remote server fromits request queue.


User Action: None.

DVG038I THE REMOTE SERVER HAS AN INSUFFICIENTFTP LEVEL;ERROR CODE = error-code

Explanation: A server issues this message if itdetects that the remote server has an incompatibleFTP level, or if it detects that the remote transferprogram is not NetView FTP or FTP V2.

Note: A compatibility PTF must be installed for FTPV2 to be able to communicate with NetView FTP.


01 The remote transfer program isnot NetView FTP or FTP V2.

02 The remote transfer program isFTP V2 for MVS and VSE.

03 The remote transfer program isFTP V2 for VM or a compatiblerelease.

System Action: The remote transfer program eitherissues the FTP V2 message DVG034I with sensecode 10050000 or shows an ACF/VTAM RECEIVEerror.

If the file-transfer request specifies the name of aserver group, NetView FTP tries to establish asession with another logical unit in the server group.If there are no more untried logical units left in theserver group or if the request specified a remote LUname, NetView FTP rejects the file-transfer requestand changes the status of the request to finished .

User Action: Check that the location that wascontacted is a NetView FTP or FTP V2 location. If itis not, correct and resubmit the request. If it is,contact your system administrator.


DVG039I � DVG042I

DVG039I REMOTE SERVER luname COULD NOT ACCEPTA SESSION

Explanation: The remote server cannot accept asession initiation request. Possible reasons are:

� The remote FTP V2 VM is not running in remoterequest server mode.

� The remote FTP V2.2 MVS or FTP V2.2 VSE isnot running in resident session partner mode.

If NetView FTP is to transfer a file to or from an FTPV2 location, the remote FTP V2 must be either aremote request server (VM) or a resident sessionpartner (VSE or MVS).

luname LU name of the remote server asspecified in the file-transfer request orretrieved from the server group table.

System Action: If the file-transfer request specifiesthe name of a server group, NetView FTP tries toestablish a session with another logical unit in theserver group. If there are no more untried logicalunits left in the server group, or if the requestspecified a remote LU name, NetView FTP rejectsthe file-transfer request and changes the status ofthe request to finished .

User Action: Check the specified LU name or, ifthe name of a server group was specified, check theserver group table for valid values. If the problempersists, contact the remote location for informationabout the remote servers.

DVG040I function ERROR ON ddname

Explanation: An error occurred in one of theNetView FTP components during execution of thefunction specified. Probably an additional systemmessage was issued to the component’s job log.

function One of the following:

� OPEN � CLOSE� TCLOSE (CLOSE TYPE = T).

ddname ddname or data-set name of the file inerror.

System Action:

� Error occurred during a file transfer; the filetransfer ends.

If the error occurred in a server and the functionwas OPEN, it is probably due to one of thefollowing:

– The data-set type in the request does notmatch the file type of the data set.

– The data set does not exist. This is usuallya result of using the default data-set type.

– Insufficient storage in the MVS region, theVM machine that the NetView FTPcomponent runs on, or the VSE partition.

– An authorization problem.

If the function was CLOSE, check to see if youspecified DISP=MOD for a PDS member.

Possibly there is an existing member on thereceiving data set with the same name. If youdid not specify DISP=MOD, the receiving dataset could have overflowed. NetView FTPchanges the status of the file-transfer request tofinished .

� Error occurred in queue handler; the queuehandler stops.

User Action:

� For an error during a file transfer, correct theerror and resubmit the request.

� For error in queue handler, correct the problemand restart the queue handler.

DVG041I I/O ERROR FOR QSAM macro;UNIT = unit;DEVICE = device;DD-NAME = ddname;OPERATION = operation;ERROR DESCRIPTION = errordesc;PHYSICAL RECORD ADDRESS = bbcchhr

Explanation: An I/O error occurred in one of theNetView FTP components while NetView FTP wasprocessing the data set via QSAM.

macro QSAM macro that is in error: � CLOSE � GET � OPEN � PUT.

unit Unit address.device Device type.ddname Symbolic name of the DD statement.operation Operation attempted.errordesc Description of error.bbcchhr Direct access address of record in error.

System Action: If the error occurs independently ofa file transfer, the NetView FTP component thatissued the message stops. If the error occurs duringa file transfer, the file transfer ends and NetView FTPchanges the status of the request to finished ; theserver does not stop.

User Action: See the SYNADAF macroinstructionin the Administration Macroinstruction Reference foryour operating system.

DVG042I I/O ERROR FOR SAM macro;TRANSMIT INFO = trans;CSW STATUS = status;TYPE CODE = code;CCW ADDRESS = ccw;COMMAND CODE = cmdcd;RELATIVE BLOCK NUMBER = rbn

Explanation: An I/O error occurred whileprocessing the SAM file.

macro SAM macro that encountered the error.Can be one of the following: � GET � PUT.

trans Transfer information from CCB.status CSW status from CCB.


DVG043I � DVG044I

code Type code from CCB.ccw Address of CCW from CCB.ccd Command code of the current CCW.rbn Relative block number from DTF.

System Action: Transfer ends.

User Action: Correct the error and resubmit therequest. For an explanation of the fields from theCCB, see VSE/ESA Version 1 System MacrosReference or VSE/AF 4.1.1 Macro Reference. If youcannot solve the problem, contact your IBM SupportCenter.

DVG043I LOGICAL ERROR FOR VSAM macro;REGISTER 15 RETURN CODE = reg15;FUNCTION CODE IN RPL = rcrpl;FEEDBACK FIELD IN RPL = fdbk;DD-NAME = name

Explanation: During processing of a VSAM dataset, a logical error occurred.

macro VSAM macro that encountered the error:

� ERASE � GET � POINT � PUT.

reg15 Contents of register 15 in hexadecimalformat; returned by VSAM.

rcrpl VSAM function code in RPL for alternateindex processing, in hexadecimal format.

fdbk VSAM feedback code in RPL, inhexadecimal format.

name ddname of the data set in error.


User Action: Analyze the problem using one ormore of the following:

� MVS/DFP V3: Macro Instructions for VSAMData Sets

� MVS/XA VSAM Administration Macro InstructionReference

� Using VSE/VSAM Commands and Macros.

If a NetView FTP component stopped, fix theproblem and restart the component.

If a file transfer ended, fix the problem and resubmitthe file-transfer request.

DVG044I PHYSICAL ERROR FOR VSAM macro;REGISTER 15 RETURN CODE = reg15;VSAM RETURN CODE IN RPL = rcrpl;FEEDBACK FIELD IN RPL = fdbk;DATE = yyddd; TIME = hhmmssth;RELATIVE BYTE ADDRESS = rba;COMPONENT TYPE = comp;VOLUME SERIAL NUMBER = ser;JOB = job;STEP = step;UNIT = cuu;DEVICE = devtyp;DD-NAME = ddname;COMMAND CODE = op-OP;ERROR MESSAGE = errmsg;PHYSICAL RECORD ADDRESS = bbcchhr

Explanation: During processing of a VSAM dataset a physical error occurred.

macro VSAM macroinstruction that encounteredthe error:

� ERASE � GET � POINT � PUT.

reg15 Contents of register 15; returned byVSAM.

rcrpl VSAM return code in RPL.

fdbk VSAM feedback code in RPL.

yyddd Date that the error occurred: yy=year,ddd=day.

hhmmssthTime that the error occurred: hh=hour,mm=minute, ss=second, th=tenth, andhundredth of a second.

rba Relative byte address.

comp Component type:

� DATA � INDEX.

ser Volume serial number.

job Job name.

step Step name.

cuu Device address.

devtyp Direct access: DA always appears in thismessage.

ddname Symbolic name of the DD statement.

op-OP Command code from CCW followed bycharacters -OP.

errmsg VSAM error message.

bbcchhr Direct access address of record in error.



DVG045I � DVG048I


� MVS/DFP V3: Macro Instructions for VSAM DataSets



If a NetView FTP component stopped, fix theproblem and restart the component. If a file transferended, fix the problem and resubmit the file-transferrequest.

DVG045I VSAM macro ERROR;REGISTER 15 RETURN CODE = reg15;VSAM ERROR CODE = errcode;DD-NAME = name

Explanation: During processing of a VSAM dataset, an error occurred.

macro VSAM macro that encountered the error:

� CLOSE � GENCB � MODCB � OPEN � SHOWCB� TCLOSE (CLOSE TYPE = T)

� TESTCB � SHOWCAT.

reg15 Contents of register 15 returned byVSAM.

errcode VSAM error code.

name If the transfer program runs under MVS,then this is the ddname used to allocatethe data set. Otherwise it is the filename. It is either the name specified inthe file name parameter or, if dynamicallocation is used, the one generated bythe server involved in the file transfer.






If a NetView FTP component stopped, fix theproblem and restart the component. If the filetransfer ended, fix the problem and resubmit thefile-transfer request.

The most common VSAM error code is 74. Thismeans that you should perform a VSAM VERIFY onthe data set, as it has not been closed since the lasttime it was accessed.

DVG046I I/O ERROR FOR BPAM macro;UNIT = unit;DEVICE = device;DD-NAME = ddname;OPERATION = operation;ERROR DESCRIPTION = description;PHYSICAL RECORD ADDRESS = bbcchhr

Explanation: An I/O error occurred whileprocessing the BPAM data set.

macro BPAM macro that is in error: � READ � WRITE.

unit Unit address.device Device type.ddname Symbolic name of the DD statement.operation Operation attempted.description Description of error.bbcchhr Direct access address of record in

error.

System Action: The transfer ends.

User Action: For more information, see one ormore of the following:

� MVS/DFP V3: Macro Instructions for non-VSAMData Sets

� MVS/XA Data Administration: Macro InstructionReference.

DVG048I I/O ERROR DURING SEQUENTIAL FILEPROCESSING;THE FOLLOWING SYSTEM MESSAGE WASFOUND IN THE SYNADAF MESSAGE BUFFERmessage

Explanation: This message occurs when an erroris detected during the processing of a physicalsequential file.

message The message returned by the operatingsystem.

For an explanation of the error condition associatedwith these messages, refer to the following:

� MVS/ESA Messages and Codes� MVS/XA Messages and Codes� VM/ESA System Messages and Codes� VM/XA SP System Messages and Codes

Reference.

System Action: If the error is detected during thetransfer of a file that is related to a source or targetfile, the file transfer is broken off. If the error isrelated to the FTP reader, printer, or log files, and afile transfer is in progress, NetView FTP stops afterthe file transfer is completed.



DVG049I � DVG053I

DVG049I ERROR DURING RESTART PROCESSING FORfile;ERROR CODE = error-code

Explanation: An error occurred when NetView FTPtried to position a data set to the recordedcheckpoint.

file ddname of the data set in error.


01 No buffer could be obtained for aPDS member.

02 Buffer size insufficient for a PDSmember.

04 Checkpoint not found in data set.Possibly, the data set wasmodified after the file transferwas interrupted.

System Action: The transfer ends and NetViewFTP changes the status of the request to finished .

User Action: Do one of the following:

� For error code 01, use a server that is started ina larger address space, requesting a restart fromthe recorded checkpoint. In this case, contactyour system administrator.

� For error code 02 or 04, add a new file-transferrequest to the request queue to perform the filetransfer, specifying that the file transfer must bestarted from the beginning of the receiving dataset (other than NetView FTP V2.2 MVS), orrestart the file transfer with RSTPNT=BEGIN totransfer from the beginning of the data set(NetView FTP V2.2 MVS).

DVG050I RECORD TO BE REPLACED NOT FOUND

Explanation: The VSAM KSDS option REPKEYwas specified, but a record in the sending data setdid not have a corresponding record in the receivingdata set.


User Action: If appropriate, choose another VSAMKSDS option. After you have corrected the errors,resubmit the file-transfer request.

DVG051I nn RECORDS COULD NOT BE PROCESSED ASREQUIRED BY THE KSDS OPTION

Explanation: A request specified the VSAM KSDSoption ADDKEY or DELKEY, and one of thefollowing was true:

� For ADDKEY, the receiving data set containedrecords that were identical to those in thesending data set.

� For DELKEY, records to be deleted from thereceiving data set were not there.

This message is issued for your information; themessage does not necessarily indicate that an erroroccurred. If a file transfer is restarted and its requestspecifies ADDKEY, this message might be issued forthe records that are retransferred.

nn Number of logical errors that occurred.


User Action: Check whether you have chosen thecorrect VSAM KSDS option.

DVG052I A RECORD WITH THE SAME KEY BUTDIFFERENT CONTENT WASFOUND IN THE RECEIVING KSDS WHILEUPDATING IT USING THEKSDS OPTION "ADDKEY"

Explanation: A server found a record with thesame key but different content in the receiving dataset, which was a KSDS and which it was updatingwith the VSAM KSDS option ADDKEY.


User Action: If appropriate, choose another VSAMKSDS option. After you have corrected the errors,resubmit the file-transfer request.

DVG053I FTP LEVEL OF REMOTE SERVER = ftplevel

Explanation: The server established a session withthe remote server. This message gives informationabout the FTP level of the remote server.

ftplevel One of the following:

4 FTP Version 2.2 withcompatibility PTF for NetViewFTP

5 NetView FTP Version 1 for MVSwithout the AFF

6 NetView FTP Version 1 for MVSwith the AFF

7 NetView FTP V2 MVS, NetViewFTP VM, or NetView FTP VSE.


User Action: None.


DVG054I � DVG060I

DVG054I I/O ERROR FOR QSAM function;DATA SET NAME = dsname;SYSTEM ABEND CODE = sac

Explanation: An I/O error occurred during a QSAMfunction. The error caused an abnormal termination,from which NetView FTP recovered.

function One to the following:

GET QSAM GET

PUT QSAM PUT

POINT QSAM GET

dsname Name of data set.

sac System ABEND code.

System Action: The transfer ends and NetViewFTP changes the status of the file-transfer request tofinished .




DVG056I VSAM DATA SET TYPE NOT SUPPORTED

Explanation: During the OPEN on the data set tobe accessed during the file transfer, the serverdetected that the VSAM data set is of anunsupported VSAM type.


User Action: If you want to transfer the data set,copy it into a data set of a supported type andtransfer that one.

DVG057I KSDS OPTION SPECIFIED FOR A VSAM ESDS

Explanation: During the OPEN on the receivingdata set, the server detected that the VSAM data setis an entry-sequenced data set (ESDS). However, aVSAM KSDS option was specified in the file-transferrequest.

System Action: The parameter is ignored andprocessing continues.

User Action: If the receiving data set is not aVSAM KSDS, do not specify a VSAM KSDS option.

DVG058W RECORDS FOUND WHILE OPENING VSAMESDS dsname

Explanation: The receiving data set is a VSAMESDS and has the name dsname. During the OPENon the receiving data set, the server detected that itwas not empty. The server expected the receivingdata set to be empty. The server writes over anyexisting records. If there are more records in theexisting data set than are being transferred to it,these other records remain in the data set. This cancause an integrity problem.

System Action: Processing continues; the serverwrites records from the beginning of the data set. Awarning is issued in the file-transfer completionmessage.

User Action: If an integrity problem exists, deleteand redefine the data set and, after you havecorrected the errors, resubmit the file-transferrequest. Otherwise, ignore the message.

DVG059I RECORDS FOUND WHILE OPENING VSAMKSDS FOR A FILE TRANSFER USING THEKSDS OPTION "ADDBEG"

Explanation: During the OPEN on the receivingdata set the server detected that the receiving dataset, a VSAM KSDS, was not empty. The file-transferrequest specified the VSAM KSDS option ADDBEG,which requires an empty data set.


User Action: Check that you have chosen thecorrect KSDS and correct any errors. Then add anew file-transfer request to the request queue toperform the file transfer.

DVG060I NETWORK NAME VECTOR NOT FOUND.LOCAL FTP NAME USED FOR BUILDINGCHECKPOINT KEY.

Explanation: The server did not find the networkname in the VTAM* resource identification list. Thelocal FTP name is used for building the key for thecheckpoint record.


User Action: If the problem persists contact yourIBM Support Center.


DVG061I � DVG064I

DVG061I ACF/VTAM macro ERROR FOR LOGICAL UNITluname;ACB ERROR CODE = errcd

Explanation: During processing of an ACF/VTAMmacro, an error occurred.

macro ACF/VTAM macro that encountered theerror:

� CLOSE � OPEN.

luname LU name of the server that issued therequest.

errcd Error code provided by ACF/VTAM afterinvocation of the macroinstruction.

System Action: The server stops.

User Action: Correct the ACF/VTAM problem andrestart the server.

For a description of this error code, see the VTAMProgramming book.

DVG062I ACF/VTAM macro ERROR;REGISTER 15 RETURN CODE = reg15;RETURN CODE IN RPL = rcrpl;FEEDBACK FIELD IN RPL = fdbk;SENSE CODE IN RPL = sensecodeLOGICAL UNIT NAME = luname

Explanation: During processing of an ACF/VTAMmacro, an error occurred.

macro ACF/VTAM macro that encountered theerror:

� CLSDT � INQUIRE � OPNDST � OPNSEC � RECEIVE � SEND � SESSIONC � SETLOGON � TERMSESS.

reg15 Return code in register 15 returned byACF/VTAM.




luname For the INQUIRE and SETLOGONmacro, this is the LU name of the localserver. In all other cases this is the LUname of the remote server.

System Action: If the macro is not SEND orRECEIVE, the file transfer ends or the server stops,depending on whether the problem is related to onetransfer or the entire server. NetView FTP changesthe status of the request to finished . Otherwise, ifthe macro is SEND or RECEIVE and no severeACF/VTAM error occurred, the server tries to performan automatic session recovery.

If this fails, the transfer ends and NetView FTPchanges the status of the request. The status thatNetView FTP gives the request depends on thevalue of the Automatic Transfer Restart parameterfor that request.

User Action: If the automatic session recovery wassuccessful or the status of the request was changedto waiting , no action is required. If the status waschanged to finished , it is possible that the erroroccurred during the termination of the server, withoutaffecting the transfer of data. Check to see if allrecords were transferred. If all records were nottransferred, or if the return code is greater than 8,see the VTAM Programming book for descriptions ofthe ACF/VTAM codes in this message.

DVG063I DSESLIM VECTOR NOT FOUND. USE DEFAULTVALUE = ;

Explanation: The VTAM application definition forthe server LU did not specify the DSESLIMparameter. NetView FTP uses a default value.


User Action: Add the VTAM DSESLIM parameterto the VTAM application definition (APPL minornode) for this specific server LU name. For moreinformation on setting up and maintaining theACF/VTAM resources refer to NetView FTP V2 MVSInstallation, Operation, and Administration.

DVG064I SESSION NOT STARTED WITH lunameALTHOUGH POSITIVE RESPONSE RECEIVED

Explanation: The remote server, which has the LUname luname, did not start the session. This wasdetermined by checking the CON field in theACF/VTAM Node Initiation Block (NIB), whichindicated that the session was not started although apositive response was returned to the BIND.






DVG065I � DVG067I



� Finished , and you want the file transfer to bereestablished, correct the error and resubmit thefile-transfer request.

� Finished , and you do not want the file transferto be reestablished, no action is required.

DVG065I ACF/VTAM APPCCMD MACRO ERROR;OPERAND CODE = opcode;RETURN CODE IN RPL = rcrpl;FEEBACK FIELD IN RPL = fdbkrpl;SENSE CODE IN RPL6 = senserpl;APPC PRIMARY RETURN CODE = rcpri;APPC SECONDARY RETURN CODE = rcsec

Explanation: An error occurred during theprocessing of the ACF/VTAM APPCCMD macro.

opcodeA code that corresponds to the operand forwhich the error occurred. Possible valuesare:

Code Operand

DISPLAYCONTROL=OPRCNTL,QUALIFY=DISPLAY

CNOS CONTROL=OPRCNTL,QUALIFY=CNOS

ALLOCCONTROL=ALLOC,QUALIFY=ALLOCD

SENDCONFCONTROL=SEND,QUALIFY=CONFIRM

SENDCNFDCONTROL=SEND,QUALIFY=CONFRMD

DEALLOCCONTROL=DEALLOC

DEALABNDCONTROL=DEALLOC,QUALIFY=ABNDUSER

PREPRCVCONTROL=PREPRCV

RCVFMH5CONTROL=RCVFMH5

RECEIVECONTROL=RECEIVE,QUALIFY=SPEC

REJECTCONTROL=REJECT

SENDDATACONTROL=SEND,QUALIFY=DATA

SEND ERRCONTROL=SEND,QUALIFY=ERROR

rcrpl ACF/VTAM return code in the RPL.

fdbkrplACF/VTAM feedback code in the RPL.

senserplACF/VTAM sense code in the RPLextension.

rcpri ACF/VTAM LU 6.2 primary return code.

rcsec ACF/VTAM LU 6.2 secondary return code.

System Action: If this message is accompanied bymessage DVG074I, DVG075I, DVG076I, DVG077I,or DVG078I, refer to that message for an explanationof the system action and user action. Otherwise, thestatus that NetView FTP gives the request dependson the value of the Automatic Transfer Restartparameter for the request.

User Action: If the status of the request waschanged to waiting , no action is required. If thestatus was changed to finished , it is possible thatthe error occurred during termination of the serverwithout affecting the data transfer. Check to see ifall records were transferred. If they were not, or ifthe file-transfer return code was greater than 8,manually restart the file transfer.

For more information about the ACF/VTAM codes inthis message, refer to the VTAM Programming forLU 6.2.

DVG066I PROCESSING OF REQUEST NUMBER reqnumSTARTEDOr, for NetView FTP V2.2 MVS:

DVG066I PROCESSING STARTED FOR REQUESTNUMBER = reqnum; REQUEST NAME = reqname

Explanation: A server obtained a file-transferrequest from the request queue. The server hasactivated one of its subtasks to carry out the filetransfer.

reqnum Request number. Blanks indicate that thisvalue is not available.

reqname Request name. Blanks indicate that thisvalue is not available.


User Action: None.

DVG067I SERVER COULD NOT ALLOCATE ACONVERSATION USING AN LU TYPE 6.2SESSION;APPC PRIMARY RETURN CODE = rcpri;APPC SECONDARY RETURN CODE = rcsec;THE SERVER WILL TRY TO ESTABLISH AN LUTYPE 0 SESSION

Explanation: A server tried to allocate aconversation using the LU 6.2 protocol. It was notable to do this, probably because its partner serverdoes not support LU 6.2 session types.

System Action: The server tries to establish asession using the LU 0 protocol.

User Action: If the server succeeds in establishingan LU 0 session and NetView FTP issues messageDVG029I, no action is required. If it does notsucceed, NetView FTP issues another message thatexplains why not.


DVG068I � DVG074I

For more information about the ACF/VTAM codes inthis message, refer to the VTAM Programming forLU 6.2 manual for your operating system.

DVG068I APPC SECURITY PARAMETERS ARE NOTACCEPTED

Explanation: The remote server rejected theallocation of a conversation, indicating that the APPCsecurity parameters received in the VTAM FunctionManagement Header 5 (FMH5) are not valid.

System Action: The request is terminated.

User Action: Correct the APPC securityparameters and resubmit the request.

DVG069I CONVERSATION ALLOCATED WITH luname AThh:mm:ss USING AN LU TYPE 6.2 SESSIONOr, for NetView FTP V2.2 MVS:

DVG069I CONVERSATION ALLOCATED WITH luname AThh:mm:ss

Explanation: A server allocated an APPCconversation with a remote server using an LU type6.2 session.


hh:mm:ssTime the session started: hh = hour, mm= minute, ss = second.


User Action: None.

DVG071I PARAMETER WITH KEYWORD keywordMUST BE SPECIFIED FOR THE FUNCTIONfunction

Explanation: A queue handler command wasissued and the Function parameter had the valuefunction.

keyword Keyword of the parameter, as used withthe batch job interface.



System Action: The function is not performed.

User Action: When you have corrected the error,reissue the queue handler command.

DVG072I PARAMETER WITH KEYWORD keywordIS NOT VALID WHEN USING JOB ALLOCATION

Explanation: The file-transfer request specified addname, indicating that job allocation, not dynamicallocation, was to be used. The request alsospecified the parameter whose keyword is shown inthis message, but this parameter is valid for dynamicallocation only.

keyword Keyword of the parameter, as used withthe batch job interface.





DVG073I CONVERSATION WITH luname ABNORMALLYDEALLOCATED BY REMOTE SERVER

Explanation: A failure occurred that the remoteserver is unable to correct. Probably the remoteserver terminated abnormally. This message isaccompanied by message DVG065I.


System Action: The status that NetView FTP givesthe request depends on the value of the AutomaticTransfer Restart parameter for that request.

User Action: If the status of the request is:


� Finished , and you want to reestablish the filetransfer, correct the error at the remote site andresubmit the file-transfer request.

� Finished , and you do not want to reestablish thefile transfer, no action is required.

DVG074I CONVERSATION NOT ALLOCATED WITHluname;REMOTE SERVER COULD NOT ACCEPTANOTHER CONVERSATION

Explanation: The remote server cannot accept theconversation for one of the following reasons:

� It reached its limit for remotely initiatedconversations.

� It is running in single mode and is already inconversation or is not available for remotelyinitiated conversations.

� It does not have enough virtual storage toaccept another conversation.

� It is running under VM, and there is no fileserver machine available.

� It is defined as LOCAL and cannot accept aREMOTE request.


DVG075I � DVG078I

This message is accompanied by messageDVG065I.


System Action: If the conversation was beingestablished for the first time and if the file-transferrequest specifies the name of a server group,NetView FTP tries to establish a conversation withanother logical unit as defined in the server group. Ifthere are no more untried servers left in the servergroup or if the request specified a remote LU name,NetView FTP changes the status of the file-transferrequest to waiting .

If the error occurred because the server was definedas local, NetView FTP changes the status of thefile-transfer request to finished .

User Action: None.

DVG075I SESSION NOT STARTED WITH luname;LOGICAL UNIT IS UNUSABLE

Explanation: The server tried to establish a sessionwith the logical unit named in the message but thename is neither available nor recognizable. Possibly,the LU name is not defined in ACF/VTAM or thelogical unit belongs to an adjacent SSCP to which noSSCP-SSCP session is active. This message isaccompanied by message DVG065I.


System Action: If the session was beingestablished for the first time and if the file-transferrequest specifies the name of a server group,NetView FTP tries to establish a session withanother logical unit as defined in the server group. Ifthere are no more untried logical units left in theserver group or if the request specified a remote LUname, NetView FTP changes the status of thefile-transfer request to finished .

User Action: Make sure the logical unit is availableand its name is defined in the server group table.Reestablish the file transfer, correct the error, andresubmit the file-transfer request. Otherwise, noaction is required.

DVG076I SESSION NOT STARTED WITH luname;REMOTE SERVER TEMPORARILY NOTAVAILABLE

Explanation: The server tried to establish a sessionwith luname but the logical unit is temporarilyinactive. Possibly, the remote server is not started.This message is accompanied by messageDVG065I.


System Action: If the session was beingestablished for the first time and if the file-transferrequest specifies the name of a server group,NetView FTP tries to establish a session withanother logical unit in the server group. If there areno more untried logical units left in the server groupor if the request specified a remote LU name,NetView FTP changes the status of the file-transferrequest to waiting .

User Action: None.

DVG077I CONVERSATION WITH luname PREMATURELYDEALLOCATED

Explanation: A failure occurred that caused theconversation with luname to prematurely terminate.Probably, the remote server terminated abnormally.This message is accompanied by messageDVG065I.





� Finished , and you want to reestablish the filetransfer, correct the error and resubmit thefile-transfer request.


DVG078I CONVERSATION WITH luname DEALLOCATED

Explanation: The conversation with luname nolonger exists. Possibly, a severe error occurred thatinterrupted the conversation. This message isaccompanied by message DVG065I.





� Finished , and you want to reestablish thefile-transfer request, correct the error andresubmit the file-transfer request.



DVG079I � DVG084I

DVG079I NETVIEW FTP SUCCESSFULLY RECOVEREDFROM VTAM STORAGE SHORTAGE

Explanation: NetView FTP successfully recoveredfrom an ACF/VTAM storage shortage. This messageis accompanied by message DVG065I.


User Action: If this message occurs repeatedly,check if ACF/VTAM has sufficient buffers available.

DVG080I FILE TRANSFER RESTARTED FROMCHECKPOINTOr, for NetView FTP V2.2 MVS:

DVG080I FILE TRANSFER RESTARTED FROM restartpoint

Explanation: The server restarted an interruptedfile transfer.

For NetView FTP V2.2 MVS, restart point can be:

BEGINNINGOne of the following occurred:

� A server restarted an interrupted filetransfer. The corresponding requestspecified that the server was not torestart the file transfer from acheckpoint.

� A server tried to restart an interruptedfile transfer from a checkpoint, but theserver could not find a checkpointrecord for the file transfer.

CHECKPOINTA server restarted an interrupted filetransfer using the checkpoint recorded inthe checkpoint data set.


User Action: None.

DVG081I FILE TRANSFER STARTED FROM BEGINNINGOF DATA SET

Explanation: One of the following occurred:

� A server started a new file transfer.

NetView FTP other than NetView FTP V2.2 MVS :

� A server restarted an interrupted file transfer.The corresponding request specified that theserver was not to restart the file transfer from acheckpoint.

� A server tried to restart an interrupted filetransfer from a checkpoint, but the server couldnot find a checkpoint record for the file transfer.


User Action: None.

DVG082W DELETION OF CHECKPOINT RECORD FAILED;FILE TRANSFER SUCCESSFULLY COMPLETED

Explanation: After successfully transferring thedata set, the receiving server tried to delete thecheckpoint record, but failed. The cause of thefailure is explained in message DVG043I orDVG044I. These messages are written to the log fileof the checkpoint manager virtual machine.

System Action: The server ignores the error andcontinues the termination processing for the filetransfer.

User Action: Contact your system administrator.Checkpoint records that are not cleared can fill upthe checkpoint data set. In transfers with NetViewFTPs other than NetView FTP V2.2 MVS, theserecords can also cause problems during subsequenttransfers of the same data set.

DVG083I RECORD/BYTE COUNTS NOT EQUAL;SENT = sss;RECEIVED = rrr

Explanation: After transferring a data set, thesending server transfers the count of records orbytes sent to the receiving server, which compares itto the count of the records or bytes received. Thevalues of the two counts do not match.

sss Record or byte count at sending location.

rrr Record or byte count at receiving location.


User Action: The transfer of the data set was notsuccessful and the output data set is probably inerror. Possibly, there is a NetView FTP programerror. Contact your IBM Support Center.

DVG084I DATA SET NAME SPECIFIED IN REQUEST ANDIN SERVER JOB DD STATEMENT AREDIFFERENT;DATA SET NAME SPECIFIED IN REQUEST =name;DATA SET NAME (DSN) SPECIFIED IN DDSTATEMENT = name

Explanation: The file-transfer request specified addname indicating that job allocation is to be used.A data-set name was also specified in the request.These names are different.


User Action: Correct whichever data-set name is inerror and resubmit the request.


DVG085W � DVG088I

DVG085W ERROR DURING CHECKPOINT DATA SETHANDLING;FILE TRANSFER CONTINUES

Explanation: An error occurred when the serveraccessed the checkpoint data set.

System Action: Processing continues. If thefile-transfer is interrupted, NetView FTP might not beable to restart it from a checkpoint. NetView FTPsother than NetView FTP V2.2 MVS might insteadrestart it from the beginning of the data set.

User Action: If the error persists, contact yoursystem administrator. Check the checkpoint dataset; you might have to redefine it.

This message is accompanied by message DVG043Ior DVG045I. Examine this message to find out moreabout the error.

DVG086W NO CHECKPOINT RECORD FOUND

Explanation: Restart was requested, but nocheckpoint record exists for this request.

System Action: The file transfer starts from thebeginning.

If the file status option in the initial request wasMUSTNOTEXIST and the data set was alreadyallocated before the file transfer was interrupted, therestart might not be successful (NetView FTP V2.2MVS only).

User Action:

NetView FTP V2.2 MVS: If the restart failed becausethe receiving data set was already allocated, check ifit can be deleted. If so, delete it and restart the filetransfer manually.

Other NetView FTP: None.

DVG087I DATA SET TYPE SPECIFIED IN REQUEST ANDRETRIEVED FROM SYSTEM ARE DIFFERENT;DATA SET NAME = dsnameDATA SET TYPE SPECIFIED IN REQUEST =typeDATA SET TYPE RETURNED FROM SERVICES= typeOr, for NetView FTP V2.2 MVS:

DVG087I FILE ORGANIZATION AND LABEL TYPESPECIFIED IN REQUEST AND RETRIEVEDFROM SYSTEM ARE DIFFERENT;DATA SET NAME = dsnameFILE ORGANIZATION SPECIFIED IN REQUEST= type; LABEL TYPE = lab-typeFILE ORGANIZATION RETURNED FROMSYSTEM SERVICES = type

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

dsname Name of data set.

type Data-set type or file organization:

VSAM VSAM data setPS Physical sequential data set

stored on DASD (other thanNetView FTP V2.2 MVS)Physical sequential data setstored on DASD or tape(NetView FTP V2.2 MVS):the label type of the tape isindicated by lab-type

LAB Physical sequential data setstored on labeled tape (otherthan NetView FTP V2.2 MVS)

UNLAB Physical sequential data setstored on unlabeled tape(other than NetView FTP V2.2MVS)

PO Partitioned organized data setTAPE Physical sequential data set

stored on labeled orunlabeled tape.

lab-type Label type of the tape(NetView FTP V2.2 MVS)

SL Labeled tape

NL Unlabeled tape.

System Action: The transfer ends. The status ofthe request is changed to finished .

User Action: Correct whichever data-set type or fileorganization is in error and resubmit the request.

DVG088I MEMBER NAME SPECIFIED FOR RECEIVINGDATA SET BUT NOT FOR SENDING DATA SET

Explanation: A request to transfer a single memberfrom one PDS to another specifies a member namefor the receiving data set, but does not specify onefor the sending data set. Such a request mustcontain one of the following:

� A member name for the sending data set only� A member name for both data sets.

System Action: The transfer ends and the status ofthe request is changed to finished .

User Action: Submit a new request, with a membername for either the sending data set or both datasets.


DVG089I � DVG098I

DVG089I FILE ID SPECIFIED IN REQUEST AND IN DLBLOR TLBL STATEMENT ARE DIFFERENT;FILE ID SPECIFIED IN REQUEST = name;FILE ID SPECIFIED IN DLBL OR TLBLSTATEMENT = name

Explanation: The file-transfer request specified afile name, indicating that job allocation is to be used.When job allocation is used, you do not need tospecify a file ID in the DLBL or TLBL statements. Ifyou do, the file ID in the DLBL or TLBL statementsmust be the same as that specified in the request.This message is issued when the IDs are different.


User Action: Correct whichever file ID is in errorand resubmit the request.

DVG090I MEMBER member IN pds name MAY RESULTFROM THIS INCOMPLETE FILE TRANSFER

Explanation: The file transfer was interrupted. Thereceiving data set of the file transfer is a PDS withthe name pds name. It contains a member namedmember that is only partially full because of theincomplete file transfer. This member is deletedwhen the file transfer is restarted.

System Action: None.

User Action: Either restart the file transfer, ordelete the member member.

DVG091I INVALID RECORD FOUND IN CHECKPOINTDATA SET. CHECKPOINT KEY: key;CHECKPOINT AREA: area

Explanation: During a transfer restart, an invalidrecord was found in the checkpoint data set.

key The first 100 bytes of the key of theinvalid checkpoint record.

area The contents of the checkpoint recordarea that contains the invalid data.

System Action: The checkpoint record is deleted.The transfer is started from the beginning of the file.

User Action: If the problem occurs for severaltimes, contact your IBM Support Center.

DVG092I END-OF-PROCESSING OPTION CHANGEDFROMeop1 TO eop2

Explanation: The end-of-processing option waseither not specified in the request or was changed fora transfer restart. NetView FTP changed theend-of-processing option to the appropriate value.


User Action: None.

DVG093I FILE STATUS OPTION CHANGED FROMfilstat1 TO filstat2

Explanation: In your file-transfer request, you eitherspecified MAYEXIST for the file status option or youomitted this parameter. NetView FTP changed thefile status option to the appropriate value, that is:

MUSTNOTEXIST If the file does not already existMUSTEXIST If the file already exists.


User Action: None.

DVG094I DCB AND SPACE PARAMETERS AREIGNORED FOR FILE STATUS OPTIONMUSTEXIST

Explanation: You specified DCB and spaceparameters for a file that already exists.


User Action: None.

DVG095I FILE ACCESS OPTION CHANGED FROMfilacc1 TO filacc2

Explanation: You did not specify the correct fileaccess option for VSAM data sets in your file-transferrequest. NetView FTP replaced the file accessoption exclusive with the file access option shared.


User Action: None.

DVG096I FILE filename IS DELETED DUE TOEND-OF-PROCESSING OPTION

Explanation: In your file-transfer request, youspecified with the end-of-processing option DELETEfor either the sending or the receiving file that,depending on the outcome of the file transfer, this fileis to be deleted after the transfer.


User Action: None.

DVG098I REMOTE TRANSFER PROGRAM HAS ANINSUFFICIENT SERVICE LEVEL

Explanation: The NetView FTP at your systemdetected that the transfer program at the remotesystem has an insufficient service level. It could becaused by one of the following:

� The remote transfer program is FTP Version 2.2but has installed the compatibility PTF requiredto communicate with NetView FTP.

� The remote transfer program is an FTP with alevel lower than FTP 2.2.

� The remote program is any other than FTP orNetView FTP.


DVG100I � DVG110I

The transfer program did not start.


User Action: Contact your administrator and askfor the appropriate PTF to be installed at the remotesystem. After it has been installed, resubmit therequest.

DVG100I MESSAGE FROM luname;FTP LEVEL = ftplevel;MESSAGE = message

Explanation: A message from the remote serverwas received. It shows that an error occurred at theremote location. The message content is notanalyzed—it is only printed.


ftplevel The FTP level of the remote server,where:

4 FTP Version 2.2 with thecompatibility PTF for NetViewFTP



7 NetView FTP V2 MVS, NetViewFTP VM, and NetView FTP VSE.

message Message received from remote server.

System Action: The transfer ends. Thefile-transfer request is treated as described in themessage sent from the remote server.

User Action: Refer to the explanation of themessage sent from the remote server and takewhatever action it recommends.

DVG102I CHARACTER DATA CONVERSION = conv

Explanation: This message tells you whetherCharacter data conversion was requested.

conv One of the following:

YES Character data conversion wasrequested.

NO Character data conversion wasnot requested.


User Action: None.

DVG103I CCSID = ccsid

Explanation: This message is issued, if characterdata conversion was requested.

ccsid Coded character set identifier of the file.


User Action: None.

DVG104I conv DATA CONVERSION FROM CCSID ccss TOCCSID ccst NOT SUPPORTED

Explanation: You specified coded character setidentifiers to convert character data, but the specifiedcharacter sets are not supported by the system.

conv Conversion typeccss Source CCSIDccst Target CCSID.

System Action: The file transfer ends and NetViewFTP changes the status of the request to finished .

User Action: Omit the character-data conversionparameters or use a different CCSID combination.

DVG105I DATA STARTING WITH char CANNOT BECONVERTED FROM CCSID ccss TO CCSID ccst

Explanation: Part of the data could not beconverted with the specified coded character setidentifiers.

char The first character that could not beconverted

ccss Source CCSIDccst Target CCSID.


User Action: Either specify the correct CCSID forthe data, or omit conversion, or erase the characterthat could not be converted.

DVG106I RECORD PADDING OPTION = padchar

Explanation: Record padding option was specified;padchar identifies the padding character.

System Action: If necessary, the receiving NetViewFTP padds the records with the specified paddingcharacter.

User Action: None.

DVG110I NO MESSAGE PROVIDED BY USER-EXITROUTINE routine FOR FUNCTION function;RETURN CODE = retcd

Explanation: The server received a nonzero returncode from the pre-transfer or post-transfer user-exitroutines. However, no message was found in themessage area, so this standard message was issuedinstead.

routine Name of the user-exit routine.

function OPEN, CLOSE, P, or C. For details, seeNetView FTP Customization.

retcd Return code from exit routine.


DVG111I � DVG121I

System Action: If a pre-transfer user-exit routinetemporarily rejected a file-transfer request, then thetransfer ends. The status that NetView FTP givesthe request depends on the value of the AutomaticTransfer Restart parameter for that request:



Otherwise, the transfer ends and NetView FTPchanges the status of the file-transfer request tofinished .

User Action: Check what caused the user-exitroutine to issue this return code and take whateveraction is appropriate.

DVG111I MESSAGE FROM USER-EXIT ROUTINE routine;MESSAGE = message

Explanation: A pre-transfer or post-transferuser-exit routine passed a message to a server forprinting. If the message is longer than 180characters, NetView FTP truncates the message andshows the truncation with three asterisks (***) as thelast three characters.

routine Name of the user-exit routine.message Message text.


User Action: None.

DVG112I SERVER LOADED USER-EXIT ROUTINE routine

Explanation: A server successfully loaded thepre-transfer or post-transfer user-exit routine with thename routine into its address space.


User Action: None.

DVG113I SERVER FAILED TO LOAD USER-EXITROUTINE routine;SYSTEM COMPLETION (ABEND) CODE OF THELOAD MACRO = abendcd;REGISTER 15 RETURN CODE= reg15

Explanation: The server tried to load a user-exitroutine from the available load libraries, but it wasnot successful.

routine Name of user-exit routine.

abendcd System completion (ABEND) code fromLOAD macroinstruction.

reg15 Register 15 contains a reason code insome cases.

System Action: If the routine was the pre-transferor post-transfer user-exit routine, the server stops. Ifthe routine was a user-written file handler, the filetransfer ends. NetView FTP changes the status ofthe file-transfer request to finished .

User Action: Check the ABEND code in themessage library system codes book for youroperating system.

DVG114I SECURITY VERIFIED BY USER-EXIT ROUTINE

Explanation: The security parameters specified inthe file-transfer request have been verified by thepre-transfer user-exit routine. NetView FTP does nofurther security checking.


User Action: None.

DVG115I POST-TRANSFER JOB SUBMISSIONPREVENTED BY USER-EXIT ROUTINE

Explanation: The request specified post-transferjob submission, but the pre-transfer or thepost-transfer user-exit routine at either the requestingor the responding system prevented the submissionof post-transfer jobs.

System Action: Processing continues, but at thesystem where the user-exit routine prevented the jobsubmission no post-transfer jobs are submitted.

User Action: None.

DVG121I macro ERROR;RETURN CODE = retcd;LENGTH = length;MODULE = modname;OFFSET = offset

Explanation: An error occurred in a NetView FTPcomponent when it attempted to obtain or releasedynamic virtual storage.

macro Macro that encountered the error:

� GETMAIN or GETVIS� FREEMAIN or FREEVIS.

retcd Return code from the macro. For moreinformation about this return code, refer tothe description of the supervisor servicesand macroinstructions for your operatingsystem.

length Length of area to be obtained or released(value not hexadecimal).

modnameName of the module where the macrowas issued.

offset Offset within the module where the macrowas issued (hexadecimal value).


DVG122I � DVG133I

System Action: If the error occurs independently ofa file transfer, the NetView FTP component thatissued the message stops.

If the error occurs during a file transfer, the filetransfer ends and NetView FTP changes the statusof the request to finished ; the server does not stop.

User Action: If the problem persists for:

� FREEMAIN or FREEVIS, contact your IBMSupport Center.

� GETMAIN or GETVIS, increase the size of theaddress space or partition in which the NetViewFTP component that issued the message runs.

DVG122I macro MACRO FAILED;RETURN CODE = retcd

Explanation: A NetView FTP component issued anESTAE or SNAP macroinstruction that failed.

macro Macro that failed:

� ESTAE � SNAP.

retcd Return code from the macro.

System Action: For:

� ESTAE, the abnormal termination exit is notactivated

� SNAP, no storage dump is taken.

NetView FTP processing continues.

User Action: Analyze the problem using one of thefollowing:

� MVS/XA Macro Instruction Reference� MVS/ESA Application Development Macro

Reference.

DVG124I DATA SET NAME SPECIFIED IN DDSTATEMENT WITH NAME name COULD NOTBE RETRIEVED;RETURN CODE FROM macro MACRO = retcd

Explanation: A NetView FTP component attemptedto retrieve a data-set name from a DD statement(MVS), but failed.

name The name of the DD statement specifiedin the File Name parameter.

macro The name of the macro used but whichwas not successful.

retcd The code returned by the macro.

System Action: If this error occurred during theprocessing of:

� A server, the transfer ends and NetView FTPchanges the status of the correspondingfile-transfer request to finished .

� The queue handler, the queue handler stops.

User Action: Analyze the return code using thesystem data administration book for your operatingsystem.

If the problem was due to a user error, correct theDD Name specified in your request or contact yoursystem administrator for the DD Name specified inthe server JCL statements. If you solved theproblem, then resubmit the request or restart thequeue handler.

If the problem was not due to a user error and theproblem persists, contact your IBM Support Center.

DVG125I FILE ID SPECIFIED IN STATEMENT WITH DLBLOR TLBL NAME name COULD NOT BERETRIEVED;RETURN CODE FROM macro MACRO=retcd

Explanation: A NetView FTP component attemptedto retrieve the file ID from a DLBL or TLBL statementbut failed.

name The name of the file as specified in theFile Name parameter.

macro The name of the macro used but whichwas not successful.

retcd The code returned by the macro.

System Action: If this error occurred during theprocessing of:

� A server, the transfer ends and NetView FTPchanges the status of the correspondingfile-transfer request to finished .

� The queue handler, the queue handler stops.

User Action: Analyze the return code using thefollowing:

� VSE/AF Initial Program Load and Job Control� VSE/AF Diagnosis Reference Supervisor� VSE/ESA System Macros Reference.

If the problem was due to a user error, correct theFile Name specified in your request or contact yoursystem administrator for the name specified in theserver DLBL or TLBL statements. If you solved theproblem, then resubmit the request or restart theNetView FTP partition.

If the problem was not due to a user error and theproblem persists, contact your IBM Support Center.

DVG133I ERROR IN MACRO macro;RETURN CODE = retcd

Explanation: One of the macros that NetView FTPused encountered an error.

macro The macro that encountered an error; itcan be any of the following:

EXTRACT Extracts information for tapeunits.

SUBSID Asks for information fromoperating system or notifiesthe operating system that aVSE subsystem is working.


DVG141I � DVG144I

CPCOM Sends file-transfer completionmessages to a VM user. Themacro return code is takendirectly from the CP MSGcommand. Possible valuesare 30, 45, and 57. Thesevalues usually indicate that auser ID is not valid or was notreceiving.

LABEL Gets label information.

retcd Return code from macro.

System Action: Processing continues but NetViewFTP may terminate during subsequent processing.

User Action: If the error did not cause NetViewFTP to terminate, stop the NetView FTP partition.For further information, see one or more of thefollowing:

� VSE/AF Initial Program Load and Job Control� VSE/AF Diagnosis Reference Supervisor� VSE/ESA System Macros Reference� VM CP Commands.

Correct the error before restarting the NetView FTPpartition.

DVG141I INVALID RECORD LENGTH length

Explanation: The receiving server received arecord that does not fit into its I/O buffer. Thefollowing conditions can cause this error:

� The record length is zero or greater than 32 760for a fixed-length record.

� The record length is zero or greater than 32 756for a variable-length record.

� The length of a fixed-length or fixed-blockedrecord sent is not equal to the record length asspecified at the receiving location.

� A variable, variable-blocked, or undefined recordexceeds the physical block size defined for thereceiving data set.

length Length of the record in error.


User Action: Correct the error that caused thismessage to be issued and resubmit the file-transferrequest.

DVG142I RECORD recnum CONTAINS USER DATAWHOSE LENGTH EXCEEDS THE MAXIMUM OFmaxlen ALLOWED FOR THE SPECIFIED DATASET

Explanation: NetView FTP received a recordwhose user data exceeds the maximum allowed forthe record length defined for the receiving data set.

recnum The number of the record in error.

maxlen The maximum allowable length of userdata within one record of the receivingdata set.

System Action: The file transfer ends and NetViewFTP changes the status of the request to finished.


DVG143I LENGTH OF RECORD recnum IS NOT EQUALTO THE RECORD LENGTH reclen OF THERECEIVING FILE

Explanation: The length of a sending record is notequal to the length of the record at the receivinglocation. Transfer record of variable or smallerlength into a data set with fixed-length record, specifya padding character in the request.


reclen The length of a record at the receivinglocation.



DVG144I INVALID RECORD LENGTH FOR RECORDrecnum

Explanation: The length of a record is greater thanthe (maximum) length allowed for the data set.



User Action: Use a bigger record size for thereceiving data set and resubmit the file-transferrequest.


DVG149I � DVG155I

DVG149I ERROR DURING VALIDATION OF USER userid;ERROR CODE = error-code

Explanation: The specified user ID and thepassword could not be verified at the local system.The message contains the VSE Access Control errorcode in hexadecimal format.

userid User ID

error-codeVSE Access Control error code:

02 GETVIS failure04 Invalid password08 Invalid user ID10 LOGON phase not found20 Resource table load failure40 Lock not possible.


User Action: Supply the correct parameters, orcheck whether the correct system was called, orboth. Correct the errors and resubmit thefile-transfer request.

DVG150I ACCESS CONTROL USER ID HAS ANINCORRECT LENGTH; USER ID = userid

Explanation: The access control user ID specifiedin a request has an incorrect length.

System Action: NetView FTP rejects the request.

User Action: Specify the correct user ID andresubmit the request.

DVG151I ACCESS CONTROL PASSWORD HAS ANINCORRECT LENGTH

Explanation: The access control password in arequest has an incorrect length.


User Action: Specify the correct password andresubmit the request.

DVG152I ACCESS CONTROL GROUP ID WILL NOT BEUSED FOR A VSE NODE; GROUP ID = groupid

Explanation: A group ID was specified in therequest for a file at a VSE location. Access Controldoes not use group IDs, it ignores the value youspecified.


User Action: Do not specify a value for thisparameter for files at VSE locations.

DVG153I ERROR DURING VALIDATION OF USER userid;RACROUTE RETURN CODE = xx;RACROUTE RETURN CODE = yy;RACROUTE REASON CODE = zz

Explanation: The specified user ID and thepassword could not be verified at the local system.The message contains the SAF return and reasoncodes, and indicates a security violation.

userid User ID

xx Hexadecimal return code from RACROUTE.

yy Hexadecimal return code from RACROUTEENVIR=CREATE.

zz Hexadecimal reason code from RACROUTEENVIR=CREATE.


User Action: Supply the correct securityparameters or check whether the correct system wascontacted. Correct the errors and resubmit thefile-transfer request.

The return codes and the RACROUTE macros aredescribed in:

� MVS/XA Macro Instruction Reference� MVS/ESA Application Development Macro

Reference.

DVG154I REQUEST CONTAINS SECURITY PARAMETERSFOR THIS SYSTEM,BUT ACCESS CONTROL FACILITY IS NOTACTIVE

Explanation: The file-transfer request specifiedsecurity parameters for the system from whichNetView FTP issued this message. However, theuser ID and password specified could not be verifiedbecause the access control facility (RACF, AccessControl, or other facility) is not installed or is notactive, or no pre-queuing user-exit routine wasloaded that could prevent specification of securityparameters.

System Action: The security parameters areignored and the server continues processing.

User Action: Check whether security parametersare required. If not, omit them in subsequentfile-transfer requests.

DVG155I USER userid CANNOT ACCESS FILE file-id

Explanation: One of the following occurred:

� The request contained a value for the User IDsecurity parameter. NetView FTP tried toaccess a file using the authorization of the userspecified for this parameter, but that user wasnot authorized to access the file.


DVG156I � DVG159I

� The request did not contain a value for the UserID security parameter. However, the JCLstatements in the startup job for the NetViewFTP partition at the system on which the file isstored contained an ID statement. NetView FTPtried to access the file using the authorization ofthe user specified in this ID statement, but thatuser was not authorized to access the file.

� The request did not contain a value for the UserID security parameter and the startup job for theNetView FTP partition did not contain an IDstatement. NetView FTP tried to access the fileusing no authorization. It was not authorized toaccess the file.

userid The user ID, if any, that NetView FTPused to try and access the file. If no userID was specified in the request and no IDstatement was specified in the startup jobfor the NetView FTP partition, this field isblank.

file-id The file ID of the file that NetView FTPused to try to access the file.

System Action: Program or transfer ends.

User Action: Check that the correct file ID wasspecified in the request. If so, either specify thecorrect values for the security parameters or arrangefor the NetView FTP partition of the server that is toaccess the file to be given the necessaryauthorization.

DVG156I REQUEST CONTAINS SECURITY PARAMETERSBUT SERVER IS NOT LINKED TO ANAUTHORIZED LIBRARY

Explanation: A request specified access securityparameters to be used to create a temporary RACFenvironment, but the server that processed therequest was not linked to an Authorized ProgramFacility (APF) library.


User Action: Contact your system administrator.

DVG157I RACF NOT ACTIVE;RACF PARAMETERS CANNOT BE RETRIEVED

Explanation: A file-transfer request specified thatthe server was to automatically retrieve values foraccess security parameters and insert them into therequest. The server that processed the requestfailed to retrieve the values because RACF was notactive on its system.

System Action: If the value of the SECPAR servercontrol statement is YES, the server rejects therequest. If the value is NO, the server tries toaccess the data set using its own authorization.

User Action: If the request was rejected, eitherstart RACF or specify the access security parametersexplicitly.

DVG158I ERROR DURING RETRIEVAL OF RACFPARAMETERS FOR USER userid;RACROUTE RETURN CODE = racrretcdRACXTR RETURN CODE = racxretcdRACXTR REASON CODE = racxrsncd

Explanation: A file-transfer request specified thatthe server was to automatically retrieve values foraccess security parameters and insert them into therequest. When the server used the router interfaceto call the RACXTR macro, it encountered an errorand failed to retrieve the values.

userid User ID of the user whose accesssecurity parameters were beingretrieved.

racrretcd Return code from the RACROUTEmacroinstruction.

racxretcd Return code from the RACXTRmacroinstruction.

racxrsncd Reason code from the RACXTRmacroinstruction.


User Action: Either correct the RACF error orspecify the access security parameters explicitly.Refer to the RACF manual.

DVG159I SECURITY PARAMETERS REQUIRED BUT NOTAVAILABLE

Explanation: The value of the SECPAR parameterin the server’s initialization control statements is YESbut the request did not contain values for the accesssecurity parameters.

If the system that issued this message is an MVSsystem the server at this system tried to retrievevalues for the security parameters automatically, butthey were not available.

If the system that issued this message is a VSEsystem the server at this system needed accesssecurity parameters specified in your file-transferrequest.


User Action: If the system that issued thismessage is an MVS system you must either specifyvalues for the access security parameters explicitlyor have your system administrator define your RACFuser ID and password at this system.

If the system that issued this message is a VSEsystem you must specify values for the accesssecurity parameters explicitly in your file-transferrequest.


DVG160I � DVG164I

DVG160I DATA SET TYPE ERROR;THE TYPE OF ONE DATA SET WAS “USER”AND THE OTHER WAS NOTOr, for NetView FTP V2.2 MVS:

DVG160I FILE ORGANIZATION ERROR;THE ORGANIZATION OF ONE FILE WAS“USER” AND THE OTHER WAS NOT

Explanation: If the data-set type or file organizationof one data set is USER, then the data-set type orfile organization of the other must also be USER.





DVG161I CHECKPOINT RECORD PASSED TOUSER-WRITTEN FILE HANDLEROr, for NetView FTP V2.2 MVS:

DVG161I FILE TRANSFER RESTART FROM restart pointSUPPORTED FOR USER-WRITTEN FILEHANDLER

Explanation: NetView FTP passed a checkpointrecord to a user-written file handler so that it couldresume an interrupted file transfer.

For NetView FTP V2.2 MVS, restart point can be:

BEGINNINGOne of the following occurred:

� A server restarted an interrupted filetransfer. The corresponding requestspecified that the server was not torestart the file transfer from acheckpoint.

� A server tried to restart an interruptedfile transfer from a checkpoint, but theserver could not find a checkpointrecord for the file transfer.

CHECKPOINTA server restarted an interrupted filetransfer using the checkpoint recorded inthe checkpoint data set.


User Action: None.

DVG162I CHECKPOINT RECORD NOT PASSED TOUSER-WRITTEN FILE HANDLEROr, for NetView FTP V2.2 MVS:

DVG162I FILE TRANSFER START FROM BEGINNING OFDATA SET SUPPORTED FOR THEUSER-WRITTEN FILE HANDLER

Explanation: NetView FTP other than NetView FTPV2.2 MVS:NetView FTP did not pass a checkpoint record to auser-written file handler that was to resume aninterrupted file transfer. This might be because thefile-transfer request specified that, in case of aninterruption, the file transfer was not to be startedfrom a checkpoint.

NetView FTP V2.2 MVS: A server started a new filetransfer.

System Action: NetView FTP resumes transferringthe file from the beginning.

User Action: Check that the user-written filehandler that wrote the checkpoint record provided thecorrect checkpoint key data (does not apply toNetView FTP V2.2 MVS).

DVG163I INVALID CHECKPOINT RECORD FOUND FORFILE TRANSFER WITH USER-WRITTEN FILEHANDLERS

Explanation: When a file transfer is interrupted, thereceiving server flags the checkpoint record it writesas belonging to a file transfer that uses eitheruser-written file handlers or NetView FTP filehandlers. Before restarting such a file transfer froma checkpoint, a server determined that the flag of thecheckpoint record it retrieved was pertaining to auser-written file handler. Either the value of theData-Set Type parameter was changed when thefile-transfer request was resubmitted, or the filehandler supplied incorrect checkpoint key data withthe OPEN function.



DVG164I INVALID CHECKPOINT RECORD FOUND FORTRANSFER WITH NETVIEW FTP FILEHANDLERS

Explanation: When a file transfer is interrupted, thereceiving server flags the checkpoint record it writesas belonging to a file transfer that uses eitheruser-written file handlers or NetView FTP filehandlers. Before restarting such a file transfer froma checkpoint, a server determined that the flag of thecheckpoint record it retrieved was pertaining to auser-written file handler. Either the value of theData-Set Type parameter was changed when thefile-transfer request was resubmitted, or the filehandler supplied incorrect checkpoint key data withthe OPEN function.


DVG165I � DVG171I



DVG165I MESSAGE ISSUED BY USER-WRITTEN FILEHANDLER modulename;MESSAGE = message

Explanation: The user-written file handler, with theload module name modulename, passed a messageto NetView FTP for printing. If the message is longerthan 180 characters, NetView FTP truncates themessage and shows the truncation with threeasterisks (***) as the last three characters. NetViewFTP can print up to ten messages after each call ofa user-written file handler.


User Action: Check the message from theuser-written file handler.

DVG166I RETURN CODE ISSUED BY USER-WRITTENFILE HANDLER modulenameFOR FUNCTION function;RETURN CODE = retcd

Explanation: NetView FTP received an allowed butnonzero return code from the user-written filehandler. No message was found in the messagearea.

modulename Name of user-written file handler.

function The function that NetView FTP calledthe user-written file handler for:

� CLOSE � GET � OPEN � POINT � PUT.

retcd The hexadecimal return code fromthe user-written file handler.

System Action: Continuation of the file transferdepends on the return code.

User Action: Contact your system administrator.The interface functions that NetView FTP uses withuser-written file handlers are described in NetViewFTP Customization.

DVG168I INVALID RETURN CODE ISSUED BYUSER-WRITTEN FILE HANDLER modulenameFOR FUNCTION function;INVALID RETURN CODE = retcd

Explanation: The user-written file handler canreturn only specifically defined return codes toNetView FTP.

modulename Name of user-written file-handlermodule.

function The function that NetView FTP calledthe user-written file handler for:

� CLOSE � GET � OPEN � POINT � PUT.

retcd The hexadecimal return code fromthe user-written file handler.


User Action: Contact your system administrator.Check if the user-written file-handler moduleobserves the return code rules. The functions thatNetView FTP uses with user-written file handlers andthe rules for return codes are described in NetViewFTP Customization.

DVG169I INVALID I/O AREA LENGTH FROMUSER-WRITTEN FILE HANDLER modulename

Explanation: Upon return from the OPEN functionof the user-written file handler with the load modulename modulename, the server expects a positivevalue in the field that designates the length of the I/Oarea. This enables the server to get storage for thisarea. The value found was not an allowed value.


User Action: Contact your system administrator.Check whether the user-written file handler suppliesa correct I/O area length when returning from theOPEN function to NetView FTP (refer to NetViewFTP Customization).

DVG170I INVALID RECORD LENGTH FROMUSER-WRITTEN FILE HANDLER modulename

Explanation: Upon return from the GET function ofthe user-written file handler, with the load modulename modulename, the server expects a positivevalue in the field that designates the length of therecord, so that the server is able to compress andsend the record. The value found was not positive,or exceeded the I/O area length.


User Action: Contact your system administrator.Check if the user-written file handler supplies acorrect record length when returning from the GETfunction to NetView FTP (refer to NetView FTPCustomization).

DVG171I name ALREADY ALLOCATED;NO DYNAMIC ALLOCATION POSSIBLE

Explanation: The server attempted to dynamicallyallocate a data set, but the ddname (MVS) orfilename (VSE) was already in use in this addressspace.


DVG175I � DVG181I

name ddname (MVS) or filename (VSE) that isalready in use.

The server uses the ddname (MVS) or the filename(VSE) for dynamic allocation. Possibly, one of thesewas used in the server startup job (MVS) or in thesystem or partition standard label area.


User Action: Check that the file-transfer request isnot in error, for example, ddname is not used in theserver startup job. If this does not correct the error,contact your system administrator. The server(MVS) or the NetView FTP partition must be stoppedand started again without using the ddname (MVS)or filename (VSE) that NetView FTP uses fordynamic allocation.

DVG175I VSE LABEL ACCESS ROUTINE routine FAILED;RETURN CODE = retcd;FILE NAME = filename

Explanation: An error occurred while NetView FTPwas writing a file label.

As NetView FTP VSE uses VSE system routineswhen writing or reading file labels, this is a VSEsystem problem.

routine Name of the VSE system routine. Can beone of the following:

� ADDLBL � ADDNXL.

retcd Return code (contents of register 15).

filename Name of the file that NetView FTP waswriting a label for.


User Action: If the problem cannot be solved usingthe error code and the function routines ADDLBL orADDNXL, contact your IBM Support Center.

DVG176I VSE LABEL ACCESS ROUTINE routine FAILED;RETURN CODE = retcd

Explanation: An error occurred while NetView FTPwas reading a file label.

As NetView FTP VSE uses VSE system routineswhen writing or reading file labels, this is a VSEsystem problem.

routine Can be one of the following:

� MODGRPL � LOCGRPL � GETNXGL � CLRGRPL � GETLBL.

retcd Return code (contents of register 15).


User Action: If your operating system is VSE/ESA*,start the NetView FTP partition in static partitionsonly. If your operating system is VSE/SP, solve theproblem using the error code and the functionroutines MODGRPL, LOCGRPL, GETNXGL,CLRGRPL, or GETLBL. If the problem persists,contact your IBM Support Center.

DVG177I (un)labeled TAPE(S) FOR FILE-ID = file-idSHOULD BE MOUNTED IN THE FOLLOWINGSEQUENCE ON DEVICE devadr IF NOALTERNATE DRIVE IS ASSIGNED;VOLSER = volser

Explanation: Job allocation for tape(s) wasrequested and NetView FTP found the serialnumbers specified.

NetView FTP writes the address of the first assignedtape device (normally SYS001) and the volume serialnumbers in the sequence in which they werespecified in the VOLSER list, to inform the operatorabout mount requests.

(un)labeled Labeled or unlabeled tapefile-id File IDdevadr Device addressvolser Volume serial number.


User Action: Mount the correct volume(s) ifnecessary.

Note: If an alternative drive is assigned, NetViewFTP cannot determine the device address of thisdrive. Therefore, you must specify the correctmounting.

DVG180I NO DATA SET NAME CAN BE CREATED FORTHE RECEIVING DATA SET

Explanation: The file-transfer request did notspecify a data-set name for the receiving data set.Dynamic allocation is invoked for the receivinglocation to create a new data set, but a valid namecannot be created, because there is no inputavailable from which NetView FTP can build adata-set name.


User Action: Specify a valid name for the data setand resubmit the file-transfer request.

DVG181I NO DATA SET NAME WAS SPECIFIED FORTHE RECEIVING DATA SET; NETVIEW FTPGENERATED THE DATA SET NAME: dsname

Explanation: The file-transfer request did notspecify a data-set name for the receiving data set.NetView FTP can build the data set name dsname.


User Action: None.


DVG182I � DVG188I

DVG182I DYNAMIC ALLOCATION ERROR;ERROR TYPE = type;DATA SET NAME = dsname;RETURN CODE = retcd;INFORMATION REASON CODE = infcode;ERROR REASON CODE = errcode

Explanation: An error occurred during dynamicallocation.

type Error type:

P Permanent allocation error.T Temporary allocation error.

dsname Name of the data set for which a dynamicallocation error occurred.

retcd Return code.

infcode Information reason code.

errcode Error reason code.


For a permanent allocation error, NetView FTPchanges the status of the request to finished .

For a temporary allocation error, the status thatNetView FTP gives the request depends on thevalue of the Automatic Transfer Restart parameterfor that request.

User Action: Refer to the description of thedynamic allocation interface return (DAIR) errors thatcan be found in the online ISPF tutorial. For furtherinformation, refer to:

� MVS/ESA SPL: Application Development Guide� MVS/XA System Macros and Facilities

Volume 1.

If it is a temporary error, the specified data set mightbe currently in use by another address space.

If the status of the file-transfer request was changedto waiting , no action is required. If the status of thefile-transfer request was changed to finished andyou want to transfer the file again, correct the error,and resubmit the new file-transfer request.

DVG185I CONTENTS OF LABEL PARAMETER LISTcontents;FUNCTION REQUESTED = function;CONTENTS OF LABEL BUFFER FOLLOW

Explanation: This message is issued if trace class3 is specified for module DVGEYDL at a VSElocation. It is used for diagnostic purposes to traceerrors related to dynamic allocation.

contents LABEL parameter list.

function Function of LABEL macro.


User Action: Contact your IBM Support Center.

DVG188I DYNAMIC ALLOCATION ERROR;ERROR CODE = error-code

Explanation: An error has occurred during NetViewFTP’s dynamic allocation process.


01 INCORRECT ACCESS MODE

The disk at the receiving systemwas found to be read-only modewhen WRITE access wasrequested.

System Action: Transmissionends.

User Action: Check yourrequest to see whether anothersuitable disk can be used, orcontact your system operator tolink the disk again with theappropriate access mode.

02 NO UNUSED VIRTUALADDRESS AVAILABLE

For the linkage of default andspecified disks NetView FTPsearches for currently unusedvirtual addresses. It starts thesearch with address 490 andends with address FFF. Themessage is issued when nounused virtual address can befound.

System Action: Program ends.

User Action: See if somedevices can be detached fromNetView FTP’s virtual machine.

03 NO UNUSED FILEMODELETTER AVAILABLE

For the linking of default andspecified disks, NetView FTPsearches for currently unused filemodes. It starts the search withfile mode A and ends with filemode Z. The message is issuedif no unused file-mode letter canbe found.

System Action: Program ends.

User Action: See if somedevices can be detached fromNetView FTP’s virtual machine.

04 NO DISK AVAILABLE FORTRANSMISSION

There is no CMS or VSAM diskavailable for transmission, alsono SPECIFIED DISK orDEFAULT DISK.

System Action: Transmissionends.


DVG190I � DVG196I

User Action: Check yourrequest to see whether anothersuitable disk can be used, orcontact your system operator tolink the disk again with theappropriate access mode.

05 INVALID CMS FILENAME

06 INVALID ADDRESS

The address of the virtual devicethat was specified does not existor is not a DASD.

System Action: Program ortransmission ends.

User Action: Check the CMSdisk or VSAM disk controlstatement specification in theinitialization control statement fileor the xVMLINK statement in thetransmission request for correctdisk identification. Correct theerror and restart NetView FTP orthe transmission.

07 WRONG DISK MODE

No disk was accessed under thegiven mode letter.

System Action: Program ortransmission ends.

User Action: Check the CMSdisk or VSAM disk controlstatement specification in theinitialization control statement fileor the xVMLINK statement in thetransmission request, for correctdisk identification. Correct theerror and restart NetView FTP orthe transmission.

08 DCB INFORMATION OF THESENDING FILE UNUSABLE

The logical record length or theblock size of the sending file isbigger than the maximumallowed for MVS. To avoid theloss of data, dynamic allocationfails.

DVG190I DISPOSITION ERROR FOR CMS FILE file-id;ERROR CODE = error-code

Explanation: The disposition parameter has beenspecified for an output CMS file. When processingaccording to the parameter value, an error hasoccurred.

file-id CMS file identification


723 Value OLD was specified but theCMS file does not exist.

724 Value NEW was specified but theCMS file exists already.

System Action: Transmission ends.

User Action: Check the value in the dispositionspecification in your file transmission request andresubmit the request. If necessary, erase an existingCMS file.

DVG191I DISPOSITION ERROR, DATA SET IS ALREADYCATALOGED;DATA SET NAME = dsnameOr, for NetView FTP V2.2 MVS:

DVG191I INCORRECT END-OF-PROCESSING OPTION,DATA SET IS ALREADY CATALOGED;DATA SET NAME = dsname

Explanation: The disposition parameter (other thanNetView FTP V2.2 MVS) or the end-of-processingoption (NetView FTP V2.2 MVS) for a newnon-VSAM data set specifies that it should becataloged when it is created. A test, however,indicated that a data set with this name alreadyexists in the catalog.

System Action: Transmission ends.


� For NetView FTP other than V2.2 MVS changethe disposition parameter to OLD

� For NetView FTP V2.2 MVS change the filestatus option to MUSTEXIST

� Delete the existing data set.

Then resubmit the request.

DVG193I DYNAMIC ALLOCATION ERROR; DATA SET ISCURRENTLY INVOLVED IN ANOTHER FILETRANSFER; DATA SET NAME = name

Explanation: The data set is currently beingtransferred.

name Name of data set involved in file transfer.

System Action: Current transfer continues. Thefile-transfer request that caused the error is rejected.

User Action: Wait until the current transfer finishesand then resubmit the file-transfer request.

DVG196I IDUMP MACRO ISSUED

Explanation: The IDUMP macro has been issued.The dump is sent either to the SYSDUMP data set,or to SYSLST, depending on what you specified forthe VSE JCL OPTION.

System Action: Dump processing continues even ifan error occurs during dumping.

User Action: None.


DVG197I � DVG201I

DVG197I NETVIEW FTP release;SERVER serverid MAINTASK ABNORMALLYTERMINATED;SYSTEM ABEND CODE = sac;USER ABEND CODE = uac

Explanation: The maintask of the server terminatedabnormally.


serverid Server ID of the server.


uac ABEND code set by the server itself.

System Action: The server stops. All file transfersare interrupted.

User Action: For an explanation of the ABENDcodes, refer to Chapter 2, “NetView FTP ABEND,Return, and Reason Codes” on page 109. If theoperator canceled the program, ignore any systemdump.

DVG198I NETVIEW FTP release;SERVER serverid SUBTASK TERMINATEDABNORMALLY;SYSTEM ABEND CODE = sac;USER ABEND CODE = uac

Explanation: The subtask of the server terminatedabnormally.


serverid Server ID of the server.


uac ABEND code set by the server itself.

System Action: The subtask ends. If a file transferwas currently being processed by the subtask, thefile transfer ends also, and if the value of theAutomatic Transfer Restart parameter is:

� YES, NetView FTP changes the status of thefile-transfer request to waiting .

� NO, NetView FTP changes the status of thefile-transfer request to finished .

The reaction of the server depends on the reason forthe termination. For further details, refer to theNetView FTP Installation, Operation, andAdministration book that applies to your operatingsystem and transfer program.

User Action: For an explanation of the ABENDcodes, refer to Chapter 2, “NetView FTP ABEND,Return, and Reason Codes” on page 109. If theoperator canceled the program, ignore any systemdump.

DVG199I DUMP INFORMATION;ACTION CODE = ac;RETURN CODE = retcd

Explanation: A NetView FTP component enteredan ABEND exit routine. This routine issued a systemmacroinstruction to obtain a dump of selectedstorage areas. This message gives informationabout the invocation result.

ac Action code:

01 If the transfer program runsunder MVS then the SNAPmacro was invoked. Otherwisethe SDUMP macro was invoked.

02 The dump was obtained becauseno data set was specified whereit could be stored.

retcd The code returned by the invokedmacroinstruction (valid only for ActionCode 01).

System Action: The transfer program continues itsABEND exit processing. If the Action Code is 01,then a dump is obtained.

User Action: For Action Code 01 and a ReturnCode greater than 0, analyze the problem using oneor more of the following:

� MVS/ESA Application Development Reference:Services for Assembler Language Programs

� MVS/XA Macro Instruction Reference� VM/ESA Group Control System Reference for

370� VM/XA SP Group Control System Command

and Macro Reference� VM/SP Group Control System Macro Reference.

DVG200I PATCH-AREA ENTERED;TRACE ACTIVE

Explanation: This message is issued only when apatch-area trace is performed.

System Action: Trace output is written.Processing continues.

User Action: None.

Originating Module: Module identified in thesymptom record.

DVG201I modulename ENTERED;TRACE ACTIVE

Explanation: NetView FTP took a trace whenentering the module.

modulename The name of the module that is beingentered.


User Action: None.


DVG202I � DVG223I

DVG202I modulename EXITED;TRACE ACTIVE;RETURN CODE = retcd

Explanation: NetView FTP took a trace whenexiting the module.

modulename The name of the module that is beingexited.

retcd Decimal return code passed by thismodule to the calling module.


User Action: None.

DVG220I TRACE OUTPUT FROM USER-EXIT ROUTINEmodulename;TRACE WAS TAKEN before|after CALL FORfunction;TRACE AREA = CONTROL BLOCK SERVINGAS INTERFACE BETWEENNETVIEW FTP AND USER-EXIT ROUTINE

Explanation: To test a user-exit routine, the maininterface between NetView FTP and the user-exitroutine was traced before and after every call of auser-exit routine function.

modulenameLoad module name of user-exit routine.

before|afterCan be one of the following:

BEFORE The trace is taken before thenamed function is called.

AFTER The trace is taken after thenamed function is called.

functionNetView FTP functions:

� CLOSE (user-written file handler)� GET (user-written file handler)� OPEN (user-written file handler)� POINT (user-written file handler)� PUT (user-written file handler)� P (for pre-transfer exit routine)� C (for post-transfer exit routine)� POSTCONV (for post-conversation exit

routine).

These function calls and the user-exit routines aredescribed in NetView FTP Customization.

System Action: Produces trace output.

User Action: None.

DVG221I TRACE OUTPUT FROM USER-EXIT ROUTINEmodulename;TRACE WAS TAKEN before|after CALL FORfunction;TRACE AREA = USER-DEFINED STORAGEAREA

Explanation: To test a user-exit routine, a specifiedstorage area was traced after every call of auser-exit routine function. The user-exit routine mustsupply the beginning address and the length of thestorage area.

modulenameLoad module name of user-exit routine.

before|afterCan be one of the following:

BEFORE The trace is taken before thenamed function is called.

AFTER The trace is taken after thenamed function is called.

functionNetView FTP functions:

� CLOSE (user-written file handler)� GET (user-written file handler)� OPEN (user-written file handler)� POINT (user-written file handler)� PUT (user-written file handler)� P (for pre-transfer exit routine)� C (for post-transfer exit routine)� POSTCONV (for post-conversation exit

routine).

These function calls and the user-exit routines aredescribed in NetView FTP Customization.

System Action: Produces trace output.

User Action: None.

DVG223I REQUEST ORIGINATOR = orig;REQUEST RECEIVED ON yy/mm/dd AThh:mm:ss;SERVER CLASS = class

Explanation: This message gives information aboutthe user ID of the originator of a request.

orig Originator of this file-transferrequest.

yy/mm/dd Date that the file-transfer requestwas received: yy=year, mm=month,dd=day.

hh:mm:ss Time that the file-transfer requestwas received: hh=hour,mm=minute, ss=second.

class Server class as found in thefile-transfer request.


User Action: None.


DVG225I � DVG234I

DVG225I INFORMATION FOR LOCAL SYSTEM;LU NAME = luname

Explanation: This message is the header of thestatistics messages and information related to thelocal server.

luname LU name of the local server thatprocessed the file-transfer request.


User Action: None.

DVG226I INFORMATION FOR REMOTE SYSTEM;LU NAME = luname;SERVER GROUP = nameNETVIEW FTP NAME = ftpname

Explanation: This message is the header of thestatistics messages and information related to theremote server.

luname LU name of remote server.

name The value of the server group, if any.

ftpname Name of the NFTPNAME queuehandler initialization parameter (MVS,VM) or partition initialization parameter(VSE).


User Action: None.

DVG227I OPERATOR STOPPED SERVER;FILE TRANSFER INTERRUPTED

Explanation: The operator stopped a server. A filetransfer that was in progress was interrupted.

System Action: The transfer ends. The receivingserver writes a checkpoint record.

The status that NetView FTP gives the requestdepends on the value of the Automatic TransferRestart parameter for that request:



User Action: Ask the operator if there are serversstarted that process requests of the class of yourrequest. If not, ask the operator to start such aserver. No further action is required if the status ofthe file-transfer request is waiting . If the status ofthe file-transfer request is finished , and you stillwant to transfer the file, correct the error, and add anew file-transfer request to the request queue.

DVG230I TRANSFER PARAMETERS;LOGICAL UNIT TYPE = lutype;TRANSFER MODE = mode

Explanation: This message lists the transferparameters that are in effect for this server.

lutype Logical unit type:

P Responding server initiated filetransfer (it was the primary LU).

S Responding server accepted aremotely-initiated file transfer (itwas the secondary LU).

mode Transfer mode:

S Server sent a file to a remotelocation.

R Server received a file from aremote location.


User Action: None.

DVG233I RECORD FORMAT = recfm;BLOCK SIZE = blk;LOGICAL RECORD LENGTH = lrecl

Explanation: This message lists the DCBparameters of a physical sequential or partitionedorganized data set. For the sending server, they arederived directly from the DCB of the data set. Forthe receiving server, they contain the valuesspecified in the file-transfer request.

recfm Record format:

U UndefinedV VariableF FixedFB Fixed-blockedVB Variable-blockedVS Variable-spannedVBS Variable-blocked-spanned.

blk Physical block size.

lrecl Logical record length (blank if the recordformat is undefined or variable).


User Action: None.

DVG234I EMPTY DATA SET TRANSFERRED

Explanation: No records were transferred, but thefile transfer ended normally.


User Action: Check that the correct data set wasspecified in the file-transfer request.


DVG236I � DVG241I

DVG236I NUMBER OF RECORDS TRANSMITTED = recno

Explanation: This message is for information only,to indicate that the file transfer has ended. If the filetransfer was interrupted, the sending location usuallyshows a higher number than the receiving location.This discrepancy came about because some recordswere lost due to the error.

recno The number of records transmitted.


User Action: None.

DVG237I DATA SET INFORMATION:DATA SET NAME = dsname;DD NAME = ddname;DATA SET TYPE = dst;DYNAMIC ALLOCATION REQUESTED = x;PDS MEMBER NAME = pdsmnamOr, for NetView FTP V2.2 MVS:

DVG237I DATA SET INFORMATION:DATA SET NAME = dsname;DD NAME = ddname;FILE ORGANIZATION = dst;DYNAMIC ALLOCATION REQUESTED = x;PDS MEMBER NAME = pdsmnam

Explanation: This message shows some of themain data set parameters.

dsname Data-set name.

ddname Symbolic name of the DD statementname, either as used by NetView FTP(local server) or as specified in thefile-transfer request (remote server).

dst One of the following:

� VSAM � PS � PO� UNLAB (other than NetView FTP

V2.2 MVS)� LAB (other than NetView FTP V2.2

MVS)

x Y(ES-dynamic allocation used) or N(O-joballocation used).

pdsmnamSingle PDS member name; only shown ifthe name of a single member is specifiedin the file-transfer request.


User Action: None.

DVG238I USER CATALOG ID = ucatid

Explanation: This message is issued if, for aVSAM data set, a user catalog is dynamicallyallocated.

ucatid Data-set name of the user catalog.


User Action: None.

DVG239I VOLUME SERIAL NUMBER no = volser

Explanation: This message is issued if the filetransfer involved one of the following:

� A physical sequential data set� A partitioned organized data set� A VSAM data set.

The first volume serial number is retrieved byNetView FTP after the file is opened. The remainingvolume serial numbers, if any, are taken from thefile-transfer request.

no Number from 1 to 9.volser Volume serial number.


User Action: None.

DVG240I EXPIRATION DATE = date

Explanation: This message is issued for adynamically-allocated physical sequential data set ora partitioned organized data set.

date Expiration date or retention periodspecified in a request. If it is in the formyyddd then it is the expiry date. If it is inthe form dddd then it is the retentionperiod.


User Action: None.

DVG241I UNIT = unit

Explanation: This message is issued for adynamically allocated physical sequential orpartitioned organized data set.

unit Device type, specified in the file-transferrequest, of the unit on which the data setresides.


User Action: None.


DVG242I � DVG253I

DVG242I VSAM KSDS OPTION = option

Explanation: This message gives informationconcerning the KSDS processing options for a VSAMkey-sequenced data set (KSDS). If this message isissued by the remote server, the KSDS option isshown without checking to see if the data set at theremote location is really a KSDS.

option The following KSDS options are valid:

� MERGE � ADDBEG � ADDKEY � REPKEY � DELKEY.


User Action: None.

DVG243I DATA SET IS ALLOCATED WITH DISPOSITIONdispOr, for NetView FTP V2.2 MVS:

DVG243I DATA SET IS ALLOCATED WITH FILE STATUSOPTION statopt, FILE ACCESS OPTION accopt,AND END OF PROCESSING OPTION OK eopok,NOT OK eopno

Explanation: NetView FTP issues this messagewhen it dynamically allocates a data set.

disp The value of the Disposition parameterthat the server used to allocate the dataset.

statopt The value of the File Status Option thatthe server used to allocate the data set.

accopt The value of the File Access Option thatthe server used to allocate the data set.

eopok The end-of-processing option after a filewas transferred successfully.

eopno The end-of-processing option after a filewas not transferred successfully.


User Action: None.

DVG244I SECURITY PARAMETERS;USER ID = parm1;GROUP ID = parm3

Explanation: The message is issued when at leastone value was specified for the access securityparameters.

parm1 First access security parameter value(user ID).

parm3 Third access security parameter value(group ID).

The second value, parm2, is not shown because itcan be a password.


User Action: None.

DVG245I VM DISK IDENTIFICATION = diskid, diskaddress

Explanation: This is the identification of the VMdisk used at the VM system from which NetView FTPissued this message. The values are taken from thefile-transfer request.

diskid The user ID of the owner of the disk.

diskaddressDisk address, as defined in the directoryof the disk user ID.


User Action: None.

DVG250I REQUEST AVAILABLE FOR restart typeTRANSFER RESTART

Explanation: The server issues this message whena file transfer is interrupted. The restart type can beone of the following:

AUTOMATICThe request is rescheduled and will beautomatically restarted. This is onlypossible if a temporary error occurredand the value of the Automatic TransferRestart parameter specified in therequest is YES.

MANUAL The request can be manually restarted.This is possible if an error occurred thatrequires manual intervention or if thevalue of the Automatic Transfer Restartparameter specified in the request is NO.

System Action: The transfer ends. If thefile-transfer request is available for automatic transferrestart, NetView FTP gives the file-transfer requestthe status waiting . It is available for rescheduling.

If the file-transfer request is available for manualtransfer restart, NetView FTP gives the file-transferrequest the status finished .

User Action: For automatic transfer restart, none.For manual transfer restart, check the cause for theinterruption, correct the error, and submit a restartrequest for the file transfer.

DVG253I FILE SEQUENCE NUMBER = fsno

Explanation: This message is issued if the filetransfer involved a file on a tape device.

fsno File sequence number. Identifies therelative position of a file on a tape device.


User Action: None.


DVG254I � DVG313I

DVG254I NUMBER OF BYTES TRANSMITTED = bytes

Explanation: This message tells you the number ofbytes that were transmitted in an initial transfer. Fordata-set type PO, this number includes bytescontaining directory information and NetView FTPcontrol information. If the file transfer is interrupted,the sending transfer program usually indicates ahigher number than the receiving transfer program.This is because data was lost due to the errorcausing the interruption.

bytes Number of data bytes (uncompressed)transmitted.


User Action: None.

DVG255I TRANSFER STARTED ON yy/mm/dd AThh:mm:ss;TRANSFER ENDED ON yy/mm/dd AT hh:mm:ss;

Explanation: This message is issued when atransfer ends. It tells you when the transfer startedat the sending system and when the transfer endedat the local system.


User Action: None.

DVG256I NUMBER OF BYTES TRANSMITTED SINCELAST CHECKPOINT = bytesOr, for NetView FTP V2.2 MVS:

DVG256I NUMBER OF BYTES TRANSMITTED SINCELAST RESTART = bytes

Explanation: This message is issued when atransfer is restarted. It tells you the number of bytesthat were transmitted since the last restart. Fordata-set type PO, this number includes bytescontaining directory information and NetView FTPcontrol information. The server can restart aninterrupted file transfer from a checkpoint recorded inthe checkpoint file.

If the file transfer is interrupted, the sending transferprogram usually indicates a higher number than thereceiving transfer program. This is because datawas lost due to the error causing the interruption.

bytes Number of data bytes (uncompressed)transmitted.


User Action: None.

DVG299I MODULE DVGCCMDn NOT FOUND

Explanation: One of the NetView FTP componentstried to load a message definition module, but it wasnot available.

n Identifier for the message module, the firstletter of the specified language.

System Action: The NetView FTP componentterminates.

User Action: Create the required message module,or specify the correct language parameter for thefailing component. For further details, refer to theNetView FTP Installation, Operation, andAdministration book that applies to your operatingsystem and transfer program.

DVG311I SERVER TERMINATION REQUESTED DUE TOEXPIRED TERMINATION TIME

Explanation: A server’s termination time hasexpired.

System Action: The server waits for the completionof all currently running file transfers. When alltransfers are completed, the server stops. No newfile-transfer requests are processed.

User Action: None.

DVG312I SERVER TERMINATION REQUESTED BYQUEUE HANDLER;TERMINATION TYPE = ttype

Explanation: The queue handler requests that theserver terminates. Usually this is a result of anoperator command to stop a server or the queuehandler.

ttype Can be one of the following:

I Immediate terminationD Delayed termination.

System Action: If delayed termination wasrequested the server waits for the completion of allcurrently running file transfers. When all transfersare completed, the server stops. No new file-transferrequests are processed. If immediate terminationwas requested, the server interrupts all transfers andterminates immediately.

User Action: None.

DVG313I SERVER CANNOT ATTACH SUBTASK;RETURN CODE = retcd

Explanation: The server tried to attach one of itslocal or remote request handlers via the ATTACHmacroinstruction, but failed.

retcd Return code from ATTACH macro.


DVG314I � DVG321I

System Action: The server waits for the completionof all currently running file transfers. When alltransfers are completed, the server terminates.

User Action: Check the return code from theATTACH macroinstruction. Refer to:


� MVS/XA Supervisor Services and Macros� VM/ESA Group Control System Reference for

370� VM/XA SP Group Control System Command

and Macro Reference� VM/SP Group Control System Macro Reference.

DVG314I SERVER TERMINATING DUE TO A SEVEREERROR IN A SUBTASK

Explanation: An error occurred in the local- orremote-request handler of a server.


User Action: Check the job log and the server logfile for messages that help you analyze the problem.After you have corrected the problem, restart theserver.

DVG315I SERVER TERMINATING DUE TO AN ACF/VTAMCOMMUNICATION ERROR

Explanation: An error occurred when a server triedto communicate with ACF/VTAM. Possibly, a logicalunit was deactivated or ACF/VTAM terminated.


User Action: Solve the ACF/VTAM problem.Check the job log and the server log file formessages that help you analyze the problem. Afteryou have corrected the problem, restart the server.

DVG316I SERVER TERMINATING DUE TO A LOGICERROR IN A SUBTASK

Explanation: An error occurred in the local- orremote-request handler.


User Action: Save the job log and the server logfile.

Contact your IBM Support Center.

DVG317I SERVER TERMINATING DUE TO AN ERROR INTHE QUEUE HANDLER

Explanation: An error occurred in the queuehandler. The queue handler ordered the server toterminate immediately.

System Action: The server interrupts all transfersand terminates immediately.

User Action: Save the job log and the queuehandler log file.


DVG318I SERVER TERMINATING DUE TO AN ERROR INMESSAGE HANDLING

Explanation: An error occurred in the messagehandling of a server. Probably an I/O error occurredwhile the server was writing messages.


User Action: Check the job log and the server logfile for messages that help you analyze the problem.After you have corrected the problem, restart theserver.

DVG319I servername CANNOT ACCEPT ANOTHERSESSION AT PRESENT, DUE TO A SHORTAGEOF VIRTUAL STORAGE

Explanation: The server with the name servernamecannot allocate enough virtual storage to allow it toaccept another conversation.

System Action: The server that processed therequest changes the request’s not-before time to thecurrent time plus the server’s delay time. The serverthen puts the request back into the queue andchanges the request’s status back to waiting . Therequest is reprocessed later.

User Action: None.

DVG321I SINGLE MODE SERVER IS TERMINATING

Explanation: A server running in single modefinished transferring a file and is now terminating,regardless of whether the file transfer endedsuccessfully or not.

System Action: The server terminates.

User Action: Check the server return code forsingle servers. Refer to Figure 2 on page 109.


DVG325I � DVG331I

DVG325I SPECIFIED NOT-AFTER TIME HAS ALREADYPASSED

Explanation: NetView FTP attempted to process afile-transfer request where the specified not-after timehad already passed.

System Action: No file transfer was performed.The request is regarded as finished.

User Action: Add a new request with a laternot-before time to the request queue.

Note: This message is accompanied by reasoncode 136 (RSSTIMEX).

DVG327I FILE TRANSFER INTERRUPTED BY USER

Explanation: A user of one of the user interfaceroutines issued a DELETE queue handler commandwhile the file-transfer request was active .

System Action: The file transfer ends. The servertakes a checkpoint, so, if there is a manual restart,the interrupted file transfer can be resumed from thecheckpoint. If the transfer program is not NetViewFTP V2.2 MVS, the file-transfer request is deletedfrom the request queue.

User Action: None.

DVG328I ERROR IN SERVER MAINTASK;FILE TRANSFER INTERRUPTED

Explanation: An error occurred in a servermaintask. All running transfers on the server areinterrupted, and the server is terminated.

System Action: The file transfer ends. The servertakes a checkpoint. The status that NetView FTPgives the request depends on the value of theAutomatic Transfer Restart parameter for thatrequest.


� Waiting , ask the operator if there is a serverstarted that processes the class of the requestthat was interrupted. If not, ask the operator tostart one.

� Finished , and you want the file transfer to bereestablished, ask the operator if there is aserver started that processes the class of theinterrupted request. If not, ask the operator tostart one. After one is started, resubmit therequest.

� Finished , and you do not want the file transferto be reestablished, no action is required.

DVG329I ERROR IN QUEUE HANDLER;FILE TRANSFER INTERRUPTED

Explanation: An error occurred in the queuehandler. All running transfers on all servers areinterrupted. All servers are stopped immediately.

System Action: The transfer ends. The servertakes a checkpoint for each of the file transfers inprogress.

User Action: Ask the operator to restart the queuehandler and the servers when the problem is solved.

DVG330I XMIT COMMAND CARRIED OUT FOR USERuserid;ERROR CODE = error-code

Explanation: A server sent the file-transfer report tothe user specified in the file-transfer request.

userid User ID.


0 Report file could be sent.20 Dynamic allocation of SYSOUT

file failed.22 OPEN error on SYSOUT file.24 OPEN error on input file.28 I/O error on input file.32 I/O error on SYSOUT file.36 CLOSE error on SYSOUT file.38 CLOSE error on input file.


User Action: If the return code is zero, then noaction is required. If the return code is not zero,check the respective file.

DVG331I ERROR DURING ATTACH OF TSO COMMANDcmd;RETURN CODE = retcd

Explanation: An error occurred during theprocessing of the ATTACH macroinstruction for theTSO commands XMIT or SEND.

cmd XMIT or SEND.

retcd Return code from ATTACH macro.

The user specified in the request cannot be notified.


User Action: Analyze the problem using the returncode description in:


� MVS/XA Supervisor Services and Macros.

Correct the error for subsequent runs.


DVG332I � DVG334I

DVG332I ERROR FROM macname MACRO;RETURN CODE = retcd

Explanation: An error occurred during processingof one of the following macros:

retcd The hexadecimal return code, passed toregister 15 by the macroinstruction.

macnameOBTAIN, DEVTYPE, TRKCALC macro, or

LOCATE-CLocate of VSAM Cluster failed

LOCATE-DRetrieve of Data partparameters failed (expirationdate format YYDDD)

LOCATED2Retrieve of Data partparameters failed (expirationdate format YYYYDDD)

LOCATEDVRetrieve of Data Volumeparameters failed

LOCATE-I Retrieve of Index partparameters failed

LOCATEIVRetrieve of Index Volumeparameters failed

System Action: Processing continues, but not allcharacteristics of the sending data set could beretrieved. The receiving data set is allocated usingdefault values for Space and DCB parameters.

User Action: Analyze the problem using the systemadministration reference for your operating system.

DVG333I DEALLOCATION ERROR;DATA SET NAME = dsname;RETURN CODE = retcd;INFORMATION REASON CODE = irsncd;ERROR REASON CODE = ersncd

Explanation: An error occurred when the servertried to deallocate a previously allocated data set.

dsname Name of the data set.

retcd Return code.

irsncd Information reason code.

ersncd Error reason code.

System Action: The transfer ends. NetView FTPchanges the status of the request to finished . Theserver stops after all file transfers in progress, if any,have ended.

User Action: Check the job log or the server logfile for messages that might help you analyze theproblem. This error might be the result of a previouserror. If this is the only error, the file transfer wassuccessful.

Refer to the description of the dynamic allocationinterface return (DAIR) errors, which can be found inthe online ISPF tutorial. For further information, referto:


Volume 1.

DVG334I SERVER ON THIS NODE HAS INSUFFICIENTFTP LEVEL;REQUIRED FTP LEVEL = ftplevel

Explanation: The file-transfer request for thisserver contains parameters that are valid only for ahigher version or release of NetView FTP.

ftplevel The FTP level of the remote server:

4 FTP Version 2.2 with one of thefollowing compatibility PTFs:

� For communication withFTP V2.2 and NetViewFTP V1 MVS only:FTP V2.2 MVS, UL29109FTP V2.2 VM, UL59949FTP V2.2 VSE, UL32626.

� For communication with FTPV2.2 and NetView FTP:FTP V2.2 MVS, UN03941FTP V2.2 VM, UN02876FTP V2.2 VSE, UN03942.



7 NetView FTP V2 MVS, NetViewFTP VM, and NetView FTP VSE.

System Action: The transfer ends. NetView FTPchanges the status of the request to finished .

User Action: After you have corrected the errors,resubmit the file-transfer request.


DVG336I � DVG337I

DVG336I REMOTE TRANSFER PROGRAM HASINSUFFICIENT FTP LEVEL;FTP LEVEL CODE = code;ERROR CODE = error-code

Explanation: During request checking, it wasdetected that the transfer program on the remotelocation could not perform all the functionsrequested.

code Version of transfer program at the remotelocation, as identified in the server grouptable, or as the remote server identifiesitself at transfer initialization time. Thecodes for the FTP levels are:

31C FTP level 4, V2.2 with one of thefollowing compatibility PTFs:

� For communication withFTP V2.2 and NetViewFTP V1 MVS only:FTP V2.2 MVS, UL29109FTP V2.2 VM, UL59949FTP V2.2 VSE, UL32626.

� For communication with FTPV2.2 and NetView FTP:FTP V2.2 MVS, UN03941FTP V2.2 VM, UN02876FTP V2.2 VSE, UN03942.

11B FTP level 5(NetView FTP V1 MVS)

11A FTP level 6(NetView FTP V1 MVS AFF)

error-codeUp to eight of the following:

01 Omitting receiving data-set nameand receiving ddname is notsupported by the remote transferprogram.

02 Specifying space parameters forthe receiving data set is notsupported by the remote transferprogram.

03 The PO data-set type is notsupported by the remote transferprogram.

04 The VSAM data-set type withNEW disposition is not supportedby the remote transfer program.

05 VS and VBS record formats arenot supported by the remotetransfer program.

06 Transmission of a GDG data setwith relative generation numberspecified is not supported by theremote transfer program.

07 Specifying SFS directory accessparameters is not supported bythe remote transfer program.

08 Specifying a 4-digitExternal/Internal Disk Address isnot supported by the remotetransfer program.

09 Data encryption is not supportedby the remote transfer program.

10 Remote checking of the requestparameters is not supported bythe remote transfer program.

11 Transferring VSAM linear datasets is not supported by theremote transfer program.

12 SMS parameters are notsupported by the remote transferprogram.

13 APPC parameters are notsupported by the remote transferprogram.

14 OS/400 parameters are notsupported by the remote transferprogram.

15 Post-Transfer Job Submissionparameters are not supported bythe remote transfer program.

16 Post-Transfer Program Callparameters are not supported bythe remote transfer program.

17 Internal address and filemodespecification is only valid for FTPV2.2 for VM.

18 DISP=REG is not valid for FTPV2.2 for VM.





Note: A wrong value in the server group table cancause this message to be issued. If you suspect thisis the case, contact your system administrator.

DVG337I DIRECTORY INFORMATION WILL NOT BETRANSMITTED DUE TO INSUFFICIENT FTPLEVEL OF TRANSFER PROGRAM AT THEREMOTE SYSTEM

Explanation: A single PDS member was specifiedin a list.

During request checking, it is detected that theremote transfer program cannot use BPAM/BSAMbuffers for file handling, so it uses QSAM. Thisresults in no directory information being transferredto the partner.

System Action: NetView FTP transfers the affectedmember without any directory information.


DVG338I � DVG353I

User Action: If the directory information is eithernot available or not required, no action is necessary.If vital directory information is missing, thetransmitted member might be unusable at thereceiving location.

DVG338I FILE-TRANSFER COMPLETION MESSAGESENT TO USER userid

Explanation: A server sent the file-transfercompletion message to the user specified in thefile-transfer request.

userid User ID of the originator of the request.


User Action: None.

DVG346I SPACE PARAMETERS;SPACE UNITS = units;PRIMARY SPACE QUANTITY = nnn;SECONDARY SPACE QUANTITY = mmm

Explanation: This message is issued at the end ofthe file transfer if space parameters were specified inthe file-transfer request for the receiving data set.

units One of the following:

BLK BlocksTRK TracksCYL CylindersREC Records.

nnn Primary space quantity of space units.

mmm Secondary space quantity of space units.


User Action: None.

DVG347I SPACE PARAMETERS;AVERAGE LENGTH = nnn

Explanation: This message is issued at the end ofthe file transfer if space parameters were specified inthe file-transfer request for the receiving data set,and if the space units are blocks.

nnn Average length.

If space units are specified as blocks, the value isinterpreted as block length. If space units arespecified as records, the value is interpreted as arecord length.


User Action: None.

DVG348I SPACE PARAMETERS;NUMBER OF DIRECTORY BLOCKS = nnn

Explanation: This message is issued at the end ofthe file transfer if space parameters were specified inthe file-transfer request for the receiving data setand, if the receiving data set is a PDS.

nnn Number of directory blocks.


User Action: None.

DVG350I INFORMATION ABOUT KEY IS MISSING;UNABLE TO DEFINE CLUSTER

Explanation: A server attempted to define a KSDScluster, but the request did not specify the key lengthand offset. This situation only occurs if the sendingdata set is not a VSAM KSDS cluster, and therequest did not specify key length and key offset, orif the sending FTP V2 did not specify theseparameters.


User Action: Provide key length and key offsetwhen resubmitting this request.

DVG351I CLUSTER DEFINED

Explanation: The receiving VSAM cluster wasdefined successfully.


User Action: None.

DVG352I CLUSTER DEFINED BUT MINOR PROBLEMSOCCURRED

Explanation: The receiving VSAM cluster wasdefined, but AMS issued warning messages.


User Action: Check the log file for DVG357Imessages that contain information about theparameters used to define the cluster, and themessages issued by AMS.

DVG353I CLUSTER COULD NOT BE DEFINED

Explanation: The receiving VSAM cluster could notbe defined.


User Action: Check the log file for DVG357Imessages that contain information about theparameters used to define the cluster, and themessages issued by AMS. If DFP Version 3.1 orolder is installed, you may receive the messageIDC3226I. If this occurs, specify the space units tobe cylinders or tracks. Earlier versions do notsupport space units to be records for a linear dataset.


DVG354I � DVG360I

DVG354I CLUSTER DELETED

Explanation: NetView FTP could not allocate thereceiving VSAM cluster it just defined, so it deletes it.Probably, there was a catalog specified for clusterdefinition that is either not allocated to the job, or isinaccessible because of system defaults.


User Action: The cluster should be defined inanother catalog.

Check the log file for DVG357I messages thatcontain information about the parameters used todefine the cluster, and the messages issued by AMS.

DVG355I CLUSTER DELETED BUT MINOR PROBLEMSOCCURRED

Explanation: NetView FTP could not allocate thereceiving VSAM cluster it just defined, so it deletes it.AMS issued warning messages. Probably, there wasa catalog specified for cluster definition that is eithernot allocated to the job, or is inaccessible because ofthe system defaults.



Check the log file for DVG357I messages thatcontain information about the parameters used todelete the cluster, and the messages issued by AMS.

DVG356I CLUSTER COULD NOT BE DELETED

Explanation: The receiving VSAM cluster could notbe deleted. Probably, there was a catalog specifiedfor cluster definition that is either not allocated to thejob, or is inaccessible due to system defaults.



Check the log file for DVG357I messages thatcontain information about the parameters used todelete the cluster, and the messages issued by AMS.Check the cluster definition and cluster deletionmessages. If a cluster was defined and still exists,delete it manually, if appropriate.

DVG357I message

Explanation: The message is output from AMS andforwarded to the log file.

message The text of the message.


User Action: If a problem occurs during clusterdefinition, use the information in the message tosolve the problem. Several DVG357I messages areissued, which list the control statements passed toAMS, and thereby give the information about the waythe cluster was defined.

DVG359I COMPRESSION METHOD = method;TRANSMISSION RATE = rate;COMPRESSION PERCENTAGE = perc

Explanation:

method Identifies the type of compression used, ifany. Can be one of the following:

NONE No compression used.SNA SNA-type compression with

number compaction used.ADAPT Adaptive data compression

used.

rate Number of uncompressed data bytestransferred divided by the time betweenthe start and the end of the file-datatransfer (in seconds). If the file transfer isinterrupted, the start time becomes thattime from when the transfer is restarted.

perc Number of compressed data bytes dividedby the number of decompressed databytes, multiplied by 100.


User Action: None.

DVG360I DATA SET INFORMATION;DATA SET NAME = dsname;DD NAME = ddname;DATA SET TYPE = type;DYNAMIC ALLOCATION REQUESTED = xOr, for NetView FTP V2.2 MVS:

DVG360I DATA SET INFORMATION;DATA SET NAME = dsname;DD NAME = ddname;FILE ORGANIZATION = type;LABEL TYPE = lab-type;DYNAMIC ALLOCATION REQUESTED = x

Explanation:

dsname Data-set name.

ddname For the requesting server, the ddname itused to allocate the data set. For theresponding server, the ddname specifiedin the file-transfer request.

type Data-set type:

� VSAM � PS � PO� UNLAB (other than NetView FTP

V2.2 MVS)� LAB (other than NetView FTP V2.2

MVS) � USER.


DVG362I � DVG366I


SL Labeled tape

NL Unlabeled tape.

x Y(ES-dynamic allocation used) or N(O-joballocation used).


User Action: None.

DVG362I DATA SET INFORMATION;DATA SET NAME = name;DATA SET TYPE = type;PDS MEMBER NAME = member-nameOr, for NetView FTP V2.2 MVS:

DVG362I DATA SET INFORMATION;DATA SET NAME = name;FILE ORGANIZATION = type;LABEL TYPE = lab-type;PDS MEMBER NAME = member-name

Explanation: This message gives information abouta data set being sent or received.

name Name of the data set.

type Type of the data set. Valid types are:

� VSAM � PS � PO� LAB (other than NetView FTP V2.2

MVS)� UNLAB (other than NetView FTP

V2.2 MVS) � USER.


SL Labeled tape

NL Unlabeled tape.

member-nameName of the data-set member.


User Action: None.

DVG363I DATA SET INFORMATION;DATA SET NAME = name;DATA SET TYPE = typeOr, for NetView FTP V2.2 MVS:

DVG363I DATA SET INFORMATION;DATA SET NAME = name;FILE ORGANIZATION = typeLABEL TYPE = lab-type

Explanation: This message gives information abouta data set being sent or received.

name Name of the data set.

type Type of the data set. Valid types are:

� VSAM � PS � PO� LAB (other than NetView FTP V2.2

MVS)� UNLAB (other than NetView FTP

V2.2 MVS) � USER.


SL Labeled tape

NL Unlabeled tape.


User Action: None.

DVG364I CHECKPOINTING INTERVAL = mmm unit

Explanation: This message tells you the currentvalue for the checkpoint interval.

mmm Either number of RUs or time intervalbetween checkpoints.

unit Unit in which checkpointing interval ismeasured; can be one of the following:

SEC Number of secondsRU Number of RUsKB Number of kilobytes.


User Action: None.

DVG366I CURRENTLY ONLY number MEMBERS CAN BEoption

Explanation: Not enough space is available tostore the complete member selection or exclusionlist. The problem might be:

� Temporary, because it is due to a temporaryCSA shortage

� Permanent, because it is due to a redefinition ofthe request queue or of the amount of CSAavailable to NetView FTP.

number The maximum number of members thatcan be currently processed.


DVG367I � DVG371I

option Can be one of the following:

SELECTEDA member selection list is specified.

EXCLUDEDA member exclusion list is specified.


User Action: Query your request. If the status isdeferred (D) then try again later. If the status isblocked (B) then contact your system administrator.

DVG367I number MEMBERS COMPLETELYTRANSMITTED

Explanation: This message tells you how manyPDS members were completely transmitted to thereceiving server (that is, end-of-member wasencountered for this number of members). If thetransmission could not be completed, a subsequentmember might already be partially transmitted.


User Action: None.

DVG368I INVALID MEMBER NAME member FOUND;ERROR CODE = error-code

Explanation: One of the PDS member namesspecified in the file-transfer request does not followthe naming conventions for PDS members.

member Member that does not follow the namingconventions for PDS members.


01 Incorrect name specified for oneof the following:

� A single member� A member to be sent,

specified in a memberselection list.

02 Incorrect new name specified fora member to be received,specified in a member selectionlist.

03 Incorrect name specified for amember specified in a memberexclusion list.





DVG369I DUPLICATE MEMBER NAME member FOUND;ERROR CODE = error-code

Explanation:

member A member that was specified more thanonce in a member selection or exclusionlist.


01 Duplicate name specified for oneof the following:

� A single member� A member to be sent,

specified in a memberselection list.

02 Duplicate new name specified fora member to be received,specified in a member selectionlist.

03 Duplicate name specified for amember specified in a memberexclusion list.





DVG370I number MEMBERS SUCCESSFULLY STOWED

Explanation: This message tells you how manyPDS members were successfully stowed in thereceiving PDS.

number Number of PDS members stowed.


User Action: None.

DVG371I MEMBER member1 STOWED AS member2 INRECEIVING PDS

Explanation: A member of the sending PDS wassuccessfully stowed in the receiving PDS.

member1 The name of the member in the sendingPDS.

member2 The name under which the member is tobe stowed in the receiving PDS.


User Action: None.


DVG372I � DVG378I

DVG372I MEMBER member NOT TRANSFERRED TO THERECEIVING PDS

Explanation: Because of the PDS option specifiedin the file-transfer request, a member of the sendingPDS was not transferred to the receiving PDS. Thereason for this message depends on the PDS optionspecified:

Option Reason

I PDS member member would have beensent to the receiving PDS, and insertedthere, with the same name or with thenew name specified in the request, butthe corresponding member alreadyexisted.

U PDS member member should have beensent to the receiving PDS to update anexisting member. However, thecorresponding member was not found inthe receiving PDS.


User Action: None.

DVG373I EMPTY RECEIVING DATA SET ALLOCATED

Explanation: A receiving data set, containing nomembers, was allocated.


User Action: If this is what you want, no furtheraction is required. If not, correct the error andresubmit the request.

DVG374I SPANNED RECORDS NOT SUPPORTED

Explanation: NetView FTP cannot transfer a PDSwith spanned records.


User Action: None.

DVG375I PDS IS UNMOVABLE

Explanation: NetView FTP cannot transfer a PDSthat is marked as unmovable.


User Action: None.

DVG376I SENDING AND RECEIVING DATA SETATTRIBUTES ARE INCOMPATIBLE

Explanation: NetView FTP cannot transfer a PDS ifone of the following is true:

� Record format is not the same for the sendingand receiving PDS.

� Both PDSs have fixed record format and thereceiving PDS has a record length different fromthe sending PDS.

� Both PDSs have variable record format and thereceiving PDS has a record length smaller thanthe sending PDS.

� Both PDSs have undefined record format andthe receiving PDS has a physical block sizesmaller than the sending PDS.

� Reblocking and TTR translation is required.

� Data-set organization of the receiving data set isdifferent from DSORG specified in the request.


User Action: None.

DVG377I RESTART ERROR; MEMBER member NOTFOUND

Explanation: NetView FTP tried to restart aninterrupted transfer from a checkpoint. Thecheckpoint record specified that the transfer shouldbe restarted with the member member. The specificmember cannot be found in the sending PDS.

System Action: The file transfer is restarted fromthe beginning.

User Action: None.

DVG378I RESTART ERROR; MEMBER memberINCOMPLETE

Explanation: NetView FTP tried to restart theinterrupted file transfer from a checkpoint.

The server retrieved, from the checkpoint data set,the number of the record with which it was tocontinue the file transfer. While searching throughthe member for that record, end of member (EOM)was reached and the record was never found.

This situation can occur if:

� The member to be restarted with has fewerrecords than have already been transferred.

The member to be sent was changed beforerestart.

� The number of records in the temporary memberat the receiving side (restart depository) hasfewer records than already transferred.

The temporary member was changed before thefile transfer was restarted. In this situation,message DVG236I in the sending and receivinglog files can indicate a different number oftransferred records.


User Action: Change the value of the Restart fromCheckpoint parameter to NO and resubmit thefile-transfer request.

Note: If the file-transfer request is resubmitted withthe restarting from checkpoint option a second time,the restart takes place from the beginning of themodified member. All previously transferredmembers remain unchanged in the receiving PDS.


DVG379W � DVG379W

DVG379W AT LEAST ONE TTR COULD NOT BETRANSLATED FOR MEMBER member

Explanation: At least one TTR in member memberdoes not correspond to a block of this member.


User Action: Check whether the member receivedis usable.

DVG380I i/o-operation TERMINATED ABNORMALLY;ABEND CODE = abendcd

Explanation: An ABEND occurred during anOPEN, WRITE, or STOW operation.

i/o-operation Input/output operation attempted.

abendcd System or user ABEND code. It isdescribed in the message librarysystem codes book for your operatingsystem.


User Action: Correct the error and resubmit thefile-transfer request.

DVG381I i/o operation ERROR;RETURN CODE = retcd;REASON CODE = rsncd

Explanation: An I/O error occurred during a BLDLor STOW operation.

i/o-operation Input/output operation attempted.

retcd Return code.

rsncd Reason code.


User Action: Examine the return and reason codesusing one of the following:



Correct the error, and restart the file transfer.

DVG382W NOTELIST OF MEMBER member CONTAINEDFEWER POINTERS THAN INDICATED IN TTR

Explanation: The number of pointers indicated inthe TTR of a note list was greater than the numberof pointers actually contained in that note list. Thismessage indicates an error during BPAM processingof PDSs, which is caused beyond the scope ofNetView FTP or indicates a member in error.

member PDS member name.


User Action: Check whether you can browse andedit the member, and that the content of the memberis correct. If the member is a load module, try it if itis still executable. If it is OK, ignore this message.

DVG383I MORE THAN ONE NOTELIST TTR FOUND FORMEMBER member

Explanation: More than one TTR that points to anote list was found in a PDS directory entry. ATTRX field in the user data part of the directory istreated as a note list TTR, if the X field is not X'00'.

member Name of failing member.


User Action: None.

DVG384I SELECTED MEMBER member NOT FOUND INSENDING PDS

Explanation: A PDS member was selected thatcannot be found in the sending PDS. Possibly, youspecified the wrong member name or the membermay have been deleted.


User Action: Make sure the member exists in thePDS and the name you specify is correct. Resubmitthe request.

DVG385I SESSION RECOVERY FAILED

Explanation: The sending server repositions to thelast recently processed member and tries to read therecords until the one is found during which thetransfer was interrupted. However, end-of-memberoccurred before this record could be found.

This situation can occur if the member to berestarted has fewer records than have already beentransferred. The member to be sent was changedbefore the session recovery was complete.

System Action: The file transfer ends.

User Action: Change the value of the restart fromthe checkpoint parameter to NO and resubmit thefile-transfer request.

DVG386I FILE TRANSFER RESTARTED WITH MEMBERmember

Explanation: The file transfer of a PDS is restarted,beginning with member member.


User Action: None.


DVG387I � DVG401I

DVG387I MESSAGES SUPPRESSED; MESSAGE BUFFERTHRESHOLD REACHED

Explanation: The message buffer threshold valuewas reached. All further DVG357I, DVG371I,DVG372I, and DVG842I messages are suppressed.


User Action: None.

DVG388I EXCLUDED MEMBER member NOT FOUND INSENDING PDS

Explanation: The PDS member member was in alist of members not to be transferred, but was notfound in the sending PDS. Possibly, you specifiedthe wrong member name or the member may havebeen deleted.


User Action: Make sure the member exists in thePDS. Resubmit the request.

DVG389I MEMBER member1 AND MEMBER member2HAVE THE SAME TTR BUT BOTH ARE REALMEMBERS

Explanation: The two PDS members mentioned inthis message are real members (not aliases) andhave the same TTR. This message indicates anerror during BPAM processing of PDS, which iscaused beyond the scope of NetView FTP orindicates a PDS in error.

System Action: The servers terminate the sessionbefore beginning the file transfer.

User Action: Check whether you can accessmembers in the PDS. After you have corrected theproblem, resubmit the transfer request.

DVG391I INVALID PDS OPTION pds-opt FOR MEMBERmember

Explanation: An incorrect PDS option wasspecified for a member.




pds-opt PDS option.

member PDS member name.


DVG392I THE mode SERVER IS NOT A srvmode MODESERVER

Explanation: The server’s running mode does notmatch the running mode required for this request.

srvmode Server’s running mode. Can be one ofthe following:

S SingleC Continuous.

mode Server location. Either LOCAL orREMOTE.

The server’s running mode is first checked using theinformation found in the server group table. If thisvalue matches the required running mode (or if noinformation can be found), the connection isestablished. If it is later detected that the server’srunning mode is not as expected, the transfer ends.This message indicates that there was eitherincorrect information or no information in the servergroup table.


User Action: Change either the running mode toagree with the remote server, or the remote LUname or node ID to agree with the running mode.Resubmit the file-transfer request, specifying a servergroup name (or LU name) that is associated with aserver with the correct running mode.

DVG400I QUEUE HANDLER IS ALREADY ACTIVE

Explanation: An attempt was made to start thesame queue handler twice but the queue handler isalready active. The queue handler represents theentire NetView FTP system, it also keeps theNetView FTP system version, release, andmodification level. While two NetView FTPs with adifferent level can coexist in one system, twoNetView FTPs with the same level cannot. Youstarted NetView FTP with the same level twice.

System Action: The queue handler stops.

User Action: Correct the error as appropriate andrestart the queue handler.

DVG401I QUEUE HANDLER INITIALIZATION FAILED

Explanation: An error occurred during theinitialization of the queue handler. Normally, thismessage is preceded by a message that describesthe failure.


User Action: Check the job log or the queuehandler log-file for messages that might help youanalyze the problem. After you have corrected theproblem, restart the queue handler.


DVG402I � DVG406I

DVG402I QUEUE HANDLER READY

Explanation: The queue handler finished itsinitialization and is now ready to process queuehandler commands.


User Action: None.

DVG403I xxx OF yyy SERVERS HAVE TERMINATED

Explanation: If the queue handler is terminating, itrequests the termination of all servers and waits acertain time to allow for confirmation from eachserver. This message indicates that the time limitwas reached and the queue handler shows thestatus of the confirmations. All servers are forced toterminate if:

� The operator stops the queue handler.

� An irrecoverable error occurred in the queuehandler.

xxx Number of servers that have confirmedtheir termination.

yyy Number of servers active beforetermination began.

System Action: The queue handler terminates.

User Action: Any servers that have not confirmedtheir termination might still be active (use the displaycommand to determine the names of any activeservers). Normally, these soon terminate bythemselves. Cancel any servers that remain in await state for an abnormal length of time.

DVG404I NETVIEW FTP release;QUEUE HANDLER ENDEDON yy/mm/dd AT hh:mm:ss;RETURN CODE = retcd

Explanation: The queue handler completed itsprocessing. The return code shows if any errorsoccurred during processing of the queue handler.The return code is not related to a specific queuehandler command.


yy/mm/dd Date that the queue handler stopped:yy=year, mm=month, dd=day.

hh:mm:ss Time that the queue handler stopped:hh=hour, mm=minute, ss=second.

retcd Queue handler return code.


User Action: None.

DVG405I NETVIEW FTP release;QUEUE HANDLER MAINTASK TERMINATEDABNORMALLY;SYSTEM ABEND CODE = sac;USER ABEND CODE = uac

Explanation: An error occurred in the maintask ofthe NetView FTP queue handler.


sac System ABEND code (refer to themessages and codes book for youroperating system for details).

uac ABEND code set up by the queuehandler.

System Action: The queue handler stops, andnormally provides a dump.

User Action: See Chapter 2, “NetView FTPABEND, Return, and Reason Codes” on page 109.For further details, refer to the NetView FTPInstallation, Operation, and Administration book thatapplies to your operating system and transferprogram. If you think that the problem is not causedby your installation, contact your IBM SupportCenter.

DVG406I NETVIEW FTP release;QUEUE HANDLER SUBTASK TERMINATEDABNORMALLY;SYSTEM ABEND CODE = sac;USER ABEND CODE = uac

Explanation: An error occurred in one of the queuehandler’s service subtasks.


sac System ABEND code (refer to themessages and codes book for youroperating system for details).

uac ABEND code set up by the queuehandler.

System Action: The queue handler stops and,normally, the queue handler notifies the originator ofthe queue handler command, and provides a dump.

User Action: See Chapter 2, “NetView FTPABEND, Return, and Reason Codes” on page 109.For further details, refer to the NetView FTPInstallation, Operation, and Administration book thatapplies to your operating system and transferprogram. If you think the problem is not caused byyour installation, contact your IBM Support Center.


DVG407I � DVG410I

DVG407I QUEUE HANDLER TERMINATION INPROGRESS

Explanation: In an MVS or VM system, thismessage is issued when the operator stops thequeue handler.

In a VSE system, this message is issued wheneverthe queue handler stops. The queue handler stopswhen the NetView FTP partition stops or when thereis an error in the request queue.

System Action: In an MVS or VM system,processing continues. The queue handler stops allstarted servers. When all termination processing hasfinished, the queue handler terminates. In a VSEsystem, the termination of the NetView FTP partitioncontinues.

User Action: None.

DVG408A UNABLE TO ALLOCATE ADDITIONAL CSASTORAGE;REPLY "CONT" OR "TERM"

Explanation: During queue handler startup,NetView FTP checks for the availability of additionalCSA storage. The maximum additional CSA storageallowed for a request is not available.

System Action: NetView FTP waits for the operatorresponse.

User Action: Enter one of the following:

CONTNetView FTP continues, but does not acceptany demand for additional CSA storage. Thefollowing requests are treated as shown:

� Requests requiring the following arerejected:

– PDS member list processing– VSAM cluster definition– A user-written file handler

– VM SFS – SMS – OS/400 – Data encryption – APPC security – Program call – Job submission

– Additional user-exit routine input.

� Requests that are waiting to beprocessed and that require additionalCSA storage are blocked. They are notexecuted until the storage requirementscan be satisfied.

� Information displayed in response to aDISPLAY SERVER subcommand mightbe truncated.

TERMNetView FTP initialization is interrupted andterminates.

To remedy this do any of the following:

� Increase the CSA size in the CSAparameter in member IEASYSxx ofSYS1.PARMLIB. Other address spacesmight also require more CSA.

� Decrease the limiting factor for themaximum additional CSA storage allowedfor one request (CSAELIM QueueHandler Initialization parameter ormaximum request-queue record length).

When doing this, take the following intoconsideration:

� Requests waiting to be processed thatrequire additional CSA storage will beblocked. They are not executed until thestorage requirements can be satisfied.

� Server status information presentedfollowing a DISPLAY SERVERsubcommand might be truncated.

DVG409I TRANSFER REQUEST QUEUE DOES NOTMATCH THE CURRENT LEVEL OF NETVIEWFTP

Explanation: Record 0 of the file-transfer requestqueue does not contain an identifier that matches thecurrent release of NetView FTP. It is no longerpossible to use file-transfer request queues fromprevious NetView FTP releases.

System Action: Queue handler initializationterminates.

User Action: Define a file-transfer request queueusing the job provided with the product.

DVG410I NETVIEW FTP release;QUEUE HANDLER STARTED ON yy/mm/dd AThh:mm:ss;MAINTENANCE LEVEL = mlevel

Explanation: The queue handler finished itsinitialization and has started. It must issue themessage DVG402I before it can process queuehandler commands.

release Release level.

yy/mm/dd Date that the queue handler started:yy=year, mm=month, dd=day.

hh:mm:ss Time that the queue handler started:hh=hour, mm=minute, ss=second.

mlevel Program maintenance-level information.


User Action: None.


DVG411I � DVG416I

DVG411I REQUEST QUEUE IDENTIFICATION = file id

Explanation: The queue handler accessed itsrequest queue.

file id File identification of the request queue.


User Action: None.

DVG412I UNABLE TO ALLOCATE REQUIRED CSASPACE

Explanation: During queue handler initialization,NetView FTP attempted to obtain an area for theFTP MVS shared block (FSB) from CSA subpool231. The allocation failed due to insufficientcontiguous CSA space.


User Action: Try the following:

� Determine whether all the specified FSB slotsare required. If not, reduce their number untilsufficient space is available. For details abouthow to do this, refer to the section on theFSBSLOTS queue handler initializationparameter in the NetView FTP Installation,Operation, and Administration book that appliesto your operating system and transfer program.

� Check for CSA fragmentation.

� Shut down address spaces that use largeamounts of CSA.

� Re-IPL the system.

DVG413I INVALID RECORD FOUND IN SERVER GROUPTABLE;RECORD = record

Explanation: An incorrect specification was foundin a record of the server group table. The syntax ofthe record in the server group table does not followthe standards described in the NetView FTPInstallation, Operation, and Administration book thatapplies to your operating system and transferprogram.

record Number of the record that was processedby the queue handler.

System Action: The queue handler also checks theremainder of the server group table and then stops.

User Action: Correct the server group table andstart the queue handler again.

DVG414I REQUEST QUEUE WAS DEFINED WITH TOOMANY RECORDS

Explanation: The NetView FTP queue handlerrecognized that the number of records generated forthe request queue is too large. A maximum of100 000 is allowed.


User Action: Define a smaller request queue. Howto do this is described in the NetView FTPInstallation, Operation, and Administration book thatapplies to your operating system and transferprogram.

DVG415I ERROR DURING REQUEST QUEUEINITIALIZATION;RETRIEVAL OF A REQUEST FROM THEREQUEST QUEUE FAILED;ERROR CODE = error-code

Explanation: The queue handler was unable toretrieve one or more file-transfer requests from therequest queue.


01 End-of-file reached, record keyexceeds maximum on requestqueue data set.

04 Record not found on requestqueue data set.

65 Permanent I/O error on requestqueue data set.


User Action: Check the job log or the queuehandler log file for messages that might help youanalyze the problem. After you have corrected theproblem, restart the queue handler.

DVG416I ERROR DURING REQUEST QUEUEINITIALIZATION; DELETION OF AN EXPIREDREQUEST FAILED;ERROR CODE = error-code

Explanation: The queue handler failed whileattempting to delete an expired file-transfer requestfrom the request queue.


01 End of file reached, record keyexceeds maximum on requestqueue data set.




DVG417I � DVG423I



DVG417I ERROR DURING REQUEST QUEUEINITIALIZATION;UPDATE OF A REQUEST FAILED;ERROR CODE = error-code

Explanation: The queue handler failed to update afile-transfer request on the request queue. Theupdate is necessary because the status of thefile-transfer request is still active .







DVG418I ERROR DURING REQUEST QUEUE REBUILD;DELETION OF AN EXPIRED REQUEST FAILED;ERROR CODE = error-code

Explanation: Due to an overflow of the requestqueue, the queue handler started rebuilding therequest queue. One or more of the expiredfile-transfer requests failed to be deleted.







DVG419I REQUEST QUEUE INITIALIZED WITH AMAXIMUM NUMBER OF reqnum REQUESTS

Explanation: During initialization of the requestqueue the queue handler determined that the requestnumber is the highest request number available withthe current request queue (also the maximumnumber of requests that will fit in the queue).


User Action: None.

DVG420I REQUEST QUEUE WAS DEFINED WITH ANINCORRECT RECORD LENGTH;RECORD LENGTH = lrecl

Explanation: The queue handler retrieved therecord length of the request queue data set andfound it to be inappropriate for storing file-transferrequests.


User Action: Check the job used to define therequest queue and correct the record lengthspecified for the request queue. For moreinformation on the request queue definition, refer tothe NetView FTP Installation, Operation, andAdministration book that applies to your operatingsystem and transfer program.

DVG421I INVALID NETVIEW FTP OPERATORSUBCOMMAND;COMMAND INPUT = subcommand

Explanation: The operator entered an operatorcommand with an incorrect subcommand.

subcommand Subcommand that is passed to theNetView FTP.

System Action: Processing continues. Thecommand is rejected.

User Action: If appropriate, issue the operatorcommand with the correct subcommand. For moreinformation about valid subcommands, refer to theNetView FTP Installation, Operation, andAdministration book that applies to your operatingsystem and transfer program.

DVG423I SERVER serverid COULD NOT BE STOPPED

Explanation: The operator tried to stop the serverbut the server could not be stopped because of oneof the following:

� The specified server was not found in the servergroup table (MVS, VM)

� The specified server was not started (VSE)

� The specified server was not defined using theSRVSUF parameter (VSE).


DVG424I � DVG430I


� The job name or STC name underwhich the server was started (MVS)

� The user ID of the distribution servicecomponent virtual machine (VM)

� The server’s suffix (VSE).

System Action: Processing continues. Theoperator command is ignored.

User Action: Use the operator command to displaythe NetView FTP system status. Verify all activeNetView FTP components.

DVG424I NETVIEW FTP ACCEPTED COMMAND TOSTART SERVER serverid

Explanation: The operator issued a command tostart a server. The command was accepted.



� The server prefix plus the serversuffix (VSE)

� The user ID of the distribution servicecomponent virtual machine (VM).

System Action: The queue handler internally startsthe specified server by invoking a catalogedprocedure.

User Action: None.

DVG425I SERVER serverid COULD NOT BE STARTED

Explanation: The operator issued a command tostart a server. The command was performed but theinternal start facility returned an error.

One of the following occurred:

� The specified server was already started

� The specified server is still terminating

� The specified server was not defined using theSRVSUF parameter (VSE).






User Action: Use the operator command to displaythe NetView FTP system status. Check if anaddress space with the same name already exists.

DVG426I SERVER serverid COULD NOT BE STOPPEDBECAUSE IT WAS NOT STARTED

Explanation: The operator issued a command tostop a started server. The queue handler acceptedthe command but the server’s address space wasfound to be not active.





User Action: None.

DVG428I DELAY TIME = hhh HOURS

Explanation: This message is issued at queuehandler startup and indicates how long, in hours,finished requests remain on the queue before theycan be deleted during a queue rebuild.


User Action: None.

DVG429I NETVIEW FTP CANNOT START ANY SERVERS

Explanation: The operator issued a command tostart a server. The command was rejected for one ofthe following reasons:

� A STOP command was previously entered andthe queue handler is terminating. Operatorcommands are no longer accepted.

� The queue handler entered its shutdownsequence due to an irrecoverable error.Operator commands are no longer accepted.


User Action: Wait until the queue handlertermination sequence finishes, then, start the queuehandler again. When the queue handler is ready youcan start one or more servers via the operatorinterface.

DVG430I SYSTEM STATUS COULD NOT BE DISPLAYED

Explanation: The operator issued a command todisplay the NetView FTP system status, but this isnot possible. The command is rejected because apreviously entered DISPLAY command has notfinished processing.


User Action: Wait until the previously issuedDISPLAY command finishes.


DVG431I � DVG437I

DVG431I QUEUE HANDLER TRACE MASK COULD NOTBE CHANGED

Explanation: The operator issued a command tochange the currently active trace mask, but thequeue handler has not completed its initialization.

System Action: Processing continues. Commandis rejected.

User Action: Wait for message DVG402I, whichindicates that the initialization of the queue handler iscomplete.

DVG432I NETVIEW FTP ACCEPTED OPERATORSUBCOMMAND subcommand

Explanation: The operator issued a command,accompanied by the subcommand shown in thismessage. NetView FTP accepted it.

System Action: Processing continues. NetViewFTP attempts to carry out the subcommand.

User Action: None.

DVG433I NETVIEW FTP ACCEPTED OPERATORSUBCOMMAND TOSTOP system

Explanation: The operator issued a subcommandto stop system.

system One of the following:

� The queue handler (MVS, VM)� The NetView FTP partition (VSE).

NetView FTP accepted the command.

System Action: All started servers are terminatedand all file transfers that are in progress areinterrupted. The system stops. No furtherfile-transfer requests are accepted.

User Action: None.

DVG434I SERVER serverid CANNOT BE MODIFIED

Explanation: The operator entered a server ID orserver suffix as part of a command to modify aserver. The server was not modified because of oneof the following:

� The specified server has not started.� The specified server was not defined using the

SRVSUF parameter (VSE).





System Action: The command is not processed.

User Action: Use the DISPLAY command to viewthe names of started servers. Reenter the commandwith the name of a started server.

DVG435I ERROR IN NETVIEW FTP OPERATORSUBCOMMAND;VALUE FOR PARAMETER parmname ISINCORRECT

Explanation: The operator entered a command tomodify a request. NetView FTP rejected it for one ofthe following reasons:

� The value is not numeric, but must be

� The value is not in the valid range

� If the parameter is REQNUM, then the value isnot the number of a request on the input queue.

parmname Name of the incorrect parameter.

System Action: The command is not processed.

User Action: Reenter the command with a correctvalue.

DVG436I NETVIEW FTP OPERATOR SUBCOMMANDWAS CARRIED OUT SUCCESSFULLY

Explanation: The operator entered a command tomodify the class or priority of a request. Themodification was carried out successfully.


User Action: None.

DVG437I REQUEST QUEUE REBUILD COMPLETED AThh:mm:ss;n REQUESTS WERE DELETED

Explanation: The request queue rebuild finished. Ifthe queue handler deleted any file-transfer requests,then new file-transfer request(s) can be added to therequest queue.

hh:mm:ss Time that the rebuild completed:hh=hour, mm=minute, ss=second.

n Number of file-transfer requests that weredeleted.


User Action: If the number is zero, refer to theNetView FTP Installation, Operation, andAdministration book that applies to your operatingsystem and transfer program.


DVG438I � DVG446I

DVG438I REQUEST QUEUE REBUILD STARTED AThh:mm:ss

Explanation: The queue handler detected anoverflow of the request queue when it attempted towrite a file-transfer request to it. It reacted byrebuilding the request queue, trying to delete allfile-transfer requests whose status is finished andwhose delay time expired. During the rebuild noother queue handler commands that access therequest queue are allowed.

hh:mm:ss Time that the rebuild started: hh=hour,mm=minute, ss=second.

User Action: Wait for message DVG437I, whichindicates the end and the result of the rebuild.

DVG439I DELAY TIME SPECIFIED FOR QUEUE REBUILDWAS INCORRECT

Explanation: The operator entered a command torebuild the queue. Its value was rejected. The delaytime specified was incorrect. It was specified eitherwith more than 3 digits or with nonnumericcharacters.

System Action: The queue handler rejected thecommand. The queue rebuild is not performed.

User Action: Issue the command again, with acorrectly specified delay time.

DVG440I SYSTEM STATUS DISPLAY

Explanation: The operator issued a command todisplay the NetView FTP system status.

System Action: The queue handler collects statusinformation from all active servers. The queuehandler writes the NetView FTP system statusdisplay to the operator’s console. The display showsthe status of the queue handler and each server thatpresented its status so far. The time interval to allowall servers to present their status information is 30seconds.

User Action: None.

DVG441I COMPONENT compname COULD NOT BEPOSTED

Explanation: The queue handler issued a crossmemory post to notify another NetView FTPcomponent. The cross memory post failed, becausethe NetView FTP component stopped.

compnameSTC name or job name under which theNetView FTP component was started.

System Action: Processing continues. If themessage is issued when the queue handler is in theprocess of terminating, the termination process cantake longer than normal.

User Action: None.

DVG442I SERVER TO BE HELD OR RELEASED ISALREADY IN THE REQUESTED STATE

Explanation: The operator issued a command tohold or release a server but the server was alreadyin the requested state.


User Action: None.

DVG443I INCORRECT PRIORITY SPECIFIED

Explanation: The operator issued a command tochange the priority of a specified request, but thespecified priority was in error.

System Action: The queue handler rejected thecommand. NetView FTP processing continues.

User Action: Issue the command again with a validpriority. The priority must be an integer from 0 to 9.

DVG444I INCORRECT CLASS SPECIFIED

Explanation: The operator issued a command tochange the class of the specified request, but theclass parameter specified was not alphanumeric.

System Action: Processing continues. Therequest is unchanged.

User Action: Issue the command again with a validclass (0 to 9, A to Z).

DVG445I NO SERVERS ACTIVE

Explanation: The operator issued a command todisplay the status of all servers. Because no serveris started, no server data lines are displayed.


User Action: None.

DVG446I SERVER serverid CANNOT BE DISPLAYEDBECAUSE IT IS NOT STARTED

Explanation: The operator issued a command todisplay the status of the server serverid. A serverwith that name has not started.




System Action: Display terminates.

User Action: Make sure you specify the correctserver and reissue the command.


DVG447I � DVG450I

DVG447I SERVER serverid IS UNABLE TO COLLECTDATA

Explanation: The operator issued a command todisplay the status of the server serverid. The serveris active but did not answer the request within apredefined time limit.This can be because of an error situation in theserver or because the server is terminating.




System Action: Display terminates.

User Action: Repeat the command later.

DVG448I disp OF total SERVERS DISPLAYED

Explanation: The operator issued a command todisplay the status of all started servers.

disp Number of servers about which data couldbe displayed

total Number of servers that are currentlystarted.

If disp is less than total, there was not enoughcommon storage to pass information about allservers to the operator’s console.

System Action: Display terminates normally.

User Action: If disp is less than total, repeat thecommand later.

DVG449I disp OF total SESSIONS DISPLAYED

Explanation: The operator issued a command todisplay the status of a server.

disp Number of file transfers displayed.

total Number of file transfers currently inprogress.

If disp is less than total, there was not enoughcommon storage to pass information about all filetransfers to the operator’s console.

System Action: Display terminates normally.

User Action: If disp is less than total, repeat thecommand later.

DVG450I orig ISSUED QUEUE HANDLER COMMAND cmdFOR REQUEST NUMBER reqnum AT hh:mm:ssON yy/mm/dd;RC = retcd;RSN = rsncd

Explanation: This message logs each queuehandler command processed by the queue handler.

orig The user ID of the originator of the queuehandler command.

cmd Queue handler command performed:

01 OPEN, issued by a server.

02 CLOSE, issued by a server.

05 OBTAIN, issued by a server.

06 NOTIFY, issued by a server.

07 DELETE FINISHED requestsissued by interface routine.

08 GET SESSION VALUES, issuedby a server after operator modify.

0A NOTIFY actual record count.

10 ADD a file-transfer requestissued by interface routine.

20 DELETE a specific file-transferrequest issued by interfaceroutine.

30 DELETE all file-transfer requestsissued by interface routine.

32 Queue REBUILD.

33 Queue CLEANUP.

40 MODIFY class, priority, or status.

50 QUERY a specific file-transferrequest issued by interfaceroutine.

60 QUERY all file-transfer requestsissued by interface routine.

61 QUERY ADMINISTRATORfunction for queue statistics.

70 GETLUNAME, issued by server.

80 GETOPSYS, issued by interfaceroutine.

90 STATUS, issued by a server.

A0 START queue handler.

A1 INITIALIZE queue handler.

A6 TERMINATE queue handler.

B0 RESTART a file transfer issuedby a interface routine.

C1 CHANGE master password.

D0 FORCE DELETE of a specificfile-transfer request issued byinterface routine.


DVG451I � DVG454I

reqnum Request number (if applicable, else set tozero).

retcd Return code from queue handlercommand.

rsncd Reason code from queue handlercommand.

hh:mm:ss Time that the queue handler commandwas issued: hh=hour, mm=minute,ss=second.

yy/mm/dd Date that the queue handler commandwas issued: yy=year, mm=month,dd=day.

For more information about retcd and rsncd seeChapter 2, “NetView FTP ABEND, Return, andReason Codes” on page 109.


User Action: None.

DVG451I ERROR DURING QUEUE HANDLERINITIALIZATION PARAMETER HANDLING;ERROR CODE = error-code

Explanation: An error occurred when the queuehandler processed its initialization parameters.


01 No parameters found.

02 No value found for themandatory NFTPNAMEparameter.

03 The number of servers to bestarted exceeds the value of theMAXSRV parameter.

04 The specified number of TSOsessions exceeds the number ofavailable sessions.

08 If ALL is specified for theNVEVENT parameter, no othervalues can be assigned to thisparameter.

09 Duplicate events were specifiedfor the NVEVENT parameter.


User Action: Correct the error and start the queuehandler again.

DVG452I REQUEST QUEUE OVERFLOW OCCURREDWHILE ADDING A REQUEST TO THE REQUESTQUEUE

Explanation: The queue handler tried to add arequest to the queue. The queue handler detectedthat it cannot add the request to the queue becausethe queue is full.

System Action: The queue handler command isrejected. The request is not placed in the queue.The queue handler initiates a rebuild of the requestqueue.

User Action: Delete old request and resubmit therequest. For a description of how to avoid requestqueue overflows, refer to the NetView FTPInstallation, Operation, and Administration book thatapplies to your operating system and transferprogram.

DVG453I UNABLE TO DISPLAY ALL AVAILABLE DATA

Explanation: Only some of the data retrieved canbe displayed following a DISPLAY server command.

During queue handler startup, you specified themaximum additional CSA storage allowed. Thisvalue is passed to the server during the OPENphase. When the server presents its detailed statusfollowing a DISPLAY SERVER command, the basicplus the additional CSA storage was not enough tohold all the data that was retrieved. There is aninformation unit for each of the active sessions onthis server.

System Action: The server presents as much dataas it can.

User Action: To avoid this situation, do one of thefollowing:

� Increase the limiting factor that determines themaximum additional CSA obtained (CSAELIMQueue Handler Initialization parameter).

� Decrease the maximum number of simultaneoussessions for this server (MAXSESS serverinitialization parameter).

DVG454I UNABLE TO ALLOCATE SUFFICIENT CSASTORAGEFOR REQUEST NUMBER reqnum;ERROR CODE = error-code

Explanation: This message occurs duringprocessing of a file-transfer request. The problemthat caused this message to be issued may betemporary. However, if it occurs often, it indicates apossible permanent CSA space problem.

reqnum Number of the file-transfer requestcurrently being processed by a queuehandler command. On a failing ADDqueue handler command or STATUSdisplay, reqnum is zero.


DVG455I � DVG459I


01 Error occurred on an ADD queuehandler command.

10 Error occurred on an OBTAINqueue handler command.

11 Error occurred on a STATUSdisplay.

12 Error occurred on a NOTIFYRESTARTABLE queue handlercommand.

13 Error occurred on a NOTIFYFINISHED queue handlercommand.

System Action: If the problem occurs on:

� An ADD queue handler command, the failingfile-transfer request is rejected.

� A STATUS DISPLAY, the displayed informationis truncated.

� An OBTAIN queue handler command, the failingfile-transfer request is requeued with the statusDEFERRED.

� Any NOTIFY queue handler command, thefile-transfer request is processed.

User Action: If the message occurs often, it ispossible that the limiting factor to determine themaximum additional CSA size for one request is toohigh (CSAELIM queue handler initializationparameter or maximum request-queue recordlength). If this is the case, decrease this value.

DVG455I ENTRY FOR SERVER servername ALREADY INSERVER TABLE

Explanation: A server with the name servernamestarted and asked the queue handler to make anentry in the queue handler’s server table, but there isalready an entry for a server with that name. Thiscan happen if a server terminated abnormally andwas not able to inform the queue handler.

servername Procedure name of server.

System Action: The server terminates and thequeue handler clears the server table entry for thatserver.

User Action: Restart the server. Because thequeue handler cleared the entry in the server table,the server startup should proceed normally. If theproblem occurs again or if it occurs for the sameserver, contact your IBM Support Center.

DVG456I SERVER servername CANNOT BE STARTED;MAXIMUM NUMBER OF SERVERS REACHED

Explanation: You tried to start the serverservername but the maximum number of servers arealready active.

System Action: The server stops. Processingcontinues.

User Action: Stop a started server and restart thefailed server, or restart the queue handler with alarger maximum number of servers.

DVG457I DISPLAY OF QUEUE HANDLER AND SERVERINFORMATION

Explanation: The operator issued a command todisplay the information about the queue handler andall active servers.

System Action: The queue handler asks all startedservers for information. After a short time interval,the queue handler status display is written to theoperator’s console, showing the status of the queuehandler and each server that presented its status sofar. The time interval to allow all servers to presenttheir status information is 30 seconds.

User Action: None. For more information on thequeue handler and server, refer to NetView FTP V2MVS Installation, Operation, and Administration.

DVG458I DISPLAY OF QUEUE HANDLER INFORMATION

Explanation: The operator issued a command todisplay the status of the queue handler. Detailedqueue statistics are shown. For more informationrefer to the operating section of the NetView FTP V1MVS or NetView FTP V2 MVS Installation,Operation, and Administration manual.

System Action: The data collected by the queuehandler is displayed on the operator’s console.

User Action: None.

DVG459I DISPLAY OF SERVER serverid

Explanation: The operator issued a command todisplay the status of server serverid.


� The job name or STC name underwhich the SNA or OSI server wasstarted (MVS)


System Action: The queue handler collects statusinformation for the specified server, and writes it tothe operator’s console.

User Action: None. For more information on theserver, refer to NetView FTP V2 MVS Installation,Operation, and Administration.


DVG460I � DVG464I

DVG460I ERROR DURING SPACE ALLOCATION;ERROR CODE = error-codeOr, for NetView FTP V2.2 MVS:

DVG460I ERROR DURING SPACE ALLOCATION

Explanation: An error occurred when NetView FTPtried to allocate space. The error is permanent andis due to the defined maximum record size of therequest queue or limited CSA space (MVS only)available to NetView FTP. The defined limitationswere set by the system administrator.

NetView FTP other than NetView FTP V2.2 MVS:

error-codeInsufficient space is available to store:

01 User-written file handlerparameters.

02 VSAM cluster definitionparameters.

03 Member selection or exclusionlist.

04 Receiving SFS directory accessparameters.

05 Sending SFS directory accessparameters.

06 Receiving SFS parameters orsending SFS and VSAM ClusterDefinition parameters.

07 SMS (Storage ManagementSubsystem) parameters.

08 APPC Security parameters.

09 OS/400 parameters.

10 Extended user-exit informationparameters.

11 Post-transfer JOB parameters.

12 Post-transfer programparameters.

13 Data Encryption parameters.

14 OSI parameters.

For NetView FTP V2.2 MVS, insufficient space isavailable to store one of the following:

� User-written file handler parameters� VSAM cluster definition parameters� Member selection or exclusion list� Sending SFS parameters� Receiving SFS parameters

� SMS parameters� APPC conversation security parameters� Sending OS/400 parameters� Receiving OS/400 parameters� Sending OS/2* parameters� Receiving OS/2 parameters� Sending file ID parameter� Receiving file ID parameter� User-exit information parameters.


� An interface routine, NetView FTP rejects thecommand


User Action: Try again later. If the problempersists contact your system administrator. For errorcode 3, either submit several requests each withfewer members, or try again later.

DVG461I INCORRECT REQUEST NUMBER SPECIFIED

Explanation: The operator issued a command tomodify a request. The specified request number wasincorrect; there is no request with such a number.Either:

� The specified request number is out of range

� The specified request number is unused.


User Action: Display the queue handler to see themaximum required number allowed. Reissue thecommand with the correct number. If necessary usethe user interfaces to query and change requests.

DVG462I REQUEST CANNOT BE CHANGED BECAUSE ITIS NOT WAITING

Explanation: The operator issued a command tochange the status, class or priority of a request. Therequest is not waiting, so the command is rejected.

System Action: Processing continues. Theparameter values are unchanged.

User Action: None.

DVG463I INVALID NEW SERVER SESSIONPARAMETERS SPECIFIED

Explanation: The operator issued a command tochange the session parameters of a server, whichwas rejected. Either the number of local sessions(AVLLRH), the number of remote sessions(AVLRRH), or the total number of sessions(AVLSESS) is larger than the maximum number ofavailable sessions.

System Action: Processing continues. The serveris unchanged.

User Action: Reissue the command with correctvalues.

DVG464I ERROR DURING REQUEST QUEUE HANDLING;UPDATE OF A REQUEST FAILED;ERROR CODE = error-code

Explanation: The queue handler failed to update afile-transfer request on the request queue. Theupdate is necessary because the class or priorityshould be changed.


DVG471I � DVG500I



04 Record not found in requestqueue data set.

65 Permanent I/O error in requestqueue data set.

System Action: The queue handler stops. Therequest is not changed.

User Action: Check the job log or the queuehandler log file for messages that help you analyzethe problem. After you have corrected the problem,restart the queue handler.

DVG471I SERVER SESSION VALUES ACCEPTED FORservername

Explanation: The operator-issued command tochange the session parameters for the serverservername was accepted.

System Action: Processing continues. Thespecified server runs with the new parameters.

User Action: None.

DVG481I SMF WRITING FAILED AT time;SMF RETURN CODE = smfretcd

Explanation: The writing of an SMF record failed.For further information refer to MVS/ESA SystemManagement Facilities (SMF) or MVS/XA SMF.

hh:mm:ss Time that SMF writing failed at: hh=hour,mm=minute, ss=second.

smfretcd SMF return code. Indicates that therecord was not written because:

16 SMF is not active.

20 The user-written IEFU83 orIEFU84 exit routine suppressedthe record.

24 The data was lost.

36 The record type specified is notcurrently being recorded.

40 A buffer shortage caused thedata to be lost.

44 SVC 83 could not establishrecovery.

System Action: Processing continues. The SMFrecord is not written.

User Action: None.

DVG500I QUEUE HANDLER COMMAND cmd ISSUED BYSERVER FAILED;RETURN CODE = retcd;REASON CODE = rsncd

Explanation: An error occurred when a serverissued a queue handler command.

cmd The command was one of the following:

01 OPEN, issued by a server tocome under the control of thequeue handler.

02 CLOSE, issued by a server toleave the control of the queuehandler.

05 OBTAIN, issued by a server toget a new file-transfer request forprocessing.

06 NOTIFY, issued by a server tochange the status of afile-transfer request on therequest queue.

08 GETSESSPRM, issued by aserver to get the new sessionvalues.

70 GETLUNAME, issued by aserver to get more LU names fora specified server group name.

90 STATUS, issued by a server, toreport its status, in response to aDISPLAY command.

retcd Queue handler command return code.

rsncd Queue handler command reason code.

Refer to Chapter 2, “NetView FTP ABEND, Return,and Reason Codes” on page 109 for moreinformation about retcd and rsncd.

System Action: The server interrupts all active filetransfers and terminates immediately.

User Action: Use the return and reason code toanalyze and fix the problem. If the problem persists,contact your IBM Support Center.

If the error occurred during the NOTIFY command,NetView FTP cannot update the status of formerlyactive requests. To correct this, do the following:

1. Stop the queue handler (MVS, VM) or theNetView FTP partition (VSE). NetView FTPchanges the status of all active requests towaiting .

2. Restart the queue handler (MVS, VM) or theNetView FTP partition (VSE). All waitingrequests are available for scheduling by servers.

If the error occurred during the NOTIFY commandand before the receiving server created the receivingdata set, it can happen that the file transfer cannotbe automatically restarted. This is because, whenautomatically restarting a transfer, NetView FTPallocates the receiving data set with the dispositionMOD, and this allocation can be successful only ifthe data set already exists. In this situation, youneed to submit a new request to transfer the file.


DVG510I � DVG530I

DVG510I NO LU NAME FOUND IN SERVER GROUPTABLE FOR servergroup

Explanation: No LU name is found in the servergroup table for the server group specified in thefile-transfer request. This situation happens if thequeue handler was stopped (after the file-transferrequest was added to the request queue) and thenstarted again with a different, a changed, or noserver group table.


User Action: Restart the queue handler with adifferent or a changed server group table thatcontains the entry for the server group specified inthe request, or change the server group name in thefile-transfer request and resubmit it.

DVG511I PCF IS NOT ACTIVE AT BOTH LOCATIONS

Explanation: You specified that data is to beencrypted during file transfer. NetView FTP V2 MVSallows encryption only if the ProgrammedCryptographic Facility (PCF) is active at the sendinglocation and at the receiving location.


User Action: If you want to encrypt data during filetransfer, make sure PCF is active at both locations.

DVG512I PCF RETURNED AN ERROR BY COMMANDcmd;RETURN CODE = retcd

Explanation: An error occurred with theProgrammed Cryptographic Facility (PCF) duringserver initialization or during file transfer.

cmd One of the following:

GEN_OPKY Generate an operationalkey.

ENCR_ICV Encipher ICV.

DECR_ICV Decipher ICV.

ENCR_DAT Encipher data.

DECR_DAT Decipher data.

retcd Return code issued by PCF.


User Action: None.

DVG513I ENCRYPTION LABEL NOT CORRECT

Explanation: The Programmed CryptographicFacility (PCF) does not recognize the encryptionlabel specified.


User Action: Correct the encryption label andresubmit the file-transfer request. Make sure theencryption label is stored in the PCF key data set(CKDS).

DVG514I DATA ENCRYPTION = encrypt

Explanation: This message tells you whether or notthe Data Encryption parameter was specified.

encrypt One of the following:

YES Data encryption was specified.

NO Data encryption was not specified.


User Action: None.

DVG515I ENCRYPTION LABEL CONTENTSINCONSISTENT

Explanation: The cross key at the sending locationis different from the cross key at the receivinglocation that has the same label. Because of this,the enciphered data cannot be deciphered. Formore details, see OS/VS1 OS/VS2 MVSProgrammed Cryptographic Facility: InstallationReference.


User Action: Check the encryption label at bothlocations.

DVG530I PARAMETER WITH KEYWORD keyword IS NOTPERMITTED FOR AN EXISTING DATA SET

Explanation: You specified at least one parameterincorrectly for a file that already exists. Either, theparameter whose keyword is shown in the message,or the data set status specified in the request, is inerror.



� An interface routine, NetView FTP rejects therequest




DVG531I � DVG541I

DVG531I DO NOT SPECIFY THE PARAMETER WITHKEYWORD keyword IF NOMAX IS SPECIFIEDFOR INITIAL NUMBER OF RECORDS

Explanation: You specified NOMAX for the initialnumber of records for an OS/400 file, and also avalue for the parameter whose keyword is shown inthe message. However, these values areincompatible.





User Action: Either, do not specify NOMAX for theinitial number of records, or remove the value for theparameter shown in the message, and then resubmityour request.

DVG536I NOT ENOUGH STORAGE AVAILABLETO PROCESS ADDITIONAL PARAMETERS;ERROR CODE = error-code

Explanation: The maximum additional CSA storageallowed for a request is too small to contain all yourparameters. This is a restriction of the currentdefinition of your NetView FTP environment.


01 User-written file handlerparameters.

02 VSAM cluster definitionparameters.

03 PDS member list.

04 OSI file-transfer request.


User Action: If the error code is 1 or 2, the queuehandler presently cannot accept or pass to servers,requests using these kinds of parameters.

If the error code is 3, resubmit your request withfewer selected or excluded PDS members.

DVG537I RESULTS OF ADMINISTRATOR QUERY OFWAITING REQUESTS:

Explanation: This message is used as the headerline for messages issued in response to anadministrator query for waiting requests.


User Action: None.

DVG538I RESULTS OF ADMINISTRATOR QUERY OFACTIVE REQUESTS:

Explanation: This message is used as the headerline for messages issued in response to anadministrator query for active requests.


User Action: None.

DVG539I RESULTS OF ADMINISTRATOR QUERY OFFINISHED REQUESTS:

Explanation: This message is used as the headerline for messages issued in response to anadministrator query for finished requests.


User Action: None.

DVG540I REQUEST QUEUE STATISTICS:QUEUE HANDLER = qhname;START DATE = date;START TIME = time;QUEUE SIZE = qsize

Explanation: This message is issued in responseto an administrator query for information about therequest queue. The displayed information consistsof:

qhname One of the following:

� The STC name under which thequeue handler was started (MVS)

� User ID of the queue handler’s virtualmachine (VM).

date Date that the queue handler was started.

time Time that the queue handler was started.

qsize Size of the request queue. This value isthe sum of the number of waiting, active,and finished requests, and the unusedrequest slots.


User Action: None.

DVG541I WAITING = waiting;ACTIVE = active;FINISHED = finished;RESTARTED = restarted;UNUSED = unused

Explanation: This message is issued in responseto the query administrator-command for informationabout requests in the queue. The displayedinformation consists of:

waiting Total number of waiting requests in thequeue.

active Total number of active requests in thequeue.


DVG542I � DVG544I

finished Total number of finished requests in thequeue.

restarted Total number of waiting requests in thequeue that were previously active and arenow to be restarted.

unused Number of free request slots.


User Action: None.

DVG542I CLASS = class;HELD = state;WAITING = waiting;ACTIVE = active;SERVED = served

Explanation: This message contains statisticalinformation for one request class. It is issued inresponse to the query administrator-command forinformation about requests, only for server classesthat are held by the operator, or if it contains waitingor active requests. The displayed informationconsists of:

class Letter or number of the server class.

state Whether or not the server class was puton hold by the operator. Can be one ofthe following:

Y Class is held.

N Class is not held.

waiting Number of waiting requests in the queuewith that class.

active Number of active requests in the queuewith that class.

served Whether or not a server is started for theclass. Can be one of the following:

Y A server is started.

N No server is started.

U Unknown.


User Action: None.

DVG543I REQUEST NUMBER = reqnum;CLASS = class;STATUS = status;PRIORITY = priority;RESTART = restart;SUBMITTED = yy/mm/dd,hh:mm:ss;SERVER NAME = svname;LOCAL LU NAME = loclu;REMOTE LU NAME = remlu;ORIGINATOR = orig

Explanation: This message contains information forone waiting request. It is issued as a result of thequery administrator-command for waiting requests.

reqnum Request number of the file-transferrequest.

class Server class.

status Status of the request. Can be any of thefollowing:

W WaitingH Waiting and heldB Waiting and blockedD Waiting and deferred.

priority Request priority.

restart Indicates whether or not the specifiedrequest is waiting to be restarted. Can beblank (indicating that the request is notwaiting to be restarted) or one of thefollowing:

A Request is waiting for anautomatic transfer restart.

M Request is waiting for a manualtransfer restart.

yy/mm/dd,hh:mm:ssDate and time that the request wasentered by the user and added to thequeue.

svname Name of the server processing therequest. (Not applicable to VSE.)

loclu Local LU name.

remlu Remote LU name or server group name.

orig User ID of the originator of the file-transferrequest.


User Action: None.

DVG544I REQUEST NUMBER = reqnum;CLASS = class;SUBMITTED = yy/mm/dd,hh:mm:ss;STARTED = yy/mm/dd,hh:mm:ss;SERVER NAME = svname;LOCAL LU NAME = loclu;REMOTE LU NAME = remlu;ORIGINATOR = orig

Explanation: This message contains information forone active request. It is issued in response to anadministrator query for active requests.


class Server class.

yy/mm/dd,hh:mm:ssDate and time that either the request wasentered by the user and stored on thequeue, or the file transfer for this requeststarted.

svname Name of the server processing therequest. (Not supported by VSE.)

loclu Local LU name.

remlu Remote LU name.



User Action: None.


DVG545I � DVG550I

DVG545I REQUEST NUMBER = reqnum;CLASS = class;SUBMITTED = yy/mm/dd,hh:mm:ss;STARTED = yy/mm/dd,hh:mm:ss;FINISHED = yy/mm/dd,hh:mm:ss;RETURN CODE = retcd;REASON CODE = rsncd;RECORDS = records;ORIGINATOR = orig

Explanation: This message contains information forone finished request. It is issued in response to anadministrator query for finished requests.


class Server class.

yy/mm/dd,hh:mm:ssDate and time that either the request wasentered by the user and stored on thequeue, or the file transfer for this requeststarted, or the file transfer for this requestwas finished.

retcd Return code from the file transfer.

rsncd Reason code from the file transfer.

records Number of transferred records.



User Action: None.

DVG546I NAME OF SENDING DATA SET = dsname

Explanation: This message contains the name ofthe sending data set specified in a request. Thisinformation was requested additionally for anadministrator query for waiting, active, or finishedrequests.


User Action: None.

DVG547I ERROR OCCURRED DURING function FORDATA SET dsname;ERROR CODE = error-code

Explanation: An error occurred during an OBTAINor LOCATE macroinstruction.

function OBTAIN or LOCATE.

dsname Sending data set from which data-setinformation should be retrieved.

error-codeMessage code from OBTAIN or LOCATE.


User Action: For further information, see one ormore of the following:

� MVS/DFP V3.3: Managing Catalogs� MVS/XA Catalog Administration Guide.

DVG548I function FAILED FOR DATA SET dsname;ERROR CODE = error-code

Explanation: An error occurred for the specifieddata set during OBTAIN or LOCATE.

function OBTAIN or LOCATE.

dsname Sending data set from which data-setinformation should be retrieved.


01 Data-set not cataloged.

02 Required volume not mounted.

03 Data set not found on volume.

04 Permanent I/O error.

05 Data-set type retrieved is notsupported by NetView FTP.

06 Data set is migrated to HSM.


User Action: The response depends on the errorcode:

01 If the data-set name specified is correct,specify a volume serial number.

02 Mount the volume.

03 Specify the correct data-set name or volumeserial number.

04 Contact your system administrator.



DVG550I NETVIEW FTP release;BATCH JOB INTERFACE STARTED ONyy/mm/dd AT hh:mm:ss; MAINTENANCE LEVEL= mlevel

Explanation: The batch job interface routinestarted.


yy/mm/dd Date that the batch job interface routinestarted: yy=year, mm=month, dd=day.

hh:mm:ss Time that the batch job interface routinestarted: hh=hour, mm=minute, ss=second.

mlevel Program maintenance-level information.


User Action: None.


DVG551I � DVG554I

DVG551I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;ADDED = yy/mm/dd,hh:mm:;ORIG = orig;REC = trrec;REQNAME = reqname

Explanation: This message is issued in responseto a user query command.

reqnum The request number of the file-transferrequest.

status The status of the request:

W Waiting

H Waiting and held

B Waiting and blocked

D Waiting and deferred

priority The priority of the request.

retcd The return code of the last attempt toprocess the file-transfer request.

rsncd The reason code of the last attempt toprocess the file-transfer request.

class The server class.

yy/mm/dd Date that the request was submitted:yy=year, mm=month, dd=day.

hh:mm: Time that the request was submitted:hh=hour, mm=minute.

orig The originator of the file-transfer request.

trrec The number of records that weretransferred on the last attempt to processthe file-transfer request.

reqname The name of the request.


User Action: None.

DVG552I QUEUE HANDLER COMMAND commandnameCARRIED OUT FOR USER orig;RETURN CODE = retcd;REASON CODE = rsncd;TIME = hh:mm:ss;REQUEST NUMBER = reqnum

Explanation: This message indicates thecompletion of a queue handler command that wasinitiated by the batch job interface routine.

commandnameQueue handler command as specified inthe FUNCTION parameter of the batchjob interface:

� ADD � DELETE � DELALL � DELFIN

� QUERY � QRYALL � MODIFY.


retcd The return code from the queue handlercommand. Refer to Chapter 2, “NetViewFTP ABEND, Return, and Reason Codes”on page 109 for more information.

rsncd The reason code from the queue handlercommand. Refer to Chapter 2, “NetViewFTP ABEND, Return, and Reason Codes”on page 109 for more information.

hh:mm:ss Time: hh=hour, mm=minute, ss=second.

reqnum The request number of the file-transferrequest, if applicable; otherwise set tozero.


User Action: None.

DVG553I PARAMETER WITH KEYWORD keyword IS NOLONGER SUPPORTED

Explanation: Some FTP V2.2 parameters areignored by NetView FTP. They represent obsoleteor replaced FTP V2.2 functions.

keyword The batch job interface keyword. It canbe one of the following: xLU, TIME,xCMSUSER, xCMSFID, RDSN, orRUSIZE.

System Action: The parameter is ignored.Processing continues.

User Action: Do not use these parameters insubsequent file-transfer requests.

DVG554I NETVIEW FTP release; BATCH JOB INTERFACEENDED ON yy/mm/dd AT hh:mm:ss;RETURN CODE = retcd;REASON CODE = rsncd

Explanation: This is the completion message of thebatch job interface routine.


yy/mm/dd Date that the batch job interface routineterminated: yy=year, mm=month, dd=day.

hh:mm:ss Time that the batch job interface routineterminated: hh=hour, mm=minute,ss=second.

retcd Return code for queue handler commandor file transfer.

rsncd Reason code for queue handler commandor file transfer.


DVG555I � DVG557I

Whether the return and reason codes are for aqueue handler command or for the file transferdepends on the value of the WAIT parameter and onthe outcome of the file transfer:

� If WAIT=YES; the batch job interface routineadds the file-transfer request to the requestqueue and then periodically issues a QUERYqueue handler command to check the status ofthe file-transfer request. If a queue handler erroroccurred before the file transfer ended, thecodes are the return and reason code of theQUERY queue handler command. Otherwisethe codes are the return and reason code of thefile transfer.

� If WAIT=NO; the codes are the return andreason code of the ADD queue handlercommand.

System Action: The batch job interface routineterminated.

User Action: None.

DVG555I PARAMETER WITH KEYWORD keyword IS NOTVALID FOR THE OPERATING SYSTEM opsys

Explanation: The specified parameter is not validfor the noted operating system.

keyword Batch job interface keyword.





DVG556I PARAMETER ERROR;SPECIFIED PARAMETERS OR THEIR VALUESARE INCOMPATIBLE; THEY REQUIREDIFFERENT OPERATING SYSTEMS

Explanation: You specified parameters or valuesthat are only valid for certain operating systems.You also specified other parameters or values thatare valid only for other operating systems.

The following file parameter specifications are notvalid for a location:

Operating Parameter GroupSystem

MVS SFS parametersOS/400 file parametersVM link parametersOS/2 file parameters

VM SMS parametersOS/400 file parametersOSI file-transfer parametersPost-transfer job and post-transferprogram parametersEncryption parametersPDS processing parametersOS/2 file parameters

VSE SMS parametersSFS parametersOS/400 file parametersOSI file-transfer parametersPost-transfer jobs and post-transferprogram parametersVM link parametersEncryption parametersPDS processing parametersOS/2 file parameters

OS/400 Anything other than OS/400 fileparameters

OS/2 SMS parametersSFS parametersOS/400 file parametersOSI file-transfer parametersPost-transfer jobs and post-transferprogram parametersVM link parametersEncryption parametersPDS processing parametersUser-written file handler parameters





DVG557I VALUE SPECIFIED FOR THE PARAMETERWITH KEYWORD keyword IS INVALID FOR THEOPERATING SYSTEM opsys

Explanation: The value is incorrect for the notedoperating system.


opsys The operating system. It can be one ofthe following:

� MVS � VM � VSE � OS/400 � OS/2






DVG558I � DVG560I

DVG558I QUEUE HANDLER COMMAND commandnameCARRIED OUT FOR USER orig;RETURN CODE = retcd;REASON CODE = rsncd;TIME = hh:mm:ss

Explanation: This message indicates thecompletion of a queue handler command that wasinitiated by the batch job interface routine.

commandnameQueue handler command as specified inthe FUNCTION parameter of the batchjob interface:

� QRYALL � DELALL � DELFIN � QRYADM � FORCE � RESTART � MODIFY � CHANGEPW � REBUILD.


retcd The return code of the queue handlercommand.

rsncd The reason code of the queue handlercommand.

hh:mm:ss Time: hh=hour, mm=minute, ss=second.


User Action: None.

DVG559I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;START = yy/mm/dd,hh:mm;ORIG = orig;REC = trrec;REQNAME = reqname

Explanation: This message is issued in responseto a user query.



A Active (file transfer in progress).





yy/mm/dd Date that the file transfer started:yy=year, mm=month, dd=day.

hh:mm Time that the request was started:hh=hour, mm=minute.


trrec The number of records that weretransferred at the last attempt to processthe file-transfer request.



User Action: None.

DVG560I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;FINIS = yy/mm/dd,hh:mm;ORIG = orig;REC = records;REQNAME = reqname

Explanation: This message is issued in responseto a user query.



F Finished.






hh:mm Time that the file transfer ended:hh=hour, mm=minute.


records The number of records that weretransferred on the last attempt to processthe file-transfer request.



User Action: None.


DVG561I � DVG580I

DVG561I MEMBER OR GDG NOTATION NOT VALID FORTHE OPERATING SYSTEM opsys;PARAMETER TYPE = type

Explanation: A PDS member name or a GDGnumber is defined as part of the data-set name orwith the keyword xPDSMEM. They are not valid forthe noted operating system.

opsys Operating system which does not supportPDS or GDG processing.






� A server, the file transfer ends and NetView FTPchanges the status of the request to finished.


DVG562I MEMBER OR GDG NOTATION NOT VALID FORTHE DATA SET TYPE ftype;PARAMETER TYPE = typeOr, for NetView FTP V2.2 MVS:

DVG562I MEMBER OR GDG NOTATION NOT VALID FORTHE FILE ORGANIZATION ftype, LABEL TYPElab-type;PARAMETER TYPE = type

Explanation: A PDS member name or GDGnumber is defined as part of the data set or with thekeyword xPDSMEM. They are not valid for thenoted file type or organization.

ftype The specified data-set type does notsupport PDS or GDG processing.






� A server, the file transfer ends and NetView FTPchanges the status of the request to finished.


DVG563I PARAMETER WITH KEYWORD keyword NOTSPECIFIED;NETVIEW FTP ASSUMES value

Explanation: The user has not specified a value forthe parameter indicated by the batch job interfacekeyword. NetView FTP uses the value shown.

The assumption is derived by checking other requestspecifications.

System Action: This message is for informationonly.

User Action: None.

DVG580I REQUEST NUMBER = reqnum;CLASS = class;STATUS = status;PRIORITY = priority;RESTART = restart;SUBMITTED = yy/mm/dd,hh:mm:ss;OSI SERVER NAME = svname;APPLICATION ENTITY TITLE = aet;ORIGINATOR = orig

Explanation: This message contains information forone waiting OSI request. It is issued as a result ofthe query administrator command for waitingrequests.


class Server class.

status Status of the request. Can be one of thefollowing:

W WaitingH Waiting and held.

priority Request priority.

restart Indicates whether or not the specifiedrequest is waiting to be restarted. Can beblank (indicating that the request is notwaiting to be restarted) or:

A Request is waiting for anautomatic transfer restart.

yy/mm/dd,hh:mm:ssDate and time that the request wasentered by the user and added to thequeue.

svname The job name or STC name under whichthe OSI server was started.

aet Application entity title.



User Action: None.


DVG581I � DVG584I

DVG581I REQUEST NUMBER = reqnum;CLASS = class;SUBMITTED = yy/mm/dd,hh:mm:ss;STARTED = yy/mm/dd,hh:mm:ss;OSI SERVER NAME = svname;APPLICATION ENTITY TITLE = aet;ORIGINATOR = orig

Explanation: This message contains information forone active OSI request. It is issued in response toan administrator query for active requests.


class Server class.

yy/mm/dd,hh:mm:ssDate and time that either the request wasentered by the user and stored on thequeue, or the file transfer for this requestwas started.

svname The job name or STC name under whichthe OSI server was started.

aet Application entity title.



User Action: None.

DVG582I REQUEST NUMBER = reqnum;CLASS = class;SUBMITTED = yy/mm/dd,hh:mm:ss;STARTED = yy/mm/dd,hh:mm:ss;FINISHED = yy/mm/dd,hh:mm:ss;RETURN CODE = retcdd;REASON CODE = rsncd;ORIGINATOR = orig

Explanation: This message contains information forone finished OSI request. It is issued in response toan administrator query for finished requests.


class Server class.

yy/mm/dd,hh:mm:ssDate and time that either the request wasentered by the user and stored on thequeue, or the file transfer for this requestwas started, or the file transfer for thisrequest was completed.

retcd Return code from the file transfer.

rsncd Reason code from the file transfer.



User Action: None.

DVG583I FILE NAME = local/osiname

Explanation: This message contains the name ofthe sending file specified in an OSI request. It iseither the local file name for transfer mode TO, orthe OSI file name for transfer mode FROM. Thisinformation was requested additionally for anadministrator query for waiting, active, or finishedrequests.


User Action: None.

DVG584I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;ADDED = yy/mm/dd,hh:mm;ORIG = orig;REQNAME = reqname

Explanation: This message is issued in responseto a user query command for an OSI request.



W WaitingH Waiting and held.





yy/mm/dd Date that the request was submitted:yy=year, mm=month, dd=day.

hh:mm Time that the request was submitted:hh=hour, mm=minute.


reqname The name of the OSI request.


User Action: None.


DVG585I � DVG588I

DVG585I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;START = yy/mm/dd,hh:mm;ORIG = orig;REQNAME = reqname

Explanation: This message is issued in responseto a user query for an OSI request.



A Active (file transfer in progress).





yy/mm/dd Date that the file transfer started:yy=year, mm=month, dd=day.

hh:mm Time that the request was started:hh=hour, mm=minute.




User Action: None.

DVG586I REQNUM = reqnum;ST = status;PRTY = priority;RC = retcd;RSN = rsncd;CL = class;FINIS = yy/mm/dd,hh:mm;ORIG = orig;REQNAME = reqname

Explanation: This message is issued in responseto a user query for an OSI request.



F Finished.






hh:mm Time that the file transfer ended:hh=hour, mm=minute.




User Action: None.

DVG587I OSI INPUT PARAMETER parmname INCORRECTOR MISSING

Explanation: An OSI file-transfer parameter ismissing or incorrectly specified. parmname can beone of the following:

� Application Entity Title� Permitted Actions Passwords

� Initiator Function � Destination Effect � Document Type � File Availability � Filestore Owner � Future Filesize� Local File Name� Local OSI File Name� Local Filestore Subset� Maximum String Length

� Transfer Mode� Remote OSI File Name� Local Filestore Nickname

� String Significance � Universal Class.� No OSI Parameters.

This message is displayed when the interfacevalidation routine found that the indicated parameterwas either missing or not specified according to therestrictions as specified in the OSI transfer parameterdescription. If there is more than one parameter inerror, only the last parameter found in error results ina message.

Note: Some restrictions can be checked only withinthe OSI environment, that is in OSI/File Services.

System Action: The request is not submitted.Processing continues.


DVG588I OSI TRANSFER REQUEST NUMBER reqnumREJECTED

Explanation: This message is issued when an OSIfile-transfer request cannot be processed. Probablya parameter value is incorrectly specified. Thismessage follows message DVG587I.




DVG589I � DVG602A

DVG589I AT LEAST ONE PARAMETER WASREQUESTED WHICH IS VALID FOR ANSNA-TYPE REQUEST BUT INCOMPATIBLEWITH AN OSI REQUEST

Explanation: This message is issued if a service isrequired that is not offered for an OSI file-transferrequest. For example, it applies to the followingparameters:

� Remote LU name or remote server group� Server running mode (= single)� Restart from checkpoint� Automatic transfer restart

� Data Compression � Data encryption� Remote check of the request

� OS/400 connection� Post-transfer program (local and remote)� Remote post-transfer job.

Note: All non-OSI file parameters are rejected.



DVG600A ENTER NETVIEW FTP COMMAND OR END

Explanation: The operator started communicationwith VSE by entering the VSE command MSG p,where p is the identifier of the NetView FTP partition.NetView FTP VSE responds by displaying thismessage.

System Action: NetView FTP processingcontinues, the NetView FTP partition that issued thismessage cannot display any further consolemessages until the operator replies to this message.

User Action: The operator must enter either END,to terminate the communication with NetView FTPVSE, or a NetView FTP VSE command.

DVG601A MOUNT TAPE volser WITH RING ON UNIT unit;REPLY WITH M(OUNTED), R(EQUEUE), ORC(ANCEL)

Explanation: NetView FTP wants the operator tomount a tape.

volser Volume serial number of the tape to bemounted. If, for an unlabeled tape, avalue for the volume serial number is notspecified, the default value SCRTCH isused.

unit Tape unit that the tape is to be mountedon.

System Action: The server that needs the tapewaits until the operator replies to the message. TheNetView FTP partition that issued the messagecontinues processing, but cannot display any furtherconsole messages until the operator replies to themessage.

User Action: The operator must enter either aNetView FTP VSE command or at least the firstletter of one of the following:

MOUNTEDTo indicate that the tape was mounted, asrequested. The file-transfer request isprocessed.

REQUEUETo tell NetView FTP VSE to put thefile-transfer request back in the requestqueue and change its status to waiting .

CANCEL To tell NetView FTP VSE to cancel thefile-transfer request. The file-transferrequest status is set to finished .

DVG602A MOUNT TAPE volser WITHOUT RING ON UNITunit;REPLY WITH M(OUNTED), R(EQUEUE), ORC(ANCEL)


volser Volume serial number of the tape to bemounted. If, for an unlabeled tape, avalue for the volume serial number is notspecified, the default value SCRTCH isused.


System Action: The server that needs the tapewaits until the operator replies to the message. TheNetView FTP partition that issued the messagecontinues processing, but cannot display any furtherconsole messages until the operator replies to themessage.

User Action: The operator must enter either aNetView FTP VSE command or at least the firstletter of one of the following:

MOUNTEDTo indicate that the tape was mounted, asrequested. The file-transfer request isprocessed.

REQUEUETo ask NetView FTP VSE to put thefile-transfer request back in the requestqueue and change its status to waiting .

CANCEL To ask NetView FTP VSE to cancel thefile-transfer request. The file-transferrequest status is set to finished .


DVG603I � DVG613I

DVG603I TRANSFER reqnum ENDED;RC=retcd;RSN=rsncd

Explanation: This message informs the recipient ofthe outcome of the file transfer.

reqnum Request number. This can be zero, ifthere is no valid file-transfer request whenthe message is issued.

retcd Return code from file transfer.

rsncd Reason code from file transfer.


User Action: If the return code is 0, no action isrequired. If the return code is not 0, the return andreason codes indicate the required action.

DVG610A COMMUNICATION WITH VSE/POWER NOTESTABLISHED;REPLY WITH “GO” TO CONTINUE OR “STOPNVFTP” TO TERMINATE

Explanation: The communication withVSE/POWER could not be established at NetViewFTP partition startup time, so NetView FTP VSEcannot send file-transfer reports.

System Action: The program waits for an operatorresponse. Further processing depends on theoperator’s response.

User Action: The operator should first reply to thismessage with one of the following:

GO To indicate that NetView FTP VSE is tocontinue processing without sending anytransfer report files.

STOP NVFTPTo indicate that NetView FTP VSE is toterminate processing.

and then analyze the problem referring to messageDVG613I in the log file.

DVG611W COMMUNICATION WITH VSE/POWERINTERRUPTED;PROCESSING CONTINUES WITHOUT REPORTTRANSMISSION;REPLY WITH “GO” TO CONTINUE OR “STOPNVFTP” TO TERMINATE

Explanation: The NetView FTP partitionestablished communication with VSE/POWER, butthe communication was interrupted while theNetView FTP partition was running. NetView FTPVSE can no longer send transfer reports.

System Action: The program continues transferringfiles without sending any transfer report files until areply is received. The message remains on thescreen until the operator replies.


GO To indicate that NetView FTP VSE is tocontinue transferring files without sendingany transfer report files.

STOP NVFTPStop all servers immediately andterminate processing in the NetView FTPpartition.

Then analyze the problem referring to messageDVG613I in the log file.

DVG612W COMMUNICATION WITH VSE/POWER NOTESTABLISHED OR INTERRUPTED;PROCESSING CONTINUES WITHOUT REPORTTRANSMISSIONREPLY WITH “GO” TO CONTINUE OR “STOPNVFTP” TO TERMINATE

Explanation: Either NetView FTP VSE could notestablish communication with VSE/POWER orcommunication with VSE/POWER was interrupted. Ifthe NetView FTP partition initialization parameterOPMODE is set to UNATTENDED this message isissued instead of DVG610A or DVG611A.

System Action: The program continues transferringfiles without sending any transfer report files until areply is received. The message remains on thescreen until the operator replies.


GO To indicate that NetView FTP VSE is tocontinue transferring files without sendingany transfer report files.

STOP NVFTPStop all servers immediately andterminate processing in the NetView FTPpartition.

Then analyze the problem referring to messageDVG613I in the log file.

DVG613I COMMUNICATION WITH VSE/POWER FAILED;NETVIEW FTP TASK = task-name;RETURN CODE = retcd;FUNCTION = function;POWER SAS RETURN INFO (HEX) = errinfo

Explanation: This message is written to the log filewhenever any of the messages concerningVSE/POWER communication problems (DVG610A,DVG611A, DVG612I) are written to the operator’sconsole. It contains more information about theproblem.

task-nameName of the affected NetView FTP task.

retcd VSE/POWER or XPCC return code.


DVG614I � DVG619I

function Performed XPCC function.

errinfo Additional error information. One or twohexadecimal digits for each of thefollowing:

� XPCC return code� XPCC reason code� VSE/POWER return code� VSE/POWER feedback code.

See VSE/POWER 4.1 Application Programming forinformation about VSE/POWER return and feedbackcodes.

System Action: Processing continues according tocorresponding message DVG610A, DVG611A, orDVG612A.

User Action: Analyze the information in themessage to find the reason for the problem. It maybe caused by one of the following:

� VSE/POWER problems (for example: noresponse within 2 minutes or termination)

� VSE XPCC System GETVIS problems.

DVG614I DEVICE TYPE dev-type ASSIGNED TO lunum

Explanation: A tape device of type dev-type isassigned to the logical unit lunum.

dev-type Type of tape device.

lunum Logical unit number of the tape unit.

System Action: None.

User Action: If the correct tape-device type isassigned, none. If the tape-device type is notcorrect, stop NetView FTP and check NetView FTPVSE tape definition table.

DVG615I NO TAPE DEVICE TYPE FOUND FOR lunum;DEVICE TYPE CODE dev-type;UNIT IGNORED

Explanation: The VSE EXTRACT macro did notreturn the device-type number and VSE PUB devicetype code is not X'50', X'52', or X'53'.

lunum Logical unit number of unit.

dev-type PUB device type code.

System Action: NetView FTP VSE ignores thetape unit.

User Action: Check that the tape unit is correctlyassigned. This situation should not occur with IBMtape units. If it does, contact your IBM SupportCenter.

DVG616I CDLOAD OF TAPE DEFINITION TABLE FAILED;CDLOAD RETURN CODE = cdlretcdALL TAPE UNITS IGNORED;

Explanation: The tape definition table (DVGTDF)could not be loaded. All assigned tape units areignored and file-transfer requests, involving filesstored on tape, cannot be satisfied.

cdlretcd Return code from the VSE CDLOADmacro.

System Action: NetView FTP VSE acts as if notape unit is assigned.

User Action: NetView FTP VSE continues withouttape units. If these are urgently needed, terminatethe program and correct the error condition byincluding the DVGTDF phase in the defined libraries.

DVG618I UNKNOWN DEVICE MODE FOUND FOR lunum;DEVICE MODE device mode;

Explanation: The tape mode taken from the VSEPhysical Unit Control Block (PUB) could not be foundin the tape definition table (DVGTDF).

If the tape device assigned to this logical unit numberis not a cartridge device, it is not possible to write toan unlabeled tape. If the tape device assigned tothis logical unit number is a cartridge device thatallows data compression, it is not possible to write tothis cartridge.

lunum Logical unit number of tape unit.

device modeUnknown tape device mode.

System Action: NetView FTP VSE cannot write tounlabeled reel tapes or to cartridge tape units thatallow data compression.

User Action: Check whether the tape unit assignedto the logical unit number is shown in the NetViewFTP VSE tape definition table. If not, only restricteduse is possible.

DVG619I UNKNOWN DEVICE TYPE FOUND FOR lunum;DEVICE TYPE CODE device type code;

Explanation: The device type extracted from theVSE Physical Unit Control Block Extension (PUBX)could not be found in the tape definition table(DVGTDF).

lunum Logical unit number of tape unit.

device type codeUnknown device type code.

System Action: NetView FTP VSE uses the tapeunit as assigned.

User Action: Check whether the tape deviceassigned to the logical unit number is shown in theNetView FTP VSE tape definition table. If not, onlyrestricted use is possible.


DVG620I � DVG627I

DVG620I REQUEST QUEUE NOT CLEANED UP

Explanation: During initialization of a NetView FTPpartition, requests on the request queue that havethe status active were not given the status waiting ,because another NetView FTP partition or anotherNetView FTP user interface is already running.

System Action: Initialization of the NetView FTPpartition continues.

User Action: None.

DVG621I REQUEST QUEUE SUCCESSFULLY CLEANEDUP;recnum REQUEST(S) REQUEUED

Explanation: During initialization of the NetViewFTP partition, any requests in the request queue thathave the status active were given the statuswaiting .

recnum Number of records that were requeued.

System Action: Initialization of the NetView FTPpartition continues.

User Action: None.

DVG622I ERROR WHEN DEFINING A LOCK FOR THEREQUEST QUEUE;ERROR CODE FROM GENDTL = code

Explanation: When generating DTL for requestqueue locks, via the system macro GENDTL, anerror occurred.

code System return code.

System Action: The queue handler is stopped.

User Action: See VSE/ESA Version 1 SystemMacros Reference or VSE/AF 4.1.1 MacroReference.

DVG623I ERROR WHEN LOCKING THE REQUESTQUEUE;ERROR CODE FROM LOCK = code

Explanation: An error occurred when the queuehandler task tried to lock the request queue.




DVG624I ERROR WHEN UNLOCKING THE REQUESTQUEUE;ERROR CODE FROM UNLOCK = code

Explanation: An error occurred when the queuehandler task tried to unlock the request queue.




DVG625I ERROR IN THE REQUEST QUEUE WHILEPROCESSING REQUEST NUMBER number

Explanation: During processing of a queue handlercommand either a logical error was detected for arequest in the request queue or an inconsistency hasbeen detected between the request queue’s basecluster and its alternate index.

number The number of the request that was beingprocessed.

System Action: Processing is terminated.

User Action: Ask the NetView FTP systemadministrator to delete the faulty request, or torebuild the alternate index.

DVG626I REQUEST NUMBER reqnum NOT DELETED;REQUEST IS ACTIVE

Explanation: A user tried to delete an activerequest but requests marked as active cannot bedeleted.


System Action: Processing continues. If a requestis still active after a NetView FTP partition ends, it isautomatically requeued and given the status waiting .

User Action: Either wait until the transfer hasfinished and then delete the request, or ask youroperator to stop the server that handles the requestat the moment, and then delete the request, before itis restarted again.

DVG627I RETRIEVAL OF REQUEST reqnum FAILED

Explanation: An attempt to retrieve the requestwith the given request number from request queuefailed, although this is a valid request number.


System Action: Queue handler processingterminates.

User Action: Ask your system administrator tocheck the request queue.


DVG628I � DVG632I

DVG628I CLUSTER DEFINITION OF num TOO SMALLFOR REQUEST QUEUE

Explanation: The queue handler recognized thatthe number of records generated for the requestqueue was too small. No records for use byrequests could be added.

num Number of records in request queue.

System Action: Queue handler processingterminates.

User Action: Define a larger request queue.

DVG629I num RECORD(S) IN ERROR ON REQUESTQUEUE;STARTING RECORD NUMBER = strtno;ENDING RECORD NUMBER = endno

Explanation: While scanning the request queue fora query request, records were found with an error intheir request status fields.

num Number of records in error.

strtno Record number of the first record in errorin the request queue.

endno Record number of the last record in errorin the request queue.


User Action: Notify your system administrator.Print the request queue and identify the record inerror using the request number that can be found:

� For MVS and VM, at offset 0 with a length of 4bytes

� For VSE, at offset 16 with a length of 4 bytes.


DVG630I NETVIEW FTP PARTITION jobname STARTEDON yy/mm/dd AT hh:mm:ss

Explanation: The NetView FTP partitioninitialization is completed.

jobname Job name of the NetView FTP partition.

yy/mm/dd Date that the NetView FTP partitionstarted: yy=year, mm=month, dd=day.

hh:mm:ss Time that the NetView FTP partitionstarted: hh=hour, mm=minute,ss=second.


User Action: None.

DVG631I NETVIEW FTP PARTITION jobname ENDEDON yy/mm/dd AT hh:mm:ss;RETURN CODE=retcd;REASON CODE = rsncd;OPERATING SYSTEM RETURN CODE =opsysrc

Explanation: The NetView FTP partition stopped.

jobname Job name of the NetView FTP partition.

yy/mm/dd Date that the NetView FTP partitionstopped: yy=year, mm=month, dd=day.

hh:mm:ss Time that the NetView FTP partitionstopped: hh=hour, mm=minute,ss=second.

retcd Highest return code returned by a server(at least 4) or from the NetView FTPpartition.

rsncd Reason code from the NetView FTPpartition.

opsysrc Return code from the related operatingsystem.

System Action: The NetView FTP partition stops.

User Action: None.

DVG632I NETVIEW FTP TASK task TERMINATEDABNORMALLY;TASK RETURN CODE = stretcd;TASK REASON CODE = strsncd;SYSTEM INFORMATION = sysinfo

Explanation: The specified task terminatedabnormally.

task Server ID (or server prefix + QH, TC, UN,SY, or OI) of the task that terminatedabnormally.

stretcd Return code from the task.

strsncd Reason code from the task.

sysinfo Additional system ABEND information.

System Action: NetView FTP VSE proceeds asfollows:

� If a server task terminated abnormally and thereis still at least one started server, the number ofavailable servers is reduced.

� If a server task terminated abnormally and theserver was the last started server, andAUTOTERM=YES was specified in the startupjob for the NetView FTP partition, the maintaskterminates.

� If another task is terminated abnormally (that is,where the last two characters are QH, TC, UN,SY, or OI) the NetView FTP partition terminatesimmediately.

User Action: None.


DVG633I � DVG639I

DVG633I NETVIEW FTP PARTITION INITIALIZATIONFAILED;RETURN CODE = retcd;REASON CODE = rsncd;SYSTEM CODE = syscd

Explanation: An error occurred during initializationof a NetView FTP partition.

retcd Return code (decimal) from the NetViewFTP partition.

rsncd Reason code (decimal) from the NetViewFTP partition.

syscd Return code (decimal) from the relatedoperating system. If the return code isgreater than zero the GETVIS systemmacro failed.

System Action: The NetView FTP partition job iscanceled.

User Action: Correct the error and restart the job.

DVG634I COMMAND command CURRENTLY NOTALLOWED;VALID COMMANDS ARE list

Explanation: This message is written to theoperator’s console whenever NetView FTP cannotcurrently handle a NetView FTP operator command.

commandCommand entered by the operator.

list List of valid commands. Can be any ofthe following:

C Cancel a file-transfer request fora tape file

E End operator communicationD Display informationF Modify a serverG Make NetView FTP continue

processingM Indicate that a requested tape is

mountedP Stop servers or the NetView FTP

partitionR Requeue a file-transfer request

for a tape fileS Start servers.


User Action: Enter one of the allowed commands.

Other operator commands can be entered afterenabling the operator interface using the VSE MSGcommand.

Note: When AUTOTERMINATION is set to YESand all servers have stopped. Enter END to causethe NetView FTP partition to finish termination. Noother command is allowed.

DVG635I SEVERE ERROR WHILE PROCESSING FILETRANSFER;FILE TRANSFER INTERRUPTED

Explanation: An error occurred in the NetView FTPpartition processing while your file-transfer requestwas being processed.


User Action: If you want the file transfer to bereestablished, ask the operator if there is a serverstarted that processes the class of the interruptedrequest. If not, ask the operator to start one, andthen resubmit your request. If the problem persists,contact your IBM Support Center.

DVG638I CDLOAD OF MODULE phase FAILED; RETURNCODE FROM CDLOAD = cdrc

Explanation: The loading of an essential modulefailed during initialization of NetView FTP. This maybe because you tried to load a message definitionmodule that is not available. The message modulename is in the form DVGCCMDx, where x representsthe first letter of the specified language.

phase Name of load module.cdrc Return code from CDLOAD.

System Action: Processing terminated.

User Action: Ask your administrator to check if theload module is available, or refer to VSE/ESAVersion 1 System Macros Reference or VSE/AF4.1.1 Macro Reference for information about thereturn code.

DVG639I MACRO macro FAILED; RETURN CODE = retcd;PHASE NAME = phase-name

Explanation: An error occurred in a NetView FTPcomponent when it attempted to load or delete amodule.

macro Macro that encountered the error:

� LOAD � CDLOAD � DELETE.

retcd Return code from the macro. For moreinformation about this return code, refer toVSE/ESA Version 1 System MacrosReference or VSE/AF 4.1.1 MacroReference.

phase-namePhase name.

System Action: Processing terminates if the erroroccurs when loading or deleting an essential loadmodule.


DVG640I � DVG647I

User Action: If the problem persists for:

� LOAD, analyze the return code� CDLOAD, analyze the return code� DELETE, contact your IBM Support Center.

DVG640I LOCAL VSE/POWER HAS NO PNET SUPPORT;RETURN CODE FROM POWER = retcd

Explanation: This message is issued duringinitialization of the NetView FTP partition if noVSE/POWER PNET support is installed on your VSEsystem.

retcd The POWER return code from PWRSPL.

System Action: Processing continues. No spoolingof NetView FTP transfer reports takes place.

User Action: None.

DVG641I TRANSMISSION TO VSE/POWER PNET NODEnode WAS REQUESTED BUT PNET WAS NOTAVAILABLE;REPORT WAS NOT TRANSMITTED

Explanation: A file-transfer request specified that afile-transfer report was to be sent to a user at theremote VSE/POWER node shown in the message,however VSE/POWER PNET support was notavailable.

This message precedes the corresponding report inthe report collection file.

System Action: The report is not transmitted.

User Action: Ask your system administrator toprovide VSE/POWER PNET support.

DVG642I VSE/POWER SAS OPEN WAS REJECTED;FEEDBACK CODE = code;REPORT DESTINATION = user AT node;REPORT WAS NOT TRANSMITTED

Explanation: The VSE/POWER spool accessservices (SAS) rejected the transmission startuprequest for this transmission.


code VSE/POWER SAS feedback code asdescribed in VSE macro PWRSPL.

user User to whom the report was to be sent.

node VSE/POWER node of the user to whomthe report was to be sent.


User Action: Check the user ID and node namespecified in the request; possibly one of these isincorrect. If they are both correct, analyze theVSE/POWER SAS feedback code.

DVG643I VSE/POWER SAS COMMUNICATION NOTAVAILABLE;REPORT WAS NOT TRANSMITTED

Explanation: VSE/POWER spool access services(SAS) communication could not be established orwas interrupted.



User Action: Stop NetView FTP. After you canestablish an XPCC connection via the VSE/POWERSAS, restart NetView FTP.

DVG645I TASK task1 TRIED TO POST TASK task2 BUTtask2 WAS NOT READY

Explanation: While processing a file-transferrequest a task tried to post another task but theposted task was not ready.

task1 Posting task.

task2 Posted task.


User Action: Contact your IBM Support Center.

DVG646I THE OPERATOR HAS CANCELED A TAPE-FILETRANSFER

Explanation: You tried to transfer a tape file,however, the operator received a tape mountmessage and canceled the tape-file transfer.


User Action: Contact the tape operator at thesystem where the file transfer was canceled.Resubmit the file transfer when the tape operator isable to handle your file-transfer request.

DVG647I THE OPERATOR HAS REQUEUED A TAPE-FILETRANSFER

Explanation: You tried to transfer a tape file,however, the operator received a tape mountmessage and requeued the tape-file transfer.

System Action: The file transfer ends. Dependingon the value of the Automatic Transfer Restartparameter, NetView FTP changes the status of therequest either to waiting or finished .

User Action: Take whatever action is appropriate.


DVG648I � DVG660I

DVG648I THE TRANSFER OF A TAPE FILE IS NOTPOSSIBLE AT AN UNATTENDED NODE

Explanation: You tried to transfer a tape file but thesystem where the tape file is stored is running inunattended mode.


User Action: Take whatever action is appropriate.For example, ask the system administrator at thesystem where the file transfer has been stopped tochange to attended mode.

DVG650I TAPE UNIT SELECTION FAILED;REASON CODE = rsncd

Explanation: NetView FTP failed to select a tapeunit from the FTP Tape Unit List. The reason codecontains details of the problem.

rsncd Reason code from tape select. Refer toChapter 2, “NetView FTP ABEND,Return, and Reason Codes” on page 109.

System Action: The server processing the requestterminates. The request is finished or requeued,depending on the reason code.

User Action: Specify the tape information in therequest or wait for the next request selection for filetransfer.

DVG651I SERVER servername HELD ACCESSAUTHORIZATION LONGER THAN ALLOWED BYTHE TIME INTERVAL intval;THE SERVER HAS STOPPED

Explanation: The server has requested AccessAuthorization. Access Authorization was notdisabled within the specified time interval.

servernameServer ID holding Access Authorization.

intval Timer interval.

System Action: The server is forced to terminateabnormally to avoid security problems.

User Action: Check why the time interval is notsufficient for the functions requiring AccessAuthorization. For example, an outstanding tapemount, or a program loop in a user-written filehandler.

In the case of a program loop in a user-written filehandler that can establish its own recovery routine,this user-written file handler cannot be used until theNetView FTP partition has stopped.

DVG655I STORAGE MANAGEMENT SUBSYSTEM (SMS)IS NOT AVAILABLE

Explanation: Dynamic allocation for the receivingdata set failed and returned error reason code 1232(X'04D0').

System Action: The server tries to dynamicallyallocate the receiving data set without using the SMSparameters specified in the request.

User Action: None.

DVG656I text

Explanation: This message contains output fromDynamic Allocation. If a problem occurred duringdynamic allocation, this message might help yousolve the problem.


User Action: None.

DVG657I SMS PARAMETERS;DATA CLASS = dataclass;MANAGEMENT CLASS = manclass;STORAGE CLASS = storclass

Explanation: This message is issued at the end ofa file transfer for which SMS parameters werespecified.

dataclass SMS data class.manclass SMS management class.storclass SMS storage class.


User Action: None.

DVG660I JOB jobname(jobid) SUBMITTED;MEMBER NAME = memname;DATA SET NAME = dsname

Explanation: NetView FTP successfully submitteda post-transfer job.

jobname The job name of the submitted job.

jobid The job ID of the submitted job assignedby the job entry system.

memnameThe name of the member containing theJCL of the submitted job.

dsname The name of the data set containing themember memname.


User Action: None.


DVG661I � DVG667I

DVG661I DYNAMIC ALLOCATION ERROR;DATA SET NAME = dsname;RETURN CODE = retcd;INFORMATION REASON CODE = infcode;ERROR REASON CODE = errcode

Explanation: An error occurred during the dynamicallocation of the data set containing the job.

dsname Name of the data set in error. If thedata-set name is INTRDR, a dynamicallocation error occurred for the SYSOUTdata set that was destined for the internalreader.

retcd Return code.

infcode Information reason code.

errcode Error reason code.


User Action: Refer to the description of thedynamic allocation interface return (DAIR) errors thatcan be found in the online ISPF tutorial. For furtherinformation, refer to:


Volume 1.

DVG662I I/O ERROR FOR QSAM macro;DATA SET NAME = dsname;UNIT = unit;DEVICE TYPE = devtype;OPERATION = operation;ERROR DESCRIPTION = errordesc;PHYSICAL RECORD ADDRESS = bbcchhr

Explanation: An I/O error occurred while NetViewFTP was processing the job submission request viaQSAM.

macro QSAM macro in error is one of thefollowing:

� CLOSE � GET � OPEN � PUT.

dsname Name of the data set.

unit Unit address.

devtype Device type.

operation Operation attempted.

errordesc Description of error.

bbcchhr Direct access address of record in error.

System Action: The job is not submitted.Processing continues.

User Action: See one or more of the following:



DVG663I MEMBER memname NOT FOUND;DATA SET NAME = dsname

Explanation: The data set with the name dsnamedid not contain the member with the namememname. The post-transfer job submissionparameter values are not correct.


User Action: Take whatever action is appropriate.For example, make sure the member exists and itsname is specified correctly.

DVG666I DATA SET ORGANIZATION IS NOT PO;DATA SET NAME = dsname;DSORG RETURNED BY SVC 99 = dsorg

Explanation: The data set containing apost-transfer job must be partitioned organized (PO).SVC 99 (sometimes referred to as DynamicAllocation Service) returned a DSORG other thanPO.

dsname The name of the data set.

dsorg The DSORG that SVC 99 returned for thedata set.


User Action: Refer to MVS/ESA SPL: ApplicationDevelopment Guide and MVS/XA System Macrosand Facilities Volume 1 for information aboutDSORG return specifications from SVC 99.

DVG667I VSAM request ERROR ON INTERNAL READERDATA SET;REG 15 RETURN CODE = reg15;VSAM ERROR CODE = errcode

Explanation: An error occurred during jobsubmission processing of the VSAM SYSOUT dataset allocated to the internal reader.

request One of the following:

� OPEN � PUT � ENDREQ � CLOSE.

reg15 Contents of register 15 returned byVSAM.

errcode VSAM error code.

System Action: The submitted job is not executed.Processing continues.



� MVS/XA VSAM Administration Macro InstructionReference.


DVG668I � DVG675W

DVG668I MEMBER memname OF DATA SET dsname ISEMPTY

Explanation: The member with the namememname specified to contain the JCL of the job tobe submitted is empty.


User Action: Either fill the member with theappropriate job, or correct the member name ordata-set name if they were wrongly specified.

DVG670I NETVIEW EVENTS

Explanation: Certain NetView FTP events areissued to the operator’s console as WTO messages.A NetView CLIST scanning these messages caninitiate automatic operations according to theinformation issued with the event.


User Action: None. For more information, refer toNetView FTP V2 MVS Installation, Operation, andAdministration.

DVG671I MODULE module SUCCESSFULLY LOADED

Explanation: The module to be executed asspecified by the post-transfer program parameterwas loaded successfully.

module Name of load module.


User Action: None.

DVG672I ERROR WHILE LOADING module;SYSTEM ABEND CODE = abnd;SYSTEM REASON CODE = rscd

Explanation: During execution of a LOADmacroinstruction, a system error occurred.

module Module name that could not be loaded.

abnd System ABEND code.

rscd System reason code.

System Action: The specified module is notloaded. Processing continues.

User Action: Refer to one or more of the following:


� MVS/XA Supervisor Services and Macros.

DVG673I DATA SET ORGANIZATION MISMATCH;TARGET DATA SET IS A VSAM RELATIVERECORD DATA SET

Explanation: To transfer data to a VSAM RRDS,the source file must also be relative recordorganized.


User Action: Check whether the specified data setnames are correct. If the source data set is notrelative-record organized, specify a data set with adata set organization other than VSAM RRDS astarget data set.

DVG674I VSAM LINEAR DATA SETS CANNOT BETRANSFERRED FROM OR TO OTHER DATASET TYPES

Explanation: NetView FTP does not support thecombination of VSAM linear data sets and data setsof different types within one file transfer.



DVG675W CONTROL INTERVALS FOUND WHILEOPENING VSAM LINEAR DATA SET dsname

Explanation: The receiving data set is a VSAMlinear data set and has the name dsname. Whileopening the receiving data set the server detectedthat it was not empty. Because a related checkpointrecord did not exist, the server expected thereceiving data set to be empty. The server writesover any existing control intervals. If there are morecontrol intervals in the data set than are beingtransferred to it, these other control intervals remainin the data set. This may cause an integrity problem.

System Action: The server writes control intervalsfrom the beginning of the data set. A warning isissued in the file-transfer completion message.

User Action: If an integrity problem exists, deleteand redefine the data set. After you have correctedthe errors, resubmit the file-transfer request. If nointegrity problem exists ignore the message.


DVG676I � DVG690I

DVG676I REMOTE CHECK FOR FILE TRANSFERREQUEST reqnum STARTED ON yy/mm/dd AThh:mm:ss

Explanation: Remote check was specified in therequest. This is the date and time that NetView FTPstarted checking the file-transfer request reqnum.


yy/mm/dd Date that the remote check started:yy=year, mm=month, dd=day.

hh:mm:ss Time that the remote check started:hh=hour, mm=minute, ss=second.

System Action: NetView FTP processingcontinues.

User Action: None.

DVG677I REMOTE CHECK FOR FILE TRANSFERREQUEST reqnum ENDED ON yy/mm/dd AThh:mm:ss;RC = retcd;RSN = rsncd

Explanation: Remote check was specified in therequest. This is the date and time that NetView FTPfinished checking the file-transfer request reqnum.

yy/mm/dd Date that the remote check finished:yy=year, mm=month, dd=day.

hh:mm:ss Time that the remote check finished:hh=hour, mm=minute, ss=second.

retcd Return code.

rsncd Reason code.


User Action: None.

DVG678I CHECK reqnum ENDED;RC = retcd;RSN = rsncd

Explanation: Remote check was specified in therequest. This message is issued when a remotecheck has finished.


retcd Return code from the remote check.

rsncd Reason code from the remote check.

Refer to Chapter 2, “NetView FTP ABEND, Return,and Reason Codes” on page 109.

System Action: Processing continues. If the returncode from the remote check is zero, the file-transferrequest is requeued with the status WAITING.Otherwise, the transfer request is given the statusFINISHED.

User Action: If the file-transfer request has thestatus WAITING, no action is necessary. Otherwise,check the return and reason code that explains theerror. Correct it and resubmit the request.

DVG679W RECORDS FOUND WHILE OPENING VSAMRRDS dsname

Explanation: The receiving data set is a VSAMRRDS and has the name dsname. During the OPENon the receiving data set, the server detected that itwas not empty.

System Action: Processing continues; the serverwrites records from the beginning of the data set. Awarning is issued in the file-transfer completionmessage.

User Action: If an integrity problem exists, deleteand redefine the data set and, after you havecorrected the errors, resubmit the file-transferrequest.

DVG680I MODIFICATION OF TRANSFER REQUESTREJECTED BECAUSE OF INVALID INPUTFROM THE POST-CONVERSATION EXITROUTINE

Explanation: The post-conversation user exitroutine was called. On return, NetView FTPdetected any of the following incorrect modificationsmade to the file-transfer request:

� Not-after time and date

� Not-before time and date

� Restart from checkpoint indicator.

System Action: NetView FTP processingcontinues. The file-transfer request is not modified.

User Action: Check the modification made in thepost-conversation user exit routine. Refer toNetView FTP Customization for a further explanationof what modifications can be made. Correct theerror, and compile and link the exit routine.

DVG690I REQUEST QUEUE INFORMATION; QUEUE SIZE= size

Explanation: This message is issued in responseto an administrator query for information about therequest queue.

size The total number of requests the requestqueue can hold. This number is specifiedby the system administrator wheninitializing the queue.


User Action: None.


DVG701A � DVG710I

DVG701A MOUNT labeltype TAPE volser WITH RING ONUNIT unit WITH DENSITY density


labeltype Can be one of the following:

SL Standard labelNL Unlabeled

volser Volume serial number of the tape to bemounted. If a value for the volume serialnumber for an unlabeled tape is notspecified, the default value is SCRTCH.


density Tape density.

System Action: The file service component thatneeds the tape waits until the operator replies to themessage. NetView FTP continues processing, butcannot display any further NetView FTP consolemessages until the operator replies to the message.

User Action: Mount the required tape.

DVG702A MOUNT labeltype TAPE volser WITHOUT RINGON UNIT unit WITH DENSITY density


labeltype Can be one of the following:

SL Standard labelNL Unlabeled

volser Volume serial number of the tape to bemounted. If a value for the volume serialnumber for an unlabeled tape is notspecified, the default value is SCRTCH.

unit Tape unit name that the tape is to bemounted on.

density Tape density.

System Action: The file-service component thatneeds the tape waits until the operator replies to themessage. NetView FTP continues processing, butcannot display any further NetView FTP consolemessages until the operator replies to the message.

User Action: Mount the required tape.

DVG704I FILE-SERVICE COMPONENT COULD NOTLOAD CMSAMS DCSS;CMS RETURN CODE = retcd

Explanation: The file-service component virtualmachine tried to load the CMSAMS discontiguousshared segment, but the LODSYS command failed.

retcd Return code from the LODSYS CMScommand that was issued. Can be any ofthe following:

1 Named segment defined as aVMGROUP

44 Named segment does not exist

174 Paging I/O errors

179 The DASD volume specified bySYSVOL in the NAMESYS macrois not owned by CP

203 Users in a V=R area.

System Action: Processing terminates.


DVG705I USER NOT CONNECTED TO SPECIFIED RACFGROUP

Explanation: In the access security parameters,you specified a RACF group ID to which you are notconnected.



DVG707I DISTRIBUTION-SERVICE COMPONENT WITHTHE USER ID userid IS UNABLE TO ESTABLISHRACF ENVIRONMENT

Explanation: In the access security parameters,you either specified an incorrect password, or thedistribution service machine does not have thecorrect RACF authorization.



DVG710I INVALID USER ID userid SPECIFIED INFILE-SERVICE COMPONENT TABLE

Explanation: NetView FTP VM detected a syntaxerror in the user ID specified for a file servicecomponent table.

System Action: The user ID is ignored andprocessing continues.

User Action: Contact your system administrator tocorrect the file service component table-entry.


DVG711I � DVG717I

DVG711I AUTOLOG OF userid WAS UNSUCCESSFUL;CP RETURN CODE = retcd

Explanation: The distribution service componentfailed to AUTOLOG the file service componentshown in the message.

retcd Return code returned by CP, see one ormore of the following:

� VM/ESA System Messages andCodes for 370

� VM/XA SP System Messages andCodes Reference

� VM/SP System Messages andCodes.

System Action: NetView FTP VM tries toAUTOLOG the next free file service componentvirtual machine. If running under VM/ESA*,XAUTOLOG is used.

User Action: None.

DVG712I THE MAXIMUM NUMBER OF REQUESTHANDLERS IS rhnum, BUT ONLY fsmnumFILE-SERVICE COMPONENTS ARE SPECIFIED

Explanation: There are not enough file servicecomponents declared in the file service componentstable.

rhnum Maximum number of request handlers.fsmnum Number of file service components.

System Action: Processing continues. Thenumber of request handlers is reduced to the numberof file-service components.

User Action: The system administrator can correctthe problem by either:

� Reducing the number of tasks (AVLSESS,MAXSESS, AVLLRH, and AVLRRH initializationparameters)

� Increasing the number of file servicecomponents in the file service component table.

DVG713I userid ALREADY LOGGED ON

Explanation: An entry in the file service componenttable has been found but the file service componentis already logged on.

userid User ID or resource ID of the file servicecomponent virtual machine.

System Action: Processing continues. Thefile-transfer request that caused this message isrequeued. It remains in the WAITING status untilany of the following happens:

� Another file service component that serves theclass specified obtains the request andprocesses it

� The operator solves the problem.


� Contact your system administrator� FORCE the indicated user ID.

DVG714I command COMMAND EXECUTION FAILED;RETURN CODE = retcd

Explanation: The CMS/CP command shown in themessage failed.


retcd CMS/CP command return code, see oneor more of the following:

� VM/ESA System Messages andCodes for 370

� VM/XA SP System Messages andCodes Reference

� VM/SP System Messages andCodes.

fsmnum Number of file service components.


DVG716A REPLY TO file-server WITH M(OUNTED),R(EQUEUE), OR C(ANCEL)

Explanation: This message is preceded bymessage DVG701A or DVG702A.

file-serverThe user ID or resource ID of thefile-service component.

System Action: The file service component thatneeds the tape waits until the operator replies to themessage. NetView FTP continues processing, butcannot display any further NetView FTP consolemessages until the operator replies to the message.

User Action: The operator must enter at least thefirst letter of one of the following:

MOUNTED Indicating that the tape was mountedas requested.

REQUEUE Asking NetView FTP VM to put thefile-transfer request back on therequest queue.

CANCEL Asking NetView FTP VM to cancelthe request.

DVG717I THE USER ID OF THE CHECKPOINT MANAGERIS DIFFERENT FROM THE USER ID SPECIFIEDFOR THE CMID INITIALIZATION PARAMETER

Explanation: You specified a value for theCheckpoint Manager ID (CMID) initializationparameter but the checkpoint manager does not runin the virtual machine you specified.


User Action: Run the checkpoint manager in thevirtual machine indicated by the checkpoint managerID initialization parameter.


DVG718I � DVG725I

DVG718I NO ENTRY IN FILE-SERVICE COMPONENTTABLE FOUND

Explanation: The distribution-service componenttried to build the file-service component table, butthere is no valid entry in DVGFST MACHINES file.

System Action: Server terminates duringinitialization.

User Action: Check your file service componenttable definitions. Make sure that the FILEDEFcommand concatenates the correct file to thesystem.

DVG720I FUNCTION function FAILED FOR MACHINEuserid

Explanation: An error occurred when one of thefollowing functions for a checkpoint record wasexecuted by the checkpoint manager:

function Can be one of the following functions:

� GET � PUT � DELETE.

userid User ID or resource ID of the file servicecomponent that the checkpoint managerperformed the function for.

System Action: All file transfers currently inprogress finish. If the error occurred during a GETfunction, processing continues. Otherwise, thecheckpoint manager terminates. No new request isobtained. Also all file service components anddistribution service components terminate.

User Action: Examine the checkpoint manager logfile. Look for additional messages that help you tosolve the problem. Correct the error and restart allterminated NetView FTP components.

DVG721I NETVIEW FTP release;CHECKPOINT MANAGER userid STARTED ONdate AT time;MAINTENANCE LEVEL = mlevel

Explanation: This is the startup message of thecheckpoint manager.

release Release level of the transfer program.

userid User ID or resource ID of the checkpointmanager virtual machine.

date Date that the checkpoint manager virtualmachine started: year/month/day.

time Time that the checkpoint manager virtualmachine started: hours/minutes/seconds.

mlevel Program maintenance level informationmaintained by the system administrator.


User Action: None.

DVG722I NETVIEW FTP release;CHECKPOINT MANAGER userid ENDED ON dateAT time;RETURN CODE=retcd

Explanation: This is the termination message ofthe checkpoint manager.

release Release level of the transfer program.

userid User ID or resource ID of the checkpointmanager virtual machine.

date Date that the checkpoint manager virtualmachine stopped: year/month/day.

time Time that the checkpoint manager virtualmachine stopped:hours/minutes/seconds.



User Action: None.

DVG723I message

Explanation: This is a VM system message that isissued whenever a VM error occurs. For example,when a CMS command fails, or an OPEN erroroccurs.

System Action: The system action depends on theerror. Either processing continues or thecorresponding component terminates.

User Action: If the error is caused by incorrectlyspecified file-transfer parameters, correct theparameters and resubmit the file-transfer request.

DVG724I NETVIEW FTP CHECKPOINT MANAGERINITIALIZATION FAILED; REASON CODE =rsncd

Explanation: An error occurred while thecheckpoint manager was being initialized.

rsncd Reason code. For more information referto Chapter 2, “NetView FTP ABEND,Return, and Reason Codes” on page 109.

System Action: The checkpoint managerterminates and produces a dump. No file transfercan be processed.

User Action: Check the reason code to identify thecause of the failure.

DVG725I QUEUE HANDLER IS NOT ACTIVE

Explanation: The operator entered a modify or stopoperator command but the queue handler was notactive.


User Action: None.


DVG726I � DVG730I

DVG726I SUBCOMMAND ENTERED FOR NETVIEW FTPNOT ACCEPTED

Explanation: The operator entered an unknownsubcommand or an incorrect abbreviation of asubcommand.


User Action: Enter a valid NetView FTPsubcommand.

DVG727I REQUEST CONTAINS PARAMETERS NOTSUPPORTED BY TRANSFER PROGRAM;ERROR CODE = error-code

Explanation: When checking the request, it wasdetected that parameters were specified by one ofthe following sources:

� Pre-transfer user exit routine� Request from a remote system.


01 PDS member selectionparameter

02 PDS member exclusionparameter

03 PDS member informationparameter

04 Encryption parameter

05 Sending OS/400 parameter

06 Receiving OS/400 parameter

07 Extended user exit informationparameters

08 Local job submission data

09 Remote job submission data

10 Local program call parameter

11 Remote program call parameter

12 SMS parameter

13 APPC parameter.


User Action: None.

DVG728I DISPOSITION VALUE value IS NOT ALLOWEDFOR DATA SET TYPE type

Explanation: The value specified for disposition isnot valid for the specified data-set type.

value The value specified for the Dispositionparameter.

type The value specified for the Data-Set Typeparameter.



� A server, the file transfer ends.


DVG729I DISPOSITION VALUE value IS NOT ALLOWEDFOR DATA SET TYPE type FOR THEOPERATING SYSTEM opsys

Explanation: The value specified for disposition isnot valid for the specified data-set type for thecorresponding operating system.



� A server, the file transfer ends.

value The value specified for the Dispositionparameter.

type The value specified for the Data-Set Typeparameter.

opsys The operating system that the transferprogram runs under (MVS, VM, VSE, orOS/400).


DVG730I ERROR DURING COMMUNICATIONPROCESSING TO resource;COMMUNICATION FUNCTION = function;REASON CODE = rsncd

Explanation: The NetView FTP communicationinterface detected an error while preparing orperforming an APPC/VM or IUCV function andissued a reason code.

resource Resource ID or User ID.

function Function from APPC/VM (for VM/SP) orIUCV (for VM/XA).

rsncd File-transfer reason code.

System Action: The NetView FTP component thatissued the message ends.

User Action: Check the reason code. Refer toChapter 2, “NetView FTP ABEND, Return, andReason Codes” on page 109 for more information.


DVG731I � DVG741I

DVG731I ERROR DURING function PROCESSING TOresource;code-field = error-code

Explanation: An error occurred during APPC/VM orIUCV processing.


� CONNECT � SENDDATA � SEND � SENDERR � RECEIVE.


code-field One of the following:

� IPRCODE � IPAUDIT1 � IPAUDIT2 � IPAUDIT3 � Condition code.

error-codeThe value of the field specified incode-field.


User Action: For a description of the error codessee:

� VM/ESA CP Programming Services for 370� VM/XA SP CP Programming Services� VM System Facilities for Programming.

DVG732I ERROR DURING macro function PROCESSINGTO resource;RETURN CODE = retcd

Explanation: The value of the return code fielddescribes the completion of the macro issued.

macro One of the following:

� HNDIUCV � IUCVINI � CMSIUCV � IUCVCOM.


� SET � CONNECT � CLR.




User Action: For a description of the return codesee the following:

� VM/ESA CMS Application DevelopmentReference for Assembler

� VM/ESA Group Control System Reference for370

� VM/XA SP CMS Application ProgramDevelopment Reference

� VM/XA SP Group Control System Commandand Macro Reference

� VM/SP Application Development Reference forCMS

� VM/SP Group Control System Command andMacro Reference.

DVG733I OPEN ON FILE DVGAS NOT SUCCESSFUL;FTP DEFAULTS WILL BE TAKEN

Explanation: An error occurred while opening thefile DVGAS. Either, you did not specify a FILEDEFfor the DVGAS file and want to use the defaults, oranother open error occurred.

System Action: Processing continues using thedefault values.

User Action: None.

DVG734I NO CONNECTION RECEIVED FROM QUEUEHANDLER

Explanation: To establish an operator path thequeue handler must connect to thedistribution-service component, but thedistribution-service component did not receive aconnect request.

System Action: The distribution-service componentterminates.

User Action: Contact your system administrator.After the problem is solved, restart the distributionservice component.

DVG741I NETVIEW FTP release; DISTRIBUTION-SERVICECOMPONENT userid STARTED ON date AT time;MAINTENANCE LEVEL = mlevel

Explanation: A server started.


userid User ID or resource ID of the distributionservice component virtual machine.

date Date that the distribution service machinestarted: year/month/day.

time Time that the distribution service machinestarted: hour:minute:second.

mlevel Program maintenance-level information;maintained by your system administrator.


User Action: None.


DVG742I � DVG801I

DVG742I NETVIEW FTP release; DISTRIBUTION-SERVICECOMPONENT userid ENDED ON date AT time;RETURN CODE = retcd

Explanation: A server stopped running.


userid User ID or resource ID of the distributionservice component virtual machine.

date Date that the server distribution servicecomponent virtual machine stopped:year/month/day.

time Time that the distribution servicecomponent virtual machine stopped:hours:minutes:seconds.

retcd Distribution service component virtualmachine return code.

The return code shows whether any errors occurredwhile the distribution service component virtualmachine was stopping.

System Action: The distribution service componentvirtual machine stops.

User Action: If the return code is 0, no action isrequired. If the return code is not 0, refer toChapter 2, “NetView FTP ABEND, Return, andReason Codes” on page 109 to find out what itmeans.

DVG761I NO CONNECTION FROM THE FILE-SERVICECOMPONENT RECEIVED;FILE TRANSFER TERMINATED

Explanation: A subtask in the distribution servicecomponent virtual machine, which had been attachedto process a file transfer, had still not received aconnect from the file service machine after 5minutes.

System Action: The status of the file-transferrequest is changed to waiting .

User Action: Check that the file service machinewas autologged correctly and that the PROFILEEXEC is correct.

DVG762I DATA TRANSFERRED FROM THEDISTRIBUTION-SERVICE COMPONENT TO THEFILE-SERVICE COMPONENT WAS TRUNCATED

Explanation: A remote transfer program sent a FileInterchange Unit (FIU) that could not be handled byNetView FTP VM. The file service component virtualmachine examines the data and then issues amessage explaining the error.

System Action: The file transfer ends.


DVG763I ERROR RECEIVING INITIAL CONTROL BLOCKSFROM DISTRIBUTION-SERVICE COMPONENT;FILE TRANSFER TERMINATED

Explanation: An error occurred while a file servicecomponent virtual machine received the initial controlblocks from its distribution service component virtualmachine.

System Action: The file transfer is terminated. Thestatus of the file-transfer request is changed tofinished .

User Action: Check that NetView FTP wasinstalled correctly. If the problem is not caused byyour installation, contact your IBM Support Center.

DVG764I DISTRIBUTION-SERVICE COMPONENT useridDID NOT ACCEPT COMMUNICATION PATH

Explanation: No communication path to thedistribution service virtual machine component virtualmachine is established.

userid User ID or resource ID of the distributionservice virtual machine to which acommunication path tried to establish.

System Action: The file service component virtualmachine terminates.

User Action: Check if the file DVGAS NAMES inyour file service component virtual machine containsthe valid user ID or resource ID of the distributionservice component virtual machine that autologgedthe file service component virtual machine.

DVG800I CURRENTLY, NOT ENOUGH STORAGE ISAVAILABLE AT THE REMOTE SYSTEM

Explanation: This message is issued if the remotetransfer program that processes your request cannotacquire enough virtual storage to perform the filetransfer.

System Action: The file transfer terminates.

User Action: Ask the system administrator at theremote system to correct the error, then resubmityour request.

DVG801I REMOTE TRANSFER PROGRAM IS NOT ABLETO PROCESS YOUR REQUEST DUE TO ASYSTEM EXCEPTION

Explanation: This message is issued if the remotetransfer program that processes your request has asystem exception, for example, a bad return codefrom an operating system macro.




DVG802I � DVG809I

DVG802I THERE IS A STORAGE MEDIUM ERROR

Explanation: While accessing a file the remotefile-transfer program that processes your requestencountered a storage medium error.



DVG803I YOU MUST SPECIFY THE PARAMETER WITHTHE BATCH JOB KEYWORD keywordOr, for NetView FTP V2.2 MVS:

DVG803I YOU MUST SPECIFY THE PARAMETERparameter

Explanation: The remote transfer programrecognized that you did not specify a requiredparameter in the file-transfer request.

keyword The batch job interface keyword.parameter The NetView FTP parameter.


User Action: Correct the file-transfer request, thenresubmit your request.

DVG804I DO NOT SPECIFY THE PARAMETER WITH THEBATCH JOB KEYWORD keywordOr, for NetView FTP V2.2 MVS:

DVG804I DO NOT SPECIFY THE PARAMETER parameter

Explanation: The remote transfer programrecognized that you specified a parameter that is notallowed in the file-transfer request.


parameter The NetView FTP parameter.



DVG805I YOU SPECIFIED PARAMETER parameter MORETHAN ONCE

Explanation: The remote transfer programrecognized that you specified the parameter morethan once, however, this parameter can only bespecified once.

parameter The corresponding batch job interfacekeyword or parameter name.



DVG806I THE PARAMETER WITH THE BATCH JOBKEYWORD keyword IS NOT SUPPORTEDOr, for NetView FTP V2.2 MVS:

DVG806I THE PARAMETER parameter IS NOTSUPPORTED

Explanation: The remote transfer programrecognized that you specified a parameter that itdoes not support.





DVG807I YOU DID NOT SPECIFY A REQUIREDCOMBINATION OF PARAMETERS

Explanation: The remote transfer programrecognized that a necessary combination ofparameters were not specified in the file-transferrequest.

This message is accompanied by the messageDVG840I that tells you the parameters to bespecified.



DVG808I YOU SPECIFIED A COMBINATION OFPARAMETERS THAT IS NOT ALLOWED

Explanation: The remote transfer programrecognized that a combination of parameters that isnot allowed were specified in the file-transfer request.

This message is accompanied by the messageDVG840I that tells you the parameters not to bespecified together.



DVG809I YOU DID NOT SPECIFY PARAMETERS THATNEED TO BE SPECIFIED

Explanation: The remote transfer programrecognized that a combination of parameters aremissing in the file-transfer request.

This message is accompanied by the messageDVG841I that tells you the corresponding batch jobinterface keywords and values that are missing.




DVG810I � DVG815I

DVG810I YOU SPECIFIED PARAMETERS THAT ARE NOTALLOWED IN THIS COMBINATION

Explanation: The remote transfer programrecognized that a combination of parameters werenot allowed in the file-transfer request.

This message is accompanied by the messageDVG841I that tells you the corresponding batch jobinterface keywords and values that are not allowed.



DVG811I THE VALUE value FOR THE PARAMETER WITHTHE BATCH JOB KEYWORD keyword IS NOTSUPPORTEDOr, for NetView FTP V2.2 MVS:

DVG811I THE VALUE value FOR THE PARAMETERparameter IS NOT SUPPORTED

Explanation: The remote transfer programrecognized that a value has been specified that itdoes not support.

value Is the value of the parameter

keyword The batch job interface keyword




DVG812I YOU SPECIFIED PARAMETER VALUES THATARE INCOMPATIBLE

Explanation: The remote transfer programrecognized that incompatible parameter values werespecified.

This message is accompanied by the messageDVG841I that tells you the corresponding batch jobinterface keywords and values that are incompatible.



DVG813I A VALUE FOR THE PARAMETER parameterCONTAINS AN INCORRECT CHARACTER char(HEX hex)

Explanation: The remote transfer programrecognized that a parameter value contained acharacter that is not allowed.

The characters that NetView FTP supports for thisparameter depends on the parameter.

keyword The corresponding batch job interfacekeyword or parameter name (NetViewFTP V2.2 MVS)

char The character that is not supported

hex The hexadecimal value of the characterchar.



DVG814I THE VALUE value IS NOT IN THE RANGE OFALLOWED VALUES FOR THE PARAMETERWITH THE BATCH JOB KEYWORD keyword;maximum IS THE MAXIMUM ALLOWED VALUEOr, for NetView FTP V2.2 MVS:

DVG814I THE VALUE value IS NOT IN THE RANGE OFALLOWED VALUES FOR THE PARAMETERparameter;maximum IS THE MAXIMUM ALLOWED VALUE

Explanation: The remote transfer programrecognized that a parameter contained a value that isnot in the range of allowed values.



parameter The parameter name

maximum Is the maximum value allowed.



DVG815I YOU ARE NOT ALLOWED TO SPECIFY THEVALUE value FOR PARAMETER WITH THEBATCH JOB KEYWORD keywordOr, for NetView FTP V2.2 MVS:

DVG815I YOU ARE NOT ALLOWED TO SPECIFY THEVALUE value FOR PARAMETER parameter

Explanation: The remote transfer programrecognized that a value was specified for thisparameter that is not valid.



parameter The parameter name.




DVG816I � DVG824I

DVG816I FILE file-id ALREADY EXISTS

Explanation: The remote transfer programrecognized that a file that was to be created alreadyexists.

file-id Is the file ID of the file to be created.



DVG817I MEMBER member-name OF FILE file-idALREADY EXISTS

Explanation: The remote transfer programrecognized that a member of a file that was to becreated already exists.

member-nameName of the member in the file.

file-id Is the file ID that contains the member.



DVG818I RECORD record-key OF FILE file-id ALREADYEXISTS

Explanation: The remote transfer programrecognized that a record to be added to a file alreadyexists.

file-id Is the file ID of the file to be updated.

record-keyIs the record key that already exists.



DVG819I VOLUME OR MINIDISK volume NOT FOUNDOr, for NetView FTP V2.2 MVS:

DVG819I VOLUME, MINIDISK, OR PATH volume NOTFOUND

Explanation: The remote transfer program couldnot find the volume, minidisk, or path to read from orwrite to.

Volume Is the volume, minidisk, or path that wasnot found.



DVG820I FILE file-id NOT FOUND

Explanation: The remote transfer programrecognized that a file to be updated does not exist.




DVG821I MEMBER member-name IN FILE file-id NOTFOUND

Explanation: The remote transfer programrecognized that a member of a file to be updateddoes not exists.

file-id Is the file ID of the file that should containthe member.

member-nameIs the name of the member in the file.



DVG822I RECORD record-key IN FILE file-id NOT FOUND

Explanation: The remote transfer programrecognized that the record to be updated does notexist.

record-keyIs the record key of the record to beupdated.




DVG823I VOLUME OR MINIDISK volume IS FULL

Explanation: The remote transfer programrecognized that a volume or minidisk is full.

volume Is the name of the volume or minidisk.



DVG824I FILE file-id IS FULL

Explanation: The remote transfer programrecognized that the file that it writes to is full.

file-id Is the file ID of the file.




DVG825I � DVG831I

DVG825I MEMBER member-name IN FILE file-id IS FULL

Explanation: The remote transfer programrecognized that a member of a file that it writes to isfull.

member-nameIs the name of the member in the file.




DVG826I FILE file-id IS IN USE

Explanation: The remote transfer programrecognized that a file that it reads from or writes to isin use.



User Action: Ensure that the file is not in use thenresubmit the request.

DVG827I THE REMOTE FILE TRANSFER PROGRAM ISNOT AUTHORIZED TO ACCESS THE FILE ATTHE REMOTE SYSTEM

Explanation: The remote transfer programrecognized that it cannot access a file it was to readfrom or write to. This can happen if the user IDspecified in the request is not authorized to accessthe file.


User Action: Correct the access securityparameters in your file-transfer request, thenresubmit the request.

DVG828I YOUR FILE TRANSFER FAILED TO RESTART

Explanation: The remote transfer program detectedan error during restart.


User Action:

NetView FTP V2.2 MVS:Check the value of the File StatusOption and resubmit the request.

NetView FTP other than NetView FTP V2.2 MVS:Change the value of the Restart fromCheckpoint parameter to NO andresubmit the request. The file transfer isrestarted from the beginning.

DVG829I YOUR FILE TRANSFER WAS INTERRUPTED BYidentifier

Explanation: The remote transfer program wasinterrupted.

identifier One of the following:

� The NetView FTP operator� A user-exit routine� The request originator� The NetView FTP administrator.


User Action: None.

DVG830I FUNCTION function-code NOT SUPPORTEDOr, for NetView FTP V2.2 MVS:

DVG830I function NOT SUPPORTED

Explanation: The remote transfer program does notsupport a required function.


function-code Where the function not supported isrepresented by:

01 Data-set organization02 User exits.

NetView FTP V2.2 MVS:

function can be one of the following:

� Data-set organization

� User exits.


User Action: None.

DVG831I FUNCTION function-code NOT ACTIVEOr, for NetView FTP V2.2 MVS:

DVG831I function NOT ACTIVE

Explanation: The remote transfer program cannotperform a required function because it is not active.NetView FTP other than NetView FTP V2.2 MVS:

function-code Where the function not active isrepresented by:

01 User exits02 Encryption support03 SMS support.


function can be one of the following:

� User exits � Encryption support � SMS support.


User Action: Ask the operator at the remotelocation to activate the function.


DVG832I � DVG842I

DVG832I FUNCTION function-code NOT OPERATIONALOr, for NetView FTP V2.2 MVS:

DVG832I function NOT OPERATIONAL

Explanation: The remote transfer program cannotperform a required function because it is notoperational.


function-code Where the function not operational isrepresented by:

02 Encryption support.


function is encryption support.

System Action: The file transfer terminatesbecause an error occurred while invoking thefunction.

User Action: None.

DVG833I ERROR CODE RETURNED BY comp,CODE VALUE = value.

Explanation: The remote transfer program cannotprocess your request due to a system exception.

comp Component where the error occurred. Itcan be one of the following: C Runtime NetBIOS OS2

value System code number.



DVG834I PARAMETER parameter IS NOT SUPPORTEDBY THE PARTNER SYSTEM

Explanation: You specified a parameter that is notsupported by the partner system.



DVG839I A PROTOCOL VIOLATION OCCURRED

Explanation: The transfer program has detected asituation that violates the transfer protocol. Thetransfer reason code shows whether the local or theremote transfer program detected the violation. If thepartner system is on a higher NetView FTP level, theviolation most likely is caused by a new function thatis not supported by the local system.


User Action: Check the log and report informationof the partner server that was involved in thistransfer, especially for messages in the range fromDVG803 to DVG815. If both sides show messageDVG839I and do not contain further informationidentifying certain file-transfer parameters that shouldbe specified or omitted, contact your IBM SupportCenter.

DVG840I PARAMETER = keyword

Explanation: This message informs you about aparameter in error with the corresponding batch jobkeyword.

keyword Batch job keyword.

System Action: See the messages that accompanythis message.

User Action: See the messages that accompanythis message.

DVG841I PARAMETER = keyword; VALUE = value

Explanation: This message informs you about theparameter and value in error with the correspondingbatch job keyword.

keyword Batch job keyword.

System Action: See the messages that accompanythis message.

User Action: See the messages that accompanythis message.

DVG842I NAME = protocol-name; ID = protocol-id; LENGTH= length; VALUE = value

Explanation: This message is for diagnosispurposes only. It is issued when a log of theprotocol message units is requested or when aprotocol violation is detected.

If a protocol log is requested, all items of receivedprotocol message units are logged. If a protocolviolation occurred, all items of the protocol errormessage unit are logged.

protocol-name The name of the protocol item.

protocol-id The hexadecimal identifier of theprotocol item.

length The length of the value of theprotocol item.

value The value of the protocol item. Ifthe length is zero, nothing isprinted. Otherwise, the value upto a maximum of 100 charactersis printed, even if the protocolitem contains more data.

System Action: If a protocol violation occurred, thefile transfer terminates. If a protocol log is written,processing continues.

User Action: None.


DVG843I � DVG904I

DVG843I FILE TRANSFER REQUEST NOT ACCEPTED.

Explanation: The file-transfer request is notaccepted by the remote transfer partner. If it is atemporary problem (reason code 567), probably thetransfer limit is exceeded. If it is a permanentproblem (reason code 568), probably the APPCConversation Security parameters are missing inyour file-transfer request.

System Action: The file transfer does not start andNetView FTP changes the status of the request towaiting if it is a temporary problem, and to finishedif it is a permanent problem.

User Action: For a temporary error, none. For apermanent error, correct the error and resubmit therequest.

DVG844I FILE TRANSFER REQUEST NOT ACCEPTED,RESPONDING WORKSTATION NOT ACTIVE.

Explanation: The file-transfer request is notaccepted because the responder at the remotesystem is not active.

System Action: The file transfer does not start andNetView FTP changes the status of the request towaiting .

User Action: Have the responder started.

DVG845I FILE NAME DOES NOT CORRESPOND TO THENAMING RULES AT THE RECEIVING SYSTEM.

Explanation: You used a file name that does notadhere to the naming rules of the receiving system.


User Action: Specify a file name that meets therules of the receiving system and resubmit thefile-transfer request.

DVG846I ACCESS VIOLATION, FILE IS READ-ONLY.

Explanation: You tried to write to a file that isread-only.

System Action: The file-transfer ends and NetViewFTP changes the status of the request to finished .

User Action: Either use another receiving file orchange the access authority of the file.

DVG850I ERROR MESSAGE RECEIVED FROM REMOTEFILE-TRANSFER PROGRAM: message text

Explanation: This message informs you abouterrors when the remote transfer program processesyour request.

message textIs the message text as created by theremote transfer program.


User Action: See the message text created by theremote file-transfer program.

DVG903I MODULE modulename;FUNCTION function ENTERED; TRACE ACTIVE

Explanation: This message is issued when thetrace function was activated.

modulenameThe name of the module for which thetrace mask was set.

function The name of the function that was set.

System Action: Trace output is written, processingcontinues.

User Action: None.

DVG904I MODULE modulename;FUNCTION function EXITED; TRACE ACTIVE;ERROR CODE = error-code

Explanation: This message is issued when thetrace function was activated.

modulenameThe name of the module for which thetrace mask was set.

function The name of the trace function that wasset.

error-code One of the following:

0 No error1 Processing continues2 Request in progress3 Request not available4 Request terminated5 System abort reported from

OSI/File Services6 Request completed8 OSI server function reported

general error10 Access to other filestore

missing11 Access to own filestore missing12 OSI server function reported

severe error13 Temporary error in OSI/File

Services14 Condition code not found20 Server terminating


DVG907I � DVG913I

21 Request will be skipped23 File entry not registered in

server filestore, temporaryentry will be made

24 File entry does not exist25 Temporary error in queue

handlerNONE Specific error code not defined.

System Action: Trace output is written, processingcontinues.

User Action: None.

DVG907I OSI/FS PASSWORD FOR OSI SERVERservername IS INVALID

Explanation: The OSI server tried to log on toOSI/FS. However, the password specified with theOIUSRPWD keyword of the OSI server initializationcontrol statement was not accepted by OSI/FS. Theinitialization of the OSI server is unsuccessful.

servernameThe job name or STC name under whichthe server was started.

System Action: The OSI server terminates.

User Action: Specify the correct password andrestart the OSI server.

DVG908I OSI/FS PASSWORD FOR OSI SERVERservername CHANGED

Explanation: The password to log on to OSI/FShas been successfully changed. The new passwordwas specified with the OINUSRPW keyword of theOSI server initialization statement.



User Action: None.

DVG909I RECOVERY FILE READ nnn REQUESTS TORECOVER

Explanation: This message indicates the number ofrequests to be recovered following termination of theOSI server.

When the OSI server terminates due to an error inthe queue handler or if OSI/File Services isterminated (using the immediate command) by theoperator, the recovery file is written. The recoveryfile is read and the number of requests to berecovered is specified by the value nnn. Informationto complete the unfinished request is passed to theOSI server before it terminates and is kept in therecovery file.

This message is issued whenever an OSI server isstarted.

nnn Number of requests to be recovered.


User Action: None.

DVG910I REQUEST reqnum CANNOT BE RECOVEREDAND IS CANCELED

Explanation: The request reqnum is marked asuncompleted in the recovery file. The request cannotbe finished successfully by the OSI server and istherefore canceled.

reqnum Name of the request not finishedsuccessfully.


User Action: Resubmit the request.

DVG911I RECOVERY COMPLETED

Explanation: All requests stored in the recovery fileafter an abnormal OSI server termination werecompleted.


User Action: None.

DVG912I USERID userid NOT REGISTERED IN LRD

Explanation: This message is issued if thespecified user ID is not registered in the localresource directory.

userid Name of the incorrect user ID.

System Action: The request is rejected.

User Action: Specify the correct user ID or get theOSI/File Services administrator to enter it in the localresource directory, and then resubmit the request.

DVG913I ERROR DURING OSI SERVER servernameINITIALIZATION PHASE

Explanation: The server is terminating due to anerror during the initialization of the OSI server. Thismessage is usually preceded by a messagedescribing the failure.


System Action: The OSI server is not started.

User Action: Check the log file for messages thatmight help you to analyze the problem. After youhave corrected the problem, restart the server.


DVG914I � DVG921I

DVG914I ACF/LRD SPACE PROBLEMS;RETURN CODE =rc, CONDITION CODE = cc.

Explanation: OSI/FS detected space problems onthe Access Control File or in the Local ResourceDirectory.

rc Return code.cc Condition code. Refer to OSI/File

Services System /370 User’s Guide foran explanation of the condition codes.

System Action: Depending on the return code,NetView FTP changes the status of the request towaiting or to finished .

User Action: Delete ACF/LRD entries and resubmitthe request.

DVG919I UNKNOWN ERROR FROM OSI/FS;FUNCTION func SERVER servername;RETURN CODE = retcd;CONDITION CODE = condcd

Explanation: OSI/File Services has returned acondition code that cannot be handled by the OSIserver. It may indicate that a new release ofOSI/File Services contains new condition codes, andthe current release of the OSI server is notcompatible with this release of OSI/File Services.

func Function in which the error occurred.


retcd Return code.

condcd Condition code. Refer to OSI/FileServices for MVS User’s Guide for anexplanation of the condition codes.

System Action: Depending on the return code,NetView FTP changes the status of the request towaiting or to finished , or the server terminates.


DVG920I OSI/FS COMMAND cmd ISSUED BY OSISERVER servername FAILED; RETURN CODE =retcd; CONDITION CODE = condcd

Explanation: The OSI server issued a command toaddress the OSI/File Services component. Thiscommand was not successful.


STR Start of OSI/File ServicesEND Termination of OSI/File

ServicesLENT List entry of local resource

directoryLFIR List first entry of local

resource directoryCUPW Change user password.


retcd Return code.


System Action: The command is rejected and theOSI server terminates.


DVG921I OSI/FS COMMAND cmd ISSUED BY OSISERVER servername FOR REQUEST reqnumFAILED;RETURN CODE = retcd;CONDITION CODE = condcd

Explanation: The OSI server issued a command toaddress the OSI/File Services component for thespecified request. The command could not beprocessed successfully.


COPY Copy a fileMOVE Move a fileLENT List entry of local resource

directoryLFIR List first entry of local

resource directoryAENT Add entry to local resource

directoryRENT Remove entry from local

resource directoryGTRS Get resultCANC Cancel request.


retcd Return code.


System Action: The command and the request arerejected.

User Action: Check the request parameters andresubmit the request.


DVG922I � DVG926I

DVG922I REQUEST reqnum TERMINATED DUE TO USERERROR;RETURN CODE = retcd;CONDITION CODE = condcd

Explanation: This message is issued when yousubmit a request with incorrect parameters, orinsufficient local resource directory entries.

reqnum Number of the request.

retcd Return code.




DVG923I OSI SERVER TERMINATING DUE TO ANERROR IN OSI/FS

Explanation: This message is issued when the OSIserver is terminating due to a severe error in theOSI/File Services component. Possible reasons maybe:

� OSI/File Services not yet started� Lost connection to OSI/File Services� Internal error in OSI/File Services� Unexpected shutdown of OSI/File Services.

Normally, this message is preceded by a messagedescribing the failure.



DVG924I USER userid CANNOT CARRY OUT FILETRANSFER FOR REQUEST reqnum DUE TOMISMATCH BETWEEN LRD ENTRIES ANDREQUEST PARAMETERS

Explanation: The OSI/File Services server issuesthis message when it detects a mismatch betweenthe specifications in the local resource directory andthe request.

userid User ID that requested the file transfer.

reqnum Number of the file-transfer request.


User Action: Change the access authority asdescribed in OSI/File Services User’s Guide andresubmit the request.

DVG925I OSI SERVER TERMINATING DUE TO ANINTERNAL ERROR OF OSI SERVERservername; SIGNAL signal ISSUED

Explanation: An OSI server issues this messagewhen an internal server error occurs that causes theOSI server to terminate. Normally, this message ispreceded by a message describing the failure.


signal The OSI server containing C programsuses the following C/370* supportedsignals to handle error conditions:

SIGABRT Abnormal termination signalsent by the abend function.

SIGFPE Erroneous arithmeticexceptions, such as overflow,division by zero, or operationnot valid.

SIGILL Function image not valid,such as an object module oroperation exception that is notvalid.

SIGINT Interactive attention interrupt.SIGSEGV Access to memory not valid,

such as protection exceptionor addressing exception thatis not valid.

SIGTERM Termination request sent toprogram.


User Action: A detailed description of the C/370signals is provided in the C/370 User’s Guide.

Check the log file for messages that might help youto analyze the problem. The signal issued mightalso provide a clue. After you have corrected theproblem, restart the server.

DVG926I OSI SERVER TERMINATING DUE TO ANUNEXPECTED ERROR

Explanation: An OSI server issues this messagewhen an unexpected error occurred and the OSIserver is terminating. Normally, this message ispreceded by a message describing the error.




DVG927I � DVG990I

DVG927I REQUEST reqnum TERMINATED DUE TO ANUNEXPECTED ERROR

Explanation: An unexpected error occurredprocessing the request reqnum. Normally, thismessage is preceded by a message describing theerror.

reqnum Number of the request submitted.

System Action: The request is rejected and theOSI server terminates.

User Action: Check the log file for messages thatmay help you to analyze the problem. After youhave corrected the problem, restart the OSI serverand resubmit the request.

DVG928I FUNCTION function RETURNED WITH SEVEREERROR

Explanation: This message displays the internalsequence of server functions after an error occurred.Normally this message is preceded by a messagedescribing the failure.

function Name of the function in which the erroroccurred.


User Action: Check the log file for messages thatmay help you to analyze the problem. After youhave corrected the problem, restart the OSI serverand resubmit the request.

DVG929I OSI/FS COMMAND cmd RETURNEDRETURN CODE = retcd;CONDITION CODE = condcd

Explanation: This message is for information only.The return and condition codes are kept in the logfile for information.

cmd Name of the OSI/File Services command.

retcd Return code.



User Action: None.

DVG930I REQUEST reqnum TERMINATED

Explanation: The OSI server issues this messagewhen a request terminates.

reqnum Number of the request that finished.

System Action: The request is terminated.

User Action: Check the log file for messages thatmay help you analyze the problem. After you havecorrected the error, resubmit the request.

DVG931I REQUEST reqnum CANCELED

Explanation: The OSI server issues this messagewhen a request is canceled.

reqnum Number of the request that was canceled.

System Action: The request is terminated.Processing continues.

User Action: None.

DVG941I CLOSE ON ddname FAILED

Explanation: The OSI server issues this messagewhen an internal file cannot be closed.

ddname Name of the internal file that could not beclosed.



DVG942I UNEXPECTED COMPLETION CODE FOR ECBecb

Explanation: This message is issued when the OSIserver is posted with an event control block butcannot handle the completion code. It may indicateinconsistencies between the current versions of thequeue handler and the OSI server.

ecb Event control block.



DVG950I REQUEST reqnum WAS NOT AN OSI REQUEST

Explanation: The request is not an OSI request.

reqnum Number of the request.

System Action: The request is not submitted.

User Action: Check the request class. It must notbe a class assigned to an OSI server if an SNA-typerequest is to be submitted. Correct the error andresubmit the request.

DVG990I CLASS/PRIORITY = cl/pr;OSI SERVER NAME = servername;INITIATOR FUNCTION = func;TRANSFER MODE = tranmode;DESTINATION EFFECT = destneff

Explanation: This message gives information aboutthe request and the transfer.

cl/pr Server class and request priority of therequest.

servernameName of the OSI server.

func Function COPY or MOVE.

tranmode Transfer mode, T = To or F = From.


DVG991I � DVG993I

destneff Destination effect on the destination file; C(create), A (append), R (replace), CA(create or append), or CR (create orreplace).


User Action: None.

DVG991I FILESTORE OWNER = locusid;FILESTORE NICKNAME = fsnn;FILESTORE SUBSET = fssub;LOCAL FILE NAME = locflnam

Explanation: This message gives information aboutthe file at the local system.

locusid User ID of the filestore owner.

fsnn Filestore nickname.

fssub Filestore subset.

loclnam Local file name.


User Action: None.

DVG992I LOCAL OSI FILE NAME = locosifn;LOCAL ACCESS PASSWORDS = locaccpw;REMOTE FILESTORE AET = remfsaet;REMOTE OSI FILE NAME = rosifn;REMOTE ACCESS PASSWORDS = remaccpw

Explanation: This message gives information aboutlocal and remote parameters.

locosifn Local OSI file name.

locaccpw List of YES or NO values (for example,YYNNNY) indicating how the followingpasswords are set on the local system:

� Read � Extend � Replace � Read attributes � Delete file � Filestore � Create.

remfsaet Remote filestore application entity title bywhich the filestore can be identified byusers at the remote system.

rosifn Remote OSI file name. This is the nameby which the file can be identified andaccessed by users at the local andremote system.

remaccpwList of YES or NO values (for example,YYNNNY) indicating how the followingpasswords are set on the remote system:

� Read � Extend � Replace � Read attributes � Delete file � Filestore � Create.


User Action: None.

DVG993I DOCUMENT TYPE = doctype;UNIVERSAL CLASS = univcl;STRING SIGNIFICANCE = strsig;MAXIMUM STRING LENGTH = maxstrln;FUTURE FILE SIZE = futflsiz

Explanation: This message gives information aboutthe destination file.

doctype FTAM document-type of the file. Possiblevalues are:

F1 Defined as unstructured textF3 Defined as unstructured binary.

univcl The universal class parameter is an OSIterm that refers to the type of characterstring of which the contents of thedestination file are composed. Possiblevalues are:

G GeneralStringH GraphicStringI Ia5StringV VisibleString.

For further details see the FTAMstandards.

strsig The string significance is the recordformat of the destination file. Possiblevalues are:

F Fixed format. The string length isequal to the maximum string lengthspecified. The file is stored withthis record format.

U Unbounded format (not significant).The file may be stored with anyrecord format.

V Variable format. The string lengthis equal to, or less than themaximum string length specified.The file is stored with this recordformat.

maxstrln The maximum string length is the logicalrecord length of the destination file andmust be specified.

futflsiz The future file size is the maximum size,expressed in K bytes, to which the file isexpected to grow as a result of its futurehandling.


User Action: None.


DVG994I � DVG996I

DVG994I FILE AVAILABILITY = favail;PERMITTED ACTIONS = permact;ACCESS CONTROL ELEMENT ACTIONS =aceact;ACCESS CONTROL ELEMENT PASSWORDS =acepwds

Explanation: This message gives information aboutthe destination file.

favail Indicates whether or not the file is to beavailable immediately to users once it iscreated on their system. Possible valuesare:

I Immediate availabilityD Deferred availability.

permact Permitted actions is a list of the actionsallowed on the file. Each action can havethe value Y = YES, or N = NO, forexample, YYYNNY. Possible actions are:

� Read � Extend � Replace � Read attributes � Change attributes � Delete file.

aceact Access control element actions is the listof the actions allowed by the accesscontrol element. Each action can havethe value Y = YES, or N = NO, forexample, YYYNNY. Possible actions are:


acepwds Access control element passwords is thelist of the passwords related to the actionsdefined in the access control elementactions. Each action can have the valueY = YES, or N = NO to indicate whetheror not a password is assigned, forexample, YYYNNY. Possible passwordsare:



User Action: None.

DVG995I FUNCTION RETURN CODE = funcrc;FUNCTION CONDITION CODE = funccc;REQUEST START = reqstr;ACTIVITY STATUS = actstat;TRANSFERRED BYTES = bytes

Explanation: This message gives information aboutthe function output.

funcrc Specifies the final return code of theinitiator function (COPY or MOVE) relatedto the transfer request.

funccc Specifies the final condition code of theinitiator function (COPY or MOVE) relatedto the transfer request.

reqstr Date and time the request started.

actstat The current status of the transfer request.Possible values are:

INPR The transfer is still in progress.

COMP The transfer is complete.

ABCO The transfer terminates due toan ABORT function requestissued by the console operator.

ABFO The transfer terminates due to aCANCEL function request issuedby the owner of the filestore.

ABIU The transfer terminates due to aCANCEL function request issuedby the request issuer.

ABSY The transfer terminates due tothe program terminating.

bytes The number of bytes transferred duringthe transfer.


User Action: None.

DVG996I DIAGNOSTIC: ORIGIN = diagor;TYPE = diagtyp;ERROR IDENTIFIER = diagiden;SUGGESTED DELAY = diagdel;MESSAGE = diaginfo

Explanation: This message gives diagnosticinformation that is optionally provided by the remotesystem.

diagor Diagnostic origin specifies whether theerror was detected by the local system orby the remote system. Possible valuesare:

L Locally detectedR Remote detectedN No categorization possible.

diagtyp Diagnostic error type specifies the severityof the error. Possible values are:

I Informative messageT Transient errorP Permanent error.


diagiden Diagnostic error identifier is aclassification of the errors. It is an integerfield that takes one of the values definedin ISO FTAM-IS-Standard Part 3.

diagdel Diagnostic suggested delay is an integervalue specifying how many minutes theuser should wait before restarting thetransfer request. It is meaningful fortransient errors only.

diaginfo Diagnostic error information is a messagein natural language giving further detailsabout the cause of the error.


User Action: None.


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 CodesThe following ABEND codes are issued by a NetView FTP component when it requestsabnormal termination.

Figure 1. NetView FTP ABEND Codes

ABEND CodeDescription

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 CodesFigure 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 CodeDescription

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 wasnever started.

2 2 A server running in single mode was stopped by the operator immediately. A file transfer was in progress.


� 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, aQUERY 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 successfullybut a noncritical error occurred. The error does not affect the security or integrity of the data transferred.


Figure 2 (Part 2 of 2). NetView FTP Return Codes

Return CodeDescription

Dec Hex


� If the function was a file transfer, the file transfer completed successfully but an error occurred duringtermination processing.

� If the function was the termination of the queue handler or a server, the component terminated successfullybut an error occurred during termination processing.

12 C For one of the following reasons, depending on the function being carried out, processing failed after theinitialization 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 toan error.


� 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’sinitialization.

� If the NetView FTP partition was just started an error occurred during initialization of the NetView FTPpartition.


� 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 applicationprogram interface routine.

48 30 While carrying out a queue handler command, the batch job interface routine could not find the message definitionmodule.

54 36 This return code is issued by an OSI server. The component terminated successfully but a noncritical erroroccurred. 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. Therequest 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 codepassed 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 codepassed to the OSI server is 8, indicating an error. The request passed to OSI/File Services is rejected due toexternal conditions.

82* 52 This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return codepassed to the OSI server is 12, indicating an error. The request passed to OSI/File Services is rejected because itwas incorrect.

86* 56 This OSI/File Services function return code is issued by an OSI server. The OSI/File Services function return codepassed to the OSI server is 16, indicating a severe error. The request passed to OSI/File Services is rejectedbecause 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 codepassed to the OSI server is 20, indicating a catastrophic error. The request passed to OSI/File Services isrejected.


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

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

ReturnCode

Description User Actions

24 An error occurred during execution of a GETMAIN macro.Not enough space is available to run the program.

Check the size of the available region.

28 The ISPF environment is not established. The moduleISPLINK could not be loaded.

Check the library containing ISPLINK.

32 NetView FTP is unable to load and display panels from thepanel library. This may be due to one or more of thefollowing:

� The interactive interface was invoked with an incorrectlanguage parameter.

� Panel and message libraries are not allocated.

� The panel library is incorrect. Make sure the lastcharacter of the member name is the nationallanguage support character.

� The message library is incorrect. Make sure the fifthcharacter of the member name is the nationallanguage support character.

Check the following:

� The correct panel library is allocated.

� The correct parameter is specified when theinteractive interface was invoked. One parameter witha length of one character is allowed. This characterspecifies the language to be used.

Example: If you invoked the interactive interface with theparameter F, the first panel you normally see has thepanel ID DVGME00F, where the last character (F) is thelanguage character. The members in the message librarymust have the name DVGMFxx.

36 The saved request table could not be closed. Refer to ISPF Dialog Management Services and Examplesfor actions to be taken.

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

NetView FTP Reason CodesIn 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 (withreturn 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(Issued with Return Codes 0 to 20)

From Queue Handler Commands(Issued with Return Codes 0 and 24 to 48)Dec Hex

0 0 The file transfer completed successfully.

4 4 Label : RSSTAERR

Description :

Temporary allocation error or temporary rejection.


� The server tried to dynamically allocate a data setbut the attempt failed because of an allocationerror:

– The data set was probably being used byanother program.

– For NetView FTP VSE, the system lock tableor system lock file may be too small.

� The pre-transfer user-exit routine temporarilyrejected the file-transfer request. The pre-transferuser-exit routine might have passed a message toNetView FTP that explains why the request wasrejected.

Whether the server changed the status of thecorresponding request to waiting or finished dependson the value of the Automatic Transfer Restartparameter.

Label : RSNREQM

Description : Request accepted but modified bypre-queuing user-exit routine.

The queue handler successfully added the file-transferrequest to the request queue. This reason code is tolet the user know that the pre-queuing user-exit routinechanged one or more parameters in the file-transferrequest before it was added to the request queue. Thisreason code usually accompanies the return code 0.

8 8 Label : RSSPAERR

Description : Permanent allocation error.

The server tried to dynamically allocate a data set, butthe attempt failed because of an allocation error.Probably the parameters of the file-transfer requestwere incorrect. The server changed the status of thecorresponding request to finished , regardless of thevalue of the Automatic Transfer Restart parameter. Therequest is not reprocessed later.

Label : RSNNOFBA

Description : No address or length provided for theQRA, QRA too small, or no QSR (Query Status Record)provided.

An application program queried one or morefile-transfer requests, but did not provide the address orthe length of the query response area (QRA). TheQRA is the area into which NetView FTP is to write theinformation it retrieves. This reason code is also issuedif the area provided is too small to contain the statusinformation for at least one file-transfer request.

12 C Label : RSSOPNSE

Description : Error in OPNSEC macro.

The attempt to establish the ACF/VTAM sessioninitiated by a remote server failed with an error in theOPNSEC macro.

Label : RSNVBCER

Description : Incorrect queue handler command.


� An application program specified an incorrect valuefor the APLVBC field.

� A batch job specified an incorrect value for theFunction parameter.

16 10 Label : RSSVERR

Description : Global ACF/VTAM error.

The server tried to start an ACF/VTAM session for a filetransfer but the attempt failed with an ACF/VTAM error.The ACF/VTAM error was not necessarily caused bythe session being established.





20 14 Label : RSSMIKWD

Description : Mandatory parameter missing.

The server checked the parameters in the file-transferrequest and found that a mandatory parameter wasmissing from it. The pre-transfer user-exit routine mighthave changed the file-transfer request and omitted amandatory parameter.

Label : RSNMIKWD

Description : Mandatory parameters missing.

The user interfaces checked the file-transfer requestand found that one or more mandatory parameterswere missing from it. The file-transfer request wasrejected, that is, it was not added to the request queue.

24 18 Label: RSSNAVAI

Description : Remote server temporarily not available.

The local server tried to initiate an ACF/VTAM sessionbut the attempt failed because a remote server wastemporarily not available. Common reasons for this are:

� 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 correspondingrequest back to waiting , regardless of the value of theAutomatic Transfer Restart parameter. A server willreprocess the request later.

Label: RSNCSERR

Description: Parameter error.

The user interfaces checked the file-transfer requestand found either a syntactical error or an inappropriatevalue. The file-transfer request was rejected, that is, itwas not added to the request queue.

28 1C Label: RSSUNUS

Description: LU names for remote servers unusable.

The local server tried to initiate an ACF/VTAM session.The attempt failed because ACF/VTAM replied that theLU names used to identify the remote node wereunusable. Probably the LU names were not properlydefined in ACF/VTAM.

Label: RSNNOCS

Description: No parameters found.

No parameters were specified in the file-transferrequest. The file-transfer request was rejected, that is,it was not added to the request queue.

32 20 Label: RSSQHERR

Description: Queue handler error.

The server tried to issue a queue handler command toget or update a file-transfer request. The attempt failedbecause the queue handler signalled that an erroroccurred. The error is not necessarily related to thequeue handler command that the server issued.

Label: RSNOPERR

Description: Error when opening SYSIN.

When the batch job interface routine tried to openSYSIN, the attempt failed. Probably the appropriate DDstatement was missing from the startup job for thebatch job interface routine.

36 24 Label: RSSREST

Description: Not enough storage to restart transfer ofPDS.

The server tried to restart the transfer of a PDS from acheckpoint. It found the checkpoint record in thecheckpoint data set, but there was not enough storageavailable to restart the file transfer. Its attempt to use itto restart the transfer failed.

Label: RSNIOERR

Description: I/O error when reading from SYSIN.

An I/O error occurred when the batch job interfaceroutine tried to read from SYSIN.

37 25 Label: RSSPOREC

Description: Session recovery for a PDS memberfailed.

A server tried to recover a session during which a PDSmember was being transferred. The server retrieved,from the checkpoint data set, the number of the recordwith which it was to continue the transfer. Whilesearching through the member for that record, end ofmember (EOM) was reached and the record was neverfound.

Label: RSNAPLE1

Description: Incorrect APL control block ID (APLID)specified. Must be '*DVGAPL*' (APLACCR).





38 26 Label: RSSPORST

Description: Transfer restart for a PDS member failed.

A server tried to restart the transfer of a PDS member.The server retrieved, from the checkpoint data set, thenumber of the record with which it was to continue thetransfer. While searching through the member for thatrecord, end of member (EOM) was reached and therecord was never found.

Label: RSNAPLE2

Description: Incorrect APL length specified in fieldAPLLNGTH. Must be one of the values defined in theAPL length fields in macro DVGAPL.

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 organizationthat is not supported by NetView FTP.

44 2C Label: RSSTSESS

Description: Error during session termination.

The server tried to terminate an ACF/VTAM session atthe end of a file transfer but could not. Probably, thesession had already been terminated by ACF/VTAMwhen NetView FTP issued the session terminationrequest. This reason code does not necessarilyindicate 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/VTAMsession interrupt and tried to automatically recover thesession. However, this attempt failed. Probably,whatever caused the interrupt prevented the server fromrecovering the session.

52 34 Label: RSSIMMED

Description: Immediate termination during sessionrecovery.

During a file transfer, the server detected an ACF/VTAMsession interrupt and tried to automatically recover thesession. However, this attempt failed because thetermination 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 FTPwas to use a user-written file handler to gain access toa data set. An error occurred during the running of thefile handler.





60 3C Label: RSSVNCON

Description: Incompatible parameters.

The server checked the parameters in the file-transferrequest and found an incorrect combination ofparameters or parameter values. Probably, thepre-transfer user-exit routine modified the file-transferrequest incorrectly.

Label: RSNVNCON

Description: Parameter values not compatible.

A user interface checked the file-transfer request andfound at least one parameter value that wasincompatible with others. The file-transfer request wasrejected, that is, it was not added to the request queue.

If you are using the interactive interface, check thecontents of the additional parameters panels. If you donot find any incompatible values, add the file-transferrequest to the request queue again; NetView FTP mighthave changed one or more incompatible default valueswhen it displayed the additional panels.

64 40 Label: RSSDALER

Description: Deallocation error.

The server dynamically allocated a data set for a filetransfer. After the file transfer, the server tried todeallocate the data set, but the attempt failed. Possibly,a system error occurred.

Label: RSNNRCX

Description: Pre-queuing user-exit routine not found.

Before passing a file-transfer request on to the queuehandler, the user interfaces always pass control to thepre-queuing user-exit routine. This routine was notfound. The routine must be loadable from one of thecurrent link-list libraries. Probably an error was madeduring 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. Possiblereasons are:

� The operator canceled the server� A NetView FTP program error.

69 45 Label: RSSABAM

Description: Abnormal termination of server (MVS) orthe NetView FTP maintask (VSE).

A server terminated abnormally. The reason for theabnormal termination was not necessarily related to aspecific file transfer. Possible reasons are:

� The operator canceled the server� A NetView FTP program error.

72 48 Label: RSSDSNER

Description: Data-set names do not match.

Both a data-set name and a ddname were specified inthe file-transfer request. The data-set name specified inthe DD, DLBL, or TLBL statement that corresponds tothe ddname was different from the data-set namespecified in the file-transfer request.

Label: RSNDSNER

Description: The length of at least one data-set name(file ID) exceeds the maximum length.

In NetView FTP there is a maximum length allowed forfile IDs. For more information about maximum lengthrefer to NetView FTP Parameter Reference.

76 4C Label: RSSREINC

Description: Higher FTP level required.

A file-transfer request required a server to do somethingfor which its FTP level is too low. For more informationabout FTP levels, refer to the Operation andAdministration for your transfer program.





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 LUnames for the server group but the queue handler couldnot provide any names. Probably, the server grouptable was modified and the queue handler was restartedafter the file-transfer request was added to the requestqueue. The queue handler only provides LU namesthat 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 serverencountered an I/O error in the checkpoint data set.

96 60 Label: RSSCRNFD

Description: Checkpoint not found in data set beingtransferred.

The server tried to restart an interrupted file transferfrom a checkpoint. It found the checkpoint record in thecheckpoint data set, but its attempt to use it to restartthe transfer failed. Possible reasons are:

� Not enough storage was available to restart the filetransfer of a PDS member

� The server could not find the checkpoint in the dataset being transferred because that data set hasbeen modified since the checkpoint record waswritten.

100 64 Label: RSSDSNEM

Description: Error with KSDS option ADDBEG.

The file-transfer request specified the value ADDBEGfor the KSDS option, but the receiving data set alreadycontained records. This is not allowed with the valueADDBEG. The server at the receiving node broke offthe file transfer.

Label: RSNQIQNR

Description: Queue handler not ready.

A user interface routine issued a queue handlercommand but the queue handler was not started or hadnot yet finished its initialization processing. The queuehandler command was not carried out.

104 68 Label: RSSCRINV

Description: Incorrect checkpoint record found orcheckpoint data set full.

� NetView FTP uses different formats for thecheckpoint records used with user-written filehandlers and with NetView FTP file handlers. Theserver obtained a checkpoint record of the wrongformat. This is probably due to an integrityproblem.

� The server could not write a new checkpoint dataset. The file transfer continues. Refer to theInstallation, Operation, and Administration guide foryour NetView FTP.

Label: RSNSTQUI

Description: Delayed termination of queue handler inprogress.

A user interface routine issued a queue handlercommand. However, because the queue handler wasin a state of delayed termination, the queue handlercould not carry out the command.

108 6C Label: RSNSTIMM

Description: Immediate termination of queue handler inprogress.

A user interface routine issued a queue handlercommand. However, because the queue handler wasin a state of immediate termination, the queue handlercould not carry out the command.





112 70 Label: RSNAREJT

Description: Request queue is full.

The file-transfer request cannot be added to the requestqueue because there is no free space for it. Norequest can be added to the queue until one or morerequests are deleted from it.

116 74 Label: RSNSQBLD

Description: Queue handler presently rebuilding therequest queue.

The queue handler cannot carry out the queue handlercommand because it is rebuilding the request queue.When it has finished rebuilding the queue, the queuehandler can again carry out queue handler commands.The amount of time the queue handler needs to rebuildthe request queue depends on the size of the queue.

120 78 Label: RSSRCTER

Description: Mismatch in record or byte count.

After two servers successfully transfer a data set, theycompare the number of records or bytes each recorded,sent or received. The comparison resulted in amismatch. This problem might indicate a NetView FTPprogram error.

Label: RSNSSLFE

Description: Queue handler error.

The queue handler cannot carry out the queue handlercommand because, due to a NetView FTP programerror, no resources are available to it.

124 7C Label: RSSRINER

Description: Error in building an RACF environment.

The server tried to use the values of the securityparameters in the file-transfer request to build atemporary RACF environment, but the attempt failed.Probably, the values specified were incorrect.

Label: RSNSPSTE

Description: Communication error.

The SVC routine was not able to establishcommunication between the queue handler and theNetView FTP component that issued the queue handlercommand. This code indicates a NetView FTPinstallation error or an error in the system parameterdefinition.

128 80 Label: RSSRDLER

Description: Error in deleting an RACF environment.

The server transferred a data set under the control of apreviously built RACF environment. The attempt todelete this environment and reestablish the originalauthorization failed. This is probably due to a systemerror or a NetView FTP program error.

132 84 Label: RSSOPTRM

Description: Operator termination.

The file transfer was interrupted, due to one of thefollowing:

� The operator at the local system terminated one ofthe 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 causedit to terminate immediately.

� An irrecoverable error in the NetView FTP partitioncaused it to terminate immediately (VSE).





136 88 Label: RSSTIMEX

Description: Processing period elapsed.

The server obtained a file-transfer request from therequest queue. However, the not-after time specified inthe file-transfer request had already elapsed. Theserver did not carry out the file-transfer request.

Label: RSNNFND

Description: Request not found.

A user interface routine issued a queue handlercommand to delete, query, or modify a specificfile-transfer request, but the queue handler could notfind this request in the request queue.

140 8C Label: RSSSEND

Description: ACF/VTAM error while sending data.

The server encountered an ACF/VTAM error when ittried to send data. The data could have been eitherparts of the data set to be transferred or NetView FTPinternal control information.

Label: RSNQOFLW

Description: Request queue is full; queue rebuildstarted.

A user interface routine tried to add a request to thequeue but there was no space left in the queue. Thequeue handler started to rebuild the request queue, thatis, the queue handler started to delete successfullyfinished requests that have been in the queue longerthan the delay time set by the system programmer. Ifthe queue handler finds any such requests, there willbe free space in the queue again.

144 90 Label: RSSRECV

Description: ACF/VTAM error while receiving data.

The server encountered an ACF/VTAM error when ittried to receive data. The data could have been eitherparts of the data set to be transferred or NetView FTPinternal control information.

Label: RSNNOID

Description: Server group not found in server grouptable.

A file-transfer request specified a remote server group,but this server group was not found in the server grouptable. Possible reasons are:

� The file-transfer request contained the incorrectserver 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

Description: Incorrect parameter found.

The server checked the parameters in the file-transferrequest and found an incorrect parameter or anincorrect value for a parameter. Probably, thepre-transfer user-exit routine modified the file-transferrequest incorrectly.

Label: RSNINVAL

Description: Request contains incorrect parameters orparameter values.

A user interface routine checked the file-transferrequest and found an incorrect parameter or anincorrect value for a parameter. This code indicates auser error.

152 98 Label: RSSINOPS

Description: Parameter not compatible with operatingsystem.

The server checked the file-transfer request and foundthat one or more of the parameters were incompatiblewith the operating system under which the serveroperates.

Label: RSNINOPS

Description: Parameter not compatible with operatingsystem.

A user interface routine checked the file-transferrequest and found one or more values that wereincompatible with the operating system of the node forwhich they were specified. Possible reasons are:

� The user specified incorrect values when creatingthe file-transfer request

� The wrong operating system was specified for anode in the server group table.

156 9C Label: RSNNNDT

Description: Server group table not found.

A file-transfer request contained a value that requiresthat the queue handler loaded the server group tableduring its initialization. However, during its initialization,the queue handler did not find the server group tableand started without it. This error is probably due to anerror during installation.





160 A0 Label: RSNNAUTH

Description: Master password missing or incorrect.

A user interface routine issued A queue handlercommand to query, delete, or modify the file-transferrequest of another originator. However, the masterpassword 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 handlercommand to restart a file-transfer request. The requestis not available for restart processing for one of thefollowing 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 originatorspecified.

A user interface routine issued a queue handlercommand to delete or query file-transfer requests thatwere submitted by a specific originator. However, norequest was found for this originator or no request at allwas found in the request queue. This reason codeusually accompanies the return code 0.

168 A8 Label: RSNNDEL

Description: Not all requests to be deleted weredeleted.

A user interface routine issued a queue handlercommand to delete one or more file-transfer requestsfrom the request queue. However, at least one of thefile-transfer requests could not be deleted because:

� The file-transfer request was protected with apassword that was not specified with the queuehandler command.

� The file-transfer request was unsuccessfullyfinished and can only be deleted with theFORCEDEL command.

This reason code usually accompanies the return code0.

170 AA Label: RSNRSTBL

Description: Request available for restart processing.

An active file-transfer request was interrupted with theDELETE command. The status of the file-transferrequest is changed to finished . The file-transferrequest is available for restart.





172 AC Label: RSNSAACT

Description: Server already in server table.

A server tried to connect to the queue handler but aserver with the same job or started-task name wasalready in the queue handler’s server table. This isprobably because the server did not disconnect fromthe queue handler the last time it terminated. This canhappen when the operator cancels a server.

When the queue handler encounters this problem, itremoves the entry from the server table. When theserver is then started again, it should be able toconnect 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 canconnect to the queue handler has already beenreached. This number is specified in an initializationparameter for the queue handler.

180 B4 Label: RSNNDREQ

Description: No request available for processing.

A server tried to obtain a file-transfer request to processbut the queue handler could not find one available forprocessing.

184 B8 Label: RSNSVNFD

Description: Server name not found in server table.

A server issued a queue handler command but thequeue handler could not find an entry for that server inits server table. The queue handler did not carry outthe queue handler command. This code indicates aNetView FTP program error.

186 BA Label: RSNNOIL

Description: Incorrect type of NOTIFY queue handlercommand.

The server attempted to use a queue handler commandthat is not allowed for the request specified.

196 C4 Label: RSNFBASH

Description: More information retrieved than fits inbuffers.

A user interface routine queried one or more requests.The queue handler retrieved more information than fitsinto the buffers and there is still more information toobtain. If the application program interface issues thisreason code, the buffers provided by the applicationprogram are too small. If the batch job interface routineor the interactive interface routine issues this reasoncode, a NetView FTP program error has occurred.





200 C8 Label: RSNABEND

Description: Abnormal termination of queue handler.

The queue handler abnormally terminated whileprocessing a queue handler command. This probablyhappened because of a NetView FTP program error butcan also happen when the operator cancels the queuehandler.

204 CC Label: RSSRKSDS

Description: Incorrect KSDS option.

The server found an incorrect value for the KSDSOption parameter. Probably, the pre-transfer user-exitroutine modified the file-transfer request incorrectly.

Label: RSNRKSDS

Description: Incorrect VSAM KSDS option.

A user interface routine checked the file-transferrequest and found an incorrect value for the VSAMKSDS option. This code indicates a user error.

208 D0 Label: RSSRDEN

Description: Incorrect tape density.

The server found an incorrect value for the TapeDensity parameter. Probably, the pre-transfer user-exitroutine modified the file-transfer request incorrectly.

Label: RSNRDEN

Description: Incorrect tape density.

A user interface routine checked the file-transferrequest and found an incorrect value for the TapeDensity parameter. This code indicates a user error.

212 D4 Label: RSSREXPD

Description: Incorrect expiration date.

The server found an incorrect value for the ExpirationDate parameter. Probably, the pre-transfer user-exitroutine modified the file-transfer request incorrectly.

Label: RSNREXPD

Description: Incorrect expiration date or retentionperiod.

A user interface routine checked the file-transferrequest and found an incorrect value for the ExpirationDate or Retention Period parameter. This codeindicates a user error.

216 D8 Label: RSSVMLIN

Description: Incorrect VM link parameters.

The server found at least one of the following:

� An incorrect combination of VM link parameters� An incorrect value for a VM link parameter.

Probably, the pre-transfer user-exit routine modified thefile-transfer request incorrectly.

Label: RSNVMLIN

Description: Incorrect VM link parameters.

A user interface routine checked the file-transferrequest and found at least one of the following:

� An incorrect combination of VM link parameters

� An incorrect value for a VM link parameter.

220 DC Label: RSSVOLSE

Description: Missing volume serial number.

Specifying a volume serial number is mandatory for thisfile transfer, but the server found that a volume serialnumber was not specified. Probably the pre-transferuser-exit routine modified the file-transfer requestincorrectly.

Label: RSNVOLSE

Description: Missing volume serial number.

A user interface routine checked the file-transferrequest and found that a volume serial number wasrequired but missing.

This code indicates a user error.

224 E0 Label: RSSINCOM

Description: Incompatible transfer program at remotenode.

After a local server established an ACF/VTAM sessionwith a remote server, it discovered that the transferprogram at the remote node:

� Had an FTP level that was incompatible with itsFTP 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.





228 E4 Label: RSNNANBI

Description: Not-before or not-after time or dateincorrect.

A not-before or not-after time or date is incorrect.Possible reasons are:

� The not-after time and date is earlier than thenot-before time and date, or than the current timeand date

� The specified time or date was not valid (forexample, 25:00 or 32 December).

This indicates a user error.

Label: RSNNANBI

Description: Not-before or not-after time or dateincorrect.

A not-before or not-after time or date is incorrect.Possible reasons are:

� The not-after time and date is earlier than thenot-before time and date, or than the current timeand date

� The specified time or date was not valid (forexample, 25:00 or 32 December).

This indicates a user error.

230 E6 Label: RSNINRAC

Description: Incorrect security parameter specification.

The request contained an * that was incorrectlyspecified. Refer to the NetView FTP User’s Guide forinformation about how to specify values for securityparameters correctly.

248 F8 Label: RSSREJTR

Description: File-transfer request rejected bypre-transfer user-exit routine.

Before the file transfer starts, the server passes thefile-transfer request to the pre-transfer user-exit routine.This routine rejected the file-transfer request, that is, ittold 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 notfit into the I/O buffers. The receiving data set was notdefined to contain records that are as long as those thatwere sent.

260 104 Label: RSSUXNF

Description: Error while loading a user-written filehandler.

The file-transfer request indicated that NetView FTPwas to use a user-written file handler to gain access toa data set. The load module name for the file handlerwas specified in the file-transfer request, but the serverwas not able to load the routine. Possible reasons are:

� The load module name specified in the file-transferrequest was wrong

� The server did not have access to the correct loadlibraries.

264 108 Label: RSSCONTU

Description: The file-transfer request was rejectedbecause no connection was received by thedistribution-service machine from the file-servicemachine within 5 minutes after it was autologged.





302 12E Label: RSSLIO

Description: I/O error in data set.

While gaining access to a data set, a serverencountered a logical or physical I/O error. Possiblereasons are:

� The values of the parameters for the data set wereincorrect

� All extents of a data set were full� A device error occurred.

Label: RSNLIO

Description: I/O error while carrying out queue handlercommand.

The queue handler encountered an I/O error whilecarrying out a queue handler command. The commandwas not carried out. This might be due to a hardwareproblem.

303 12F Label: RSSADDK

Description: Error with KSDS option ADDKEY.

The file-transfer request specified the value ADDKEYfor the KSDS option, but a record that was to be writtento the receiving data set had the same key as a recordthat was already in the receiving data set, and thecontents of the two records were not the same. This isnot allowed with the value ADDKEY. The receivingserver broke off the file transfer.

304 130 Label: RSSCBM

Description: VSAM macroinstruction error.

The server uses the VSAM macros MODCB, TESTCB,and SHOWCB when working with VSAM control blocks.One of the macros returned an error. This is probably aNetView FTP program error.

Label: RSNCBM

Description: VSAM macroinstruction error.

The queue handler uses the VSAM macros SHOWCAT,MODCB, TESTCB, and SHOWCB when working withVSAM control blocks. One of the macros returned anerror. This is probably because the VSAM file does notexist or because of a NetView FTP program error.

305 131 Label: RSSOPN

Description: Error returned from OPEN or CLOSEmacro.

The server uses the OPEN macroinstruction to make adata set available for access during a file transfer, andthe CLOSE macroinstruction to end the access. One ofthe macros returned an error. If the error was returnedby:

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 mightnot be mounted.

Label: RSNOPN

Description: Error during OPEN or CLOSE.

The queue handler uses the OPEN macroinstruction tomake the request queue available for accessing, andthe CLOSE macroinstruction to finish the accessing.One of these macros returned an error.

306 132 Label: RSSSPMIS

Description: Security parameters missing. The serverthat processed the request requires one of thefollowing:

� Security parameters were specified in thefile-transfer request

� The server is able to retrieve security parametersautomatically (MVS).

Refer to message DVG159I for more information.





307 133 Label: RSSRACF

Description: RACF authorization error.

When the server attempted to open the sending orreceiving data set, using the specified or default securityparameter values, it encountered a system ABENDcode of 913. This indicates that the specified or defaultuser is not authorized to access the data set.

VM only: You do not have authorization to link thespecified minidisk. CP returns code 298.

308 134 Label: RSSRPNR

Description: RACF parameters cannot be retrieved.

The transfer program failed to retrieve the RACFpassword or group ID, or both, as specified in therequest. Check the return and reason code from theRACXTR macro for more information about the error.This can be found in the transfer report file or the serverlog file.

309 135 Label: RSSOPNE

Description: Nonexistent PDS member specified.

The server tried to make a single member available forfile transfer, but this member does not exist.

310 136 Label: RSSREPK

Description: Error with KSDS option REPKEY.

The file-transfer request specified the value REPKEYfor the KSDS Option parameter, but a record was to bewritten and another record with the same key did notalready exist in the receiving data set. This is notallowed with the value ADDBEG. The receiving serverbroke off the file transfer.

Label: RSNREPK

Description: Request not found on the request queue.

The queue handler tried to update a file-transferrequest on the request queue but could not find therequest. This code can indicate either a NetView FTPprogram error or incorrect installation of the requestqueue.

311 137 Label: RSSDSNR

Description: Error while retrieving a data-set name.

NetView FTP tried to retrieve the name of a data set tobe transferred from the job file control block, but theattempt failed. If NetView FTP was using dynamicallocation, this is probably due to a NetView FTPprogram error. If NetView FTP was using job allocation,this is probably due to a user error (the wrong ddnamewas probably specified in the file-transfer request).

Label: RSNDSNR

Description: Error while retrieving a data-set name.

NetView FTP tried to retrieve the name of a data setfrom the job file control block, but the attempt failed.This is probably due to missing disk-label informationfor the NetView FTP work file catalog.





312 138 Label: RSNLOGER

Description: Error with KSDS option ADDKEY orDELKEY.


� The file-transfer request specified the valueADDKEY for the KSDS option. A record with thesame key as one of the records being sent alreadyexisted in the receiving data set, but the tworecords were identical.

� The file-transfer request specified the valueDELKEY for the KSDS option, but none of therecords to be deleted existed in the receiving dataset.

These situations do not cause the file transfer to bebroken off, but because they are unusual and might beof interest to you, FTP V2 and NetView FTP issue thisreason code for your information. The file transfercontinues normally.

313 139 Label: RSSRALOC

Description: RACF allocation error.

NetView FTP attempted to dynamically allocate a dataset that has an RACF profile for which the user orNetView FTP are not authorized.

314 13A Label: RSSNOTX

Description: Nonexistent member specified in themember selection or exclusion list.

A PDS member that could not be found in the sendingPDS was selected or excluded.

315 13B Label: RSSPDSC

Description: PDS option in conflict.

A PDS option was specified that conflicts with thepresence, or absence of the member in the receivingPDS.

316 13C Label: RSSGVSER

Description: Error while requesting virtual storage.

The operating system did not satisfy the server’s oranother NetView FTP component’s request for a blockof 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, theGETVIS area was too small (VSE).

320 140 Label: RSSRVSER

Description: Error while releasing virtual storage.

The operating system did not satisfy the server’srequest to release a block of virtual storage. Probably,there was either a system error or a NetView FTPprogram error.





324 144 Label: RSSFCERR

Description: Error while retrieving attributes of thesending data set.

The server tried to retrieve the attributes of the sendingdata set so that they could be used when defining thereceiving 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 V2at that node informed the server at the local node aboutthe error. This reason code is issued for all thedifferent kinds of errors that can occur at an FTP V2node, because reason codes for specific errors are notsupported by FTP V2.

330 14A Label: RSSDELET

Description: File transfer interrupted by requestdeletion.

A user deleted a file-transfer request that correspondedto a file transfer that was in progress. The server brokeoff the file transfer.

Label: RSNDELET

Description: File transfer interrupted by requestdeletion.


334 14E Label: RSNFORCE

Description: File transfer interrupted by forced requestdeletion.


384 180 Label: RSSFTYP

Description:

� File type in DD statement and in request do notmatch.

Both a data-set type and a ddname were specifiedin the file-transfer request. The data-set typespecified in the DD, DLBL, or TLBL statement thatcorresponds to the ddname was different from thedata-set type specified in the file-transfer request.

� No data-set type was specified in the request andthe server could not retrieve the DSORG.

388 184 Label: RSSDCERR

Description: Error during definition of receiving VSAMcluster.

The receiving VSAM cluster could not be defined.Possible reasons are:

� The cluster had a cluster, data, or index name thatalready existed.

� Incorrect password or passwords were specified inthe file-transfer request.

� An incorrect catalog was specified in thefile-transfer request.

� Insufficient suballocation data space.� Insufficient space to allocate the cluster.





392 188 Label: RSSIPO

Description: Attributes of PDS not supported by BPAM.

The PDS being transferred has attributes that are notsupported by BPAM. Possible reasons are:

� Its record format is variable spanned (VS) orvariable blocked spanned (VBS).

� The attributes of the sending and receiving datasets are incompatible.

� There is more than one note list TTR for onemember.

� Two members have the same TTR but both arereal members.

396 18C Label: RSSTPO

Description: PDS transfer error.

A PDS could not be transferred, probably because it isdefined as being unmovable, that is, it has the data-settype 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 allocationwas done. The problem may be temporary. If it occursoften, notify your system programmer; it indicates apotential CSA space problem. The limiting factor indetermining the maximum additional CSA size for onerequest (the CSAELIM queue handler initializationparameter or the maximum request queue recordlength) might be too high.

If the error occurs when a user interface issues theADD queue handler command, the file-transfer requestis rejected. Submit the request again later.

If the error occurs when a server issues the OBTAINqueue handler command, the file-transfer request ismarked as being deferred. A server will try again laterto process the request.

408 198 Label: RSNQHSHD

Description: All servers are on hold.

All servers are on hold, so no request can beprocessed.





412 19C Label: RSNQHRTL

Description: CSA too small to accommodate RXB.

A server tried to obtain a request from the queue. TheRCB extension (RXB) needs more CSA storage than isavailable. The request is blocked.

Probably, the request was added to the queue at a timewhen more space was available. In the meantime, thequeue handler was stopped and later restarted, but withless CSA storage than before (the value for theCSAELIM initialization parameter was smaller thanbefore). The request is blocked, and cannot beprocessed until the queue handler is stopped andrestarted 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 selectionspecified.

A user interface checked the request and found thatboth a member list and the name of a single memberwere specified. Specify either one or the other andresubmit the request.

424 1A8 Label: RSNLDSNC

Description: Data set not found in catalog.

Because a volume was not specified in the file-transferrequest, a user interface routine tried to locate a dataset in the catalog. The return code from the CAMLISTmacroinstruction indicated that the data set could notbe found in the catalog.

Before you can transfer the data set, you must do oneof the following:

� Catalog the data set.� Specify the type of the data set.� Specify the volume on which the data set resides.





426 1AA Label: RSNLDSAC

Description: Data set already cataloged.

Before the file transfer was started, the receiving serverfound the name of the new data set already in thecatalog. The receiving data set was not allocated, thefile transfer did not take place.

Before you can transfer the data set, you must do oneof the following:

� Uncatalog the existing data set

� Delete the existing data set

� For NetView FTP V2.2 MVS, change in the requestthe value of the File Status option fromMUSTNOTEXIST to MUSTEXIST and the value ofthe End-of-Processing option for the successfulcase from CATLG to KEEP and check if you mustremove parameters not relevant for this disposition.

� For NetView FTP other than NetView FTP V2.2MVS, change the disposition parameter in therequest from CAT to OLD and check if you mustremove parameters not relevant for this disposition.

428 1AC Label: RSNODSNF

Description: Data set not found during retrieval ofDSCB information.

A user interface routine tried to obtain DSCBinformation for a data set. The volume containing thedata set was either pointed to by the catalog entry orspecified in the file-transfer request. The return codefrom the CAMLIST macroinstruction indicated that thevolume pointed to or specified does not contain thedata set.

432 1B0 Label: RSNVOLNM

Description: Volume not mounted.

A user interface routine tried to obtain DSCBinformation for a data set. The return code from theCAMLIST macroinstruction indicated that the catalogentry points to a volume that is not mounted. Ask theoperator to mount the volume.

436 1B4 Label: RSNLOCEC

Description: Error from CAMLIST while locating dataset.

Because a volume was not specified in the file-transferrequest, a user interface routine tried to locate a dataset in the catalog. However, the return code from theCAMLIST macroinstruction indicates that the data setcould not be found in the catalog.

440 1B8 Label: RSNOBTEC

Description: Error from CAMLIST while obtainingDSCB information.

A user interface routine tried to obtain DSCBinformation for a data set. However, the return codefrom the CAMLIST macroinstruction does not indicatethat the volume pointed to or specified does not containthe data set, or that the catalog entry points to avolume that is not mounted.





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 theLU name specified in the file-transfer request was notfound in the server group table. Because most usersrarely need to specify LU names other than thosecontained in the server group table, it is possible thatthe LU name specified is incorrect. If the LU namespecified 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 eachtime you specify it, have your system programmer addit to the server group table.

446 1BE Label: RSNLUMOD

Description: Correct LU running modes not found.

No LUs with the correct running mode (continuous orsingle) could be found for the server group specified.

448 1C0 Label: RSNAFFVS

Description: Remote node does not support VSAMcluster definition.

The interactive interface checked the server group tablefor information about the transfer program at the remotenode. It found that the transfer program at the remotenode is not capable of defining a new VSAM cluster.

452 1C4 Label: RSNAFFPO

Description: Remote node does not support PDSmember list processing.

The interactive interface checked the server group tablefor information about the transfer program at the remotenode. It found that the transfer program at the remotenode is not capable of processing a PDS member list.

456 1C8 Label: RSNRXBUS

Description: Not enough storage for parameters for auser-written file handler.

A file-transfer request specifies that a user-written filehandler is to be used. This request requires morestorage than is presently available. The problem is dueto one of the following:

� Not enough CSA storage is available to pass therequest to the queue handler

� The records of the request queue are too small toaccommodate the request.

Contact your system programmer.





460 1CC Label: RSNRXBVS

Description: Not enough storage for parameters usedfor VSAM cluster definition.

A file-transfer request contains parameters for thedefinition of a VSAM cluster. This request requiresmore storage than is presently available. The problemis due to one of the following:




464 1D0 Label: RSNRXBPO

Description: Not enough storage for a PDS memberlist.

A file-transfer request contains a list of PDS members.This request requires more storage than is presentlyavailable. The problem is due to one of the following:




468 1D4 Label: RSNMBRPO

Description: Too many PDS members specified.

The interactive interface routine detected that moremembers were selected or excluded than NetView FTPcan fit in one request. Instead of creating one request,create several.

472 1D8 Label: RSNGDGCO

Description: GDG model ID and user catalog IDspecified.

You can specify either a GDG model ID or a usercatalog ID.

476 1DC Label: RSNSVMOD

Description: Running mode of the server different tothe one specified in the request.

A file-transfer request specified the LU name of aserver. The running mode of that server does notmatch the running mode specified for that server in therequest.

480 1E0 Label: RSNRXBWT

Description: Incorrect APX type specified.

The application program interface routine checked thefile-transfer request and found an APX type other thanSELECT or EXCLUDE. Correct the APX type andresubmit the request.





484 1E4 Label: RSNMBRLN

Description: Member name or relative generationnumber too long.

The application program interface routine or batch jobinterface routine checked the request and found thatone of the following was more than 8 characters long:

� The name of a PDS member

� The relative generation number of a data set that isa 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 jobinterface routine checked the file-transfer request andfound that the name of a PDS member was specifiedboth as part of the data-set name and as the value ofthe Member Name parameter. Only one of thesespecifications is allowed.

496 1F0 Label: RSNRXBT

Description: Incompatible parameters specified.

The application program interface routine or batch jobinterface routine checked the file-transfer request andfound 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 andfound the MEMBER control statement, but no membername was specified.

504 1F8 Label: RSNMBRNO

Description: Parentheses found in data-set name butno member name or relative GDG specified.

The application program interface routine or batch jobinterface routine checked the file-transfer request andfound opening and closing parentheses in the data-setname, but the name of a PDS member or a relativeGDG was not specified. Either remove the parenthesesor add the name of the missing member or relativeGDG and resubmit the request.

508 1FC Label: RSNOPBRK

Description: Only opening parenthesis in data-setname.

The application program interface routine or batch jobinterface routine checked the file-transfer request andfound an opening parenthesis in the data-set name.Remove the parenthesis and resubmit the request.





512 200 Label: RSNCLBRK

Description: Only closing parenthesis in data-setname.

The application program interface routine or batch jobinterface routine checked the file-transfer request andfound 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 duringOBTAIN.

A user interface routine performed an OBTAIN on adata set and encountered a permanent I/O error. Askthe operator to check the volume and data set.

520 208 Label: RSNLOCMI

Description: LOCATE error; data set has beenmigrated.

The interactive interface could not locate the data setspecified in the request because the data set wasmigrated. Have HSM recall the data set, then submitthe request again.

524 20C Label: RSNATLST

Description: User lost authorization to modify thisrequest.

A user’s attempt to modify a request failed becauseeither the administrator or the operator already modifiedit. After the administrator or the operator modifies arequest, only they can modify it further.

528 210 Label: RSNSVHLD

Description: Server set to hold.

The operator has set the server to hold. It cannotprocess any requests.

532 214 Label: RSNOBTUD

Description: Error encountered during OBTAIN;unsupported data-set type.

A user interface routine automatically retrieved the typeof a data set. The data set is of a type not supportedby NetView FTP, that is, does not have the type VSAM,PO, PS, LAB, or UNLAB. Ask your system supportpersonnel to check the data set.

536 218 Label: RSNAPXEN

Description: No APX entries specified.

The application program interface routine checked thefile-transfer request and found that the user supplied anAPX but did not specify any entries in the APXENTfield. Specify a value for APXENT and submit therequest again.

540 21C Label: RSNHSMAL

Description: Failed allocation.

During a recall of a migrated data set, the allocationfailed.





544 220 Label: RSNHSMDE

Description: Failed deallocation.

During a recall of a migrated data set, the deallocationfailed.

548 224 Label: RSNUNTPN

Description: Transaction program name not supported.

A remote program tried to establish a conversation withNetView FTP but used a transaction program name thatis not supported by NetView FTP.

550 226 Label: RSNPVERR

Description: The server has encountered anACF/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 thepost-transfer user-exit routine.

552 228 Label: RSNRXBSE

Description: The RXB cannot be processed becausenot enough space is available.

Possible reasons are:

� The maximum record size defined for the requestqueue is too small

� MVS only: the maximum size of CSA spacedefined for NetView FTP is too small or is notavailable.

For more information, refer to the appropriateInstallation, Operations, and Administration Guide.

553 229 Label: RSNJOERR

Description: Error during post-transfer job submission.

During processing of the post-transfer job submission, aserver encountered an error. The problem may be dueto one of the following:

� An error occurred during the dynamic allocation ofthe data set containing the job

� An I/O error occurred while the transfer programwas processing the job submission via QSAM

� The specified job library data set or the membercould not be found

� The data set containing the post-transfer job is notpartitioned organized.

554 22A Label: RSNSYSEX

Description: The server cannot continue processingdue to a system problem.

555 22B Label: RSNDPKWD

Description: A keyword that can only be specified oncehas been specified more than once.

556 22C Label: RSNEXOJ

Description: An object (file or member) already exists.





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 itis already in use.

560 230 Label: RSNUNSFC

Description: A function is not supported by the localtransfer program.

561 231 Label: RSNNACFC

Description: A function is not active at the remotetransfer program.

562 232 Label: RSNNOPFC

Description: A function is not operational at the remotetransfer program.

563 233 Label: RSNPRTER

Description: A protocol violation has been detected.

The local transfer program detected a violation of therules described in the file-transfer protocol. Theviolation has been caused by the partner transferprogram. A dump of the Error Message Unit sent to theremote file transfer program is taken.


564 234 Label: RSNCRYLB

Description: The specified encryption label is notknown to PCF. Correct and resubmit the request.

565 235 Label: RSNCRYNA

Description: PCF is not active. Start PCF andresubmit the request.





566 236 Label: RSNCRYER

Description: PCF returned a serious error. Thefollowing 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-dayclock was inoperative

� Internal PCF error during key translation(RETKEY macro).

2. At the receiving location:

� The server program was either not APFauthorized, not in supervisor state, or notunder 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 MVSProgrammed Cryptographic Facility: InstallationReference (GENKEY, RETKEY, and CIPHER macrodescription).

567 236 Label: RSNTEMP

Description: A temporary problem occurred duringprocessing of a file-transfer request.

If the request originator allowed requeuing of therequest, the request is scheduled again later.

Additional information about the problem can be foundin the server’s log and the report data set.

568 237 Label: RSNPERM

Description: A permanent problem occurred duringprocessing of a file-transfer request.

The transfer request will not be scheduled again, nomatter what the request originator specified.

Additional information about the problem can be foundin the server’s log and the report data set.

569 239 Label: RSNAPSEC

Description: The remote server did not accept theAPPC 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 functionrequest.

The requested function is valid for an SNA request, butnot for an OSI request.

591 24F Label: RSNINMBR

Description: You specified a receiving member namebut did not specify the corresponding file ID.





592 250 Label: RSNREQUE

Description: A post-conversation user exit routineforced the status of the request to WAITING. Bothnot-before and not-after date and time may have beenchanged by the exit routine. If the your exit routineprovided a message, this message can be found in thetransfer report file and in the server’s log file. The newstatus of the file-transfer request is WAITING.

602 25A Label: RSNTCTRM

Description: Access Authorization already held by aNetView FTP VSE subtask.

This reason code is defined for internal purposes onlyand does not appear during normal processing.

603 25B Label: RSNENABD

Description: Access Authorization already enabled foranother VSE SV subtask.

604 25C Label: RSNNASPP

Description: Security parameters have been specifiedbut could not be verified. Refer to message DVG154Ifor more information.

605 25D Label: RSNNAFTP

Description: Security parameters were not specifiedand NetView FTP does not have authorization toaccess the file. Refer to message DVG155I for moreinformation.

606 25E Label: RSNNAUSR

Description: Security parameters were specified butthe specified user ID does not have authorization toaccess the file. Refer to message DVG155I for moreinformation.

607 25F Label: RSNUPWLN

Description: Security parameters were specified butthe specified user ID or password is the wrong length.Refer to message DVG150I and DVG151I for moreinformation.

609 261 Label: RSNGRPSP

Description: The security parameter Group ID wasspecified but is ignored by a VSE system. Refer tomessage DVG152I for more information.

610 262 Label: RSNNOAUT

Description: Error during validation of access controluser ID and password. Refer to message DVG149I formore information.

611 263 Label: RSNDINOE

Description: Request to free access authorization butaccess authorization is not yet held by NetView FTPVSE subtask.


612 264 Label: RSNSUBNO

Description: SUBSID/NOTIFY failed.





613 265 Label: RSNCPCOM

Description: Operator message output via CPCOMmacro failed.

614 266 Label: RSNATT

Description: Attach of subtask failed.

615 267 Label: RSNCDLD

Description: The CDLOAD macro indicated an errorwhen loading the module. Refer to message DVG638Ifor more information.

Label: RSNCDLD

Description: The CDLOAD macro indicated an errorwhen loading the module. Refer to message DVG638Ifor more information.

618 26A Label: RSNCPLD

Description: The load of the parser module failed.This module is an essential module for the NetViewFTP partition.

619 26B Label: RSNIPERR

Description: NetView FTP initialization parameter error.

During initialization of the NetView FTP partition asyntactical or logical error was detected with theinitialization parameters for the NetView FTP partition orservers. The initialization stopped.

620 26C Label: RSNTDFER

Description: Tape definition table error.

During initialization of the NetView FTP partition asevere error occurred when loading the tape definitiontable (DVGTDF). The initialization stopped.

622 26E Label: RSNRQCAR

Description: Error in request queue characteristics wasfound during initialization of the queue handler. Theinitialization stops. The NetView FTP administratormust analyze the problem and may need to redefine therequest queue.

623 26F Label: RSNUIBPN

Description: Report transmission needs VSE/POWERPNET 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 setcould not be found.

Processing stops. Your system administrator mustanalyze the problem.





629 275 Label: RSNRQDLK

Description: Error defining a lock for the requestqueue.

630 276 Label: RSNRQULK

Description: Error in unlocking the request queue.Processing stops. Your system administrator mustanalyze the problem.

631 277 Label: RSNITAIU

Description: Requested tape unit currently in use.

632 278 Label: RSNITANA

Description: Requested tape unit not available. Checkthat your Tape Definition Table corresponds to yourhardware environment. Refer to NetView FTP VSEInstallation, Operation, and Administration for moreinformation.

633 279 Label: RSNITAD1

Description: Tape device type, density and tracknumber, mismatch. Check that your Tape DefinitionTable corresponds to your hardware environment.Refer to NetView FTP VSE Installation, Operation, andAdministration for more information.

634 27A Label: RSNITAD2

Description: Tape device type TAPE unlabeled butdensity 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, densitymismatch.

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 onerequest number, between one and maximum requestnumber, 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 requestbut active requests cannot be deleted by users oradministrators at VSE systems.





642 282 Label: RSNNCLP

Description: Because another NetView FTP partition isactive or a NetView FTP user interface is updating therequest queue, no clean-up of the request queue takesplace during the startup of the NetView FTP partition.

643 283 Label: RSNICON

Description: A request found via the alternate key isdifferent from the request found via the primary key.Your NetView FTP request queue administrator mustanalyze the problem.

644 284 Label: RSNRLERR

Description: Request status fields in conflict due to alogic error. Processing stops. Your NetView FTPrequest queue administrator must analyze the problem.

645 285 Label: RSNDLNTA

Description: Dynamic allocation not active for thisserver task but a request for deallocation has beenreceived.


646 286 Label: RSNTMCNC

Description: Operator has canceled transfer of a tapefile.

647 287 Label: RSNTMREQ

Description: Operator has requeued the transfer of atape file.

648 288 Label: RSNDLALA

Description: Dynamic allocation is already active forthis server task.

649 289 Label: RSNNDTE

Description: At least one invalid record found in theserver group table during initialization of NetView FTP.The initialization stops. Your NetView FTP requestqueue administrator must analyze the problem andredefine the server group table.

650 28A Label: RSNTSKNR

Description: A task asked for a service from anothertask but the posted task was not ready.


651 28B Label: RSNLRSRG

Description: SAM ESDS logical record size out ofrange. (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 aSAM ESDS with a record format that was not FB.





654 28E Label: RSNSAM

Description: SAM ESDS was specified for a non-VSEsystem.

655 28F Label: RSNSAMRF

Description: A record format was specified for anindexed 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 possibleat an unattended node. Refer to message DVG648I formore information.

700 2BC Label: RSNOPNLG

Description: An error occurred while opening the logfile.

701 2BD Label: RSNIOELQ

Description: An I/O error occurred for the log file.

702 2BE Label: RSNNOCON

Description: No connection occurred during a constantwait time.

703 2BF Label: RSNVASER

Description: The APPC/VM interface routine indicateda SENDERR (communication partner issuedAPPCVM/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 nolonger 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 theDVGAS NAMES file.

713 2C9 Label: RSNVASHT

Description: Receive area shortage.





714 2CA Label: RSNVAUNX

Description: Program logic error during communicationprocessing.

715 2CB Label: RSNVARTS

Description: SENDDATA is not valid from the receivingsystem.

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. Operatorcanceled request.

719 2CF Label: RSNNODEV

Description: Device is not a DASD, no device found, orSFS 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 receivinga connect from the queue handler.

723 2D3 Label: RSNOLDIS

Description: RTDISP=OLD orRSTATOPT=MUSTEXIST specified but file does notexist.

724 2D4 Label: RSNEWDIS

Description: RTDISP=NEW orRSTATOPT=MUSTNOTEXIST specified but file alreadyexists.

725 2D5 Label: RSNINVAC

Description: Insufficient access mode. Receiving diskmust 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 enoughspace for RXB on request queue.

728 2D8 Label: RSNUSRXB

Description: RXB contains sections not supported byVM or VSE.

730 2DA Label: RSNSUBDI

Description: SFS subdirectory parameters must befilled in contiguously.

Label: RSNSUBDI

Description: SFS subdirectory parameters must befilled in contiguously.





731 2DB Label: RSNAPXNV

Description: Existing APX is not allowed for VM orVSE.

732 2DC Label: RSNTAREQ

Description: The operator requeued the request.Either, because the tape is temporarily not available, orbecause the tape unit is currently not available.

733 2DD Label: RSNTACAN

Description: The operator canceled a tape mountrequest. This may be because the required tape doesnot exist, or because you are not authorized to use thetape.

734 2DE Label: RSNVAMRJ

Description: An IUCV message was sent and rejectedby the communications partner.

735 2DF Label: RSNMIFTY

Description: The file type must be specified if thesending system is the remote system.

Label: RSNMIFTY

Description: The file type must be specified if thesending system is the remote system.

736 2E0 Label: RSNTPLAB

Description: One of the following occurred:

� 'xFTYPE=LAB' was requested and an unlabeledtape was loaded

� 'xFILEORG=PS' and 'xLABEL=SL' were requestedand an unlabeled tape was loaded

� 'xFTYPE=UNLAB' was requested and a labeledtape was loaded

� 'xFILEORG=PS' and 'xLABEL=NL' were requestedand 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 unlabeledtape.

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.





1000 3E8 Label: None

Description: This reason code is issued when theremote system does not issue reason codes. Forexample, if a request to a remote NetView FTP/400system is rejected, the remote system issues returncode 16; but no reason code. NetView FTP sets thereason code in the server log to 1000.

Label: None

Description: Queue handler command rejected bypre-queuing user-exit routine; incorrect reason codepassed to NetView FTP.

The pre-queuing user-exit routine rejected the queuehandler command but passed an incorrect reason codeto NetView FTP. NetView FTP set the reason code to1000. There is probably an error in the pre-queuinguser-exit routine.

1nnn Label: None

Description: Error occurred on remote server.

The local server was informed by the remote server thatan error occurred at the remote system The reasoncode for the error at the remote system is representedby the number nnn , which is one of the other reasoncodes in this table.

Label: None

Description: Queue handler command rejected bypre-queuing user-exit routine.

The pre-queuing user-exit routine rejected the queuehandler command and passed the code nnn to NetViewFTP.

2000 7D0 Label: RSOSNOSI

Description: The RCE control block is not marked validfor an OSI request (the field RCESVTA has not beenset). It is possible that an SNA file-transfer request hasbeen sent to the OSI server.

2001 7D1 Label: RSOSSNAV

Description: The RXB control block that is passed tothe OSI server does not contain an OSI section. It ispossible that an SNA file-transfer request has been sentto the OSI server.

3000 668 Label: RSOSURAC

Description: SAF permission for user violated.

You do not have sufficient SAF authority to process thespecified file-transfer request. Contact your SAFsystem administrator.

3010 6C2 Label: RSOSORAC

Description: SAF permission for OSI/File Servicesviolated.

Either the OSI server or OSI/File Services do not havesufficient authority to process the file-transfer request.Contact your SAF system administrator.

3020 6CC Label: RSOSUCAP

Description: You are not allowed to perform thetransfer on the specified filestore because the capabilityof the filestore does not match that of the request. Therequest demands more capability than the filestore canprovide. Contact your system administrator.

3030 6D6 Label: RSOSUFAC

Description: You are not allowed to perform thetransfer on the specified filestore because of the valuespecified by the filestore access parameter that isconfigured in the local resource directory. Contact yoursystem administrator.





3032 6D8 Label: RSOSMFLE

Description: File entry missing and cannot be added.

The local resource directory entry for the specified file isnot recorded in the local resource directory and cannotbe temporarily entered by the OSI server.

3100 C1C Label: RSOSACCP

Description: The access control specified is notsufficient for COPY.

The access control action elements do not allowsufficient access rights to perform the read or readattributes transfer actions for the COPY function.Refer to OSI/File Services for MVS Programming Guidefor further details.

3110 C26 Label: RSOSACMV

Description: The access control specified is notsufficient for MOVE.

The specified access-control-action elements do notallow sufficient access rights to perform read , readattributes , or delete transfer actions for the MOVEfunction. Refer to OSI/File Services for MVSProgramming Guide for further details.

3120 C30 Label: RSOSSTMS

Description: The contents of the String Significanceand Maximum String Length parameters do not match.Refer to OSI/File Services for MVS Programming Guidefor further details.

3130 C3A Label: RSOSDOCT

Description: The value specified for the DocumentType parameter is incorrect.

3140 C44 Label: RSOSMSTR

Description: The value specified for the MaximumString Length parameter is incorrect.

3150 C4E Label: RSOSSSIG

Description: The value specified for the StringSignificance parameter is incorrect.

3160 C58 Label: RSOSUCLA

Description: The value specified for the UniversalClass parameter is incorrect.

4100 1004 Label: RSOSCANR

Description: The cancel request cannot be performedbecause of the internal status of the request.

4832 12E0 Label: RSOSDTUC

Description: The contents of the Document Type andUniversal Class parameters do not match. Refer toOSI/File Services for MVS Programming Guide forfurther details.

4846 12EE Label: RSOSPAMM

Description: The Permitted Actions and Access Controlparameters do not match.

5010 1392 Label: RSODSNA

Description: The requested file is not available.





5100 13EE Label: RSOSRNOF

Description: The action on the request failed becauseit is not available in OSI/File Services.

5200 1450 Label: RSOSRTRM

Description: The request has already terminated andcannot be canceled.


Glossary

This glossary defines many of the terms and abbreviationsused with NetView FTP. If you do not find the term you arelooking for, refer to the Dictionary of Computing, New York:McGraw-Hill, 1994.

Access Method Services . A utility program that definesVSAM data sets and allocates space for them, convertsindexed sequential data sets to key-sequenced data setswith indexes, modifies data set attributes in the catalog,facilitates data set portability between operating systems,creates backup copies of data sets and indexes, helps makeinaccessible data sets accessible, and lists data set recordsand catalog entries.

ACF/VTAM . Advanced Communications Function for theVirtual Telecommunications Access Method.

active request . A request that is presently being scheduledor for which the corresponding file transfer is in progress.

adaptive compression . A method by which the amount ofstorage required for data can be reduced by replacingcharacter strings that are repeated with references to adirectory of such character strings.

added request . A request that has been added to therequest queue.

administrator query command . A type of command thatcauses NetView FTP to retrieve information about therequest queue or the requests in it; the information retrievedis intended for the NetView FTP administrator. Contrast withuser query command.

administrator query record . A record containing theinformation NetView FTP retrieves when an administratorissues an administrator query command. Contrast with userquery record.

adopted authority . When a program is created, it canspecify that the program always runs under the programowner’s user profile. A user does not need authorityspecifically given to him for the objects used by the program,but uses (adopts) the program owner’s authority. The userhas authority for the objects used by the program only whenhe is running the program and other programs called by theprogram.

Advanced Communications Function for the VirtualTelecommunications Access Method . An IBM licensedprogram that controls communication and the flow of data inan SNA network. It provides single-domain, multiple-domain,and interconnected network capability. VTAM runs underMVS, VSE, and VM/SP, and supports direct controlapplication programs and subsystems such as NetView FTPand VSE/POWER.

Advanced Function Feature . A set of extra functions thatextend the capabilities of the NetView FTP V1 MVS baseproduct.

advanced peer-to-peer networking . Data communicationssupport that routes data in a network between two or moreAPPC systems that are not directly attached.

advanced program-to-program communication . Animplementation of the SNA/SDLC LU 6.2 protocol that allowsinterconnected systems to communicate and share theprocessing of programs.

AET. Application Entity Title.

AFF. Advanced Function Feature.

alias . An alternative name for a member of a partitioneddata set.

AMS. Access Method Services.

APAR . Authorized program analysis report.

APF. Authorized Program Facility.

APL . Application program parameter list.

APPC. Advanced program-to-program communication.

Application Entity Title . The name by which an OSIapplication (and filestore) can be addressed by remote users.By contrast, the local name of the filestore is the filestorenickname.

application program parameter list . A control block usedby application programs to pass parameter values toNetView FTP.

application program parameter list extension . A controlblock used by application programs to pass parameter valuesto NetView FTP; a supplement to the application programparameter list.

APPN. Advanced peer-to-peer networking.

APX. Application program parameter list extension.

attended mode . An operating mode of NetView FTP forWorkstations that assumes that a user at a workstationexpects to be informed about the success of transfers and isavailable to load devices such as diskettes or tapes.Contrast with unattended mode.

automatic logon retry . NetView FTP’s method foreventually establishing a conversation with a remote system.It is used when a server cannot initiate a conversation with aserver at a remote system because:


� All the servers at the remote system are busy with othertransfers

� None of the servers at the remote system has beenstarted

� ACF/VTAM is temporarily unable to find a path betweenthe two servers.

The server at the local system automatically changes thestatus of the request from active back to waiting , and goeson to process the next request in the request queue (MVS,VSE, or VM) or request database (OS/400). Later, NetViewFTP tries again to process the request. It keeps trying until itsucceeds in initiating a conversation.

automatic transfer restart . NetView FTP’s method forautomatically restarting a file transfer that was interrupted. Inthe following situations, NetView FTP is not able to recover aconversation:

� The queue handler or server at either system isterminated

� The server at either system cannot allocate the file beingtransferred

� A pre-transfer user-exit routine at either system rejectedthe file transfer

� There is a severe or prolonged conversation outage.

However, when you create a request you can specify that ifone of these situations arises, NetView FTP is to change thestatus of the request back to waiting . The servers at yoursystem then periodically reprocess the request until one ofthem succeeds in restarting the transfer.

basic partitioned access method . An access method thatcan be used to create program libraries in direct-accessstorage for convenient storage and retrieval of programs.

basic sequential access method . An access method forstoring or retrieving data blocks in a continuous sequence,using either a sequential access or a direct access storagedevice.

BIND. Bind Session.

Bind Session . In SNA, a request to activate a sessionbetween two logical units.

blocked request . A waiting request that is trapped in thequeue. The request was passed to the queue handler at atime when there was enough CSA storage available toNetView FTP to do so. However, in the meantime, the limitof the amount of CSA storage available to NetView FTP wasreduced and is not enough to allow the queue handler topass the request to a server for processing. The requestcannot be processed until the limit of the amount of CSAstorage available to NetView FTP is raised.

BPAM . Basic partitioned access method.

BSAM . Basic sequential access method.

callback . In the AIX operating system, a procedure that iscalled if and when certain specified conditions are met. Thisis accomplished by specifying the procedure in a callbacklist.

callback list . (1) A list of procedures that are called if andwhen certain specified conditions are met. (2) In theprogram IBM AIXwindows Environment/6000, individualwidgets can define callback lists.

CCB. Command control block.

CCI. Common control block insertion.

CCSID. Coded character set identifier.

CCW. Channel command word.

CDC. Character data conversion.

CDRA. Character Data Representation Architecture.

CDRM. Cross-domain resource manager.

CDRS. Cross-domain resource.

character data . Data in the form of letters, numbers, andspecial characters, such as punctuation marks, that can beread by the human eye.

Character Data Representation Architecture . An IBMarchitecture that defines a set of identifiers, services,supporting resources, and conventions to achieve aconsistent representation, processing, and interchange ofgraphic character data in SAA environments.

character literal . A symbol, quantity, or constant in asource program that is itself data, rather than a reference todata.

checkpoint . A point at which information about the status ofa file transfer is recorded. If the file transfer is interrupted,NetView FTP can use this information to resume the filetransfer from a point near where the interruption occurredinstead of from the beginning of the file.

checkpoint data set . A data set that contains informationabout the current status of an active file transfer. If the filetransfer is interrupted, NetView FTP can use this informationto resume the file transfer from a point near where theinterruption occurred instead of from the beginning of the file.

checkpoint file . A synonym for checkpoint data set.

checkpoint record . A record of a checkpoint data set orfile. One checkpoint record contains the information neededto restart one file transfer from a checkpoint.

checkpoint/restart data set . A deprecated term forcheckpoint data set.

checkpoint/restart record . A deprecated term forcheckpoint record.


class . See server class.

client . On a local area network, a workstation that requestsservice from a server workstation.

CLIST. Command list.

Coded character set identifier . In NetView FTP, anidentifier that represents a set of graphic characters and theircode point assignment. The coded character set identifierdefines how characters are mapped to decimal values.

command control block . A control block that containsdetails of the queue handler command to be carried out.

command list . A list of commands and control statementsthat is assigned a name. When the name is invoked (as acommand) the commands in the list are executed.

common service area . In MVS, a part of the common areathat contains data areas that are addressable by all addressspaces. During use, these areas are protected by the key ofthe requester.

completion user exit . Deprecated term for post-transferuser exit.

compression . A technique for converting data into a formthat requires less storage space and less transmission timethan its original form. Contrast with decompression. Seealso SNA compaction and SNA compression.

condition code . A 4-digit decimal value derived from thevalue a server places in register 15 before returning controlto the operating system. The digits of the condition codeconsist of the server return code and, for a server running insingle mode, the file-transfer return code.

continuous mode . A server running mode in which aserver continues running after it has transferred a file.

control language . The set of all commands with which auser requests system functions.

control point . A component of an APPN or LEN node thatmanages the resources of that node. In an APPN node, theCP is capable of engaging in CP-CP sessions with otherAPPN nodes. In an APPN network node, the CP alsoprovides services to adjacent end nodes in the APPNnetwork.

control statement . A statement that controls or affects therunning of a program. For example,NOTAFTER=(‘21:34’,‘94/12/25’) is a control statement thatassigns the value (‘21:34’,‘94/12/25’) to the parameterrepresented by the keyword NOTAFTER.

conversation . In SNA, a connection between twotransaction programs over an LU-LU session that lets themcommunicate with each other while processing a transaction.

CP. Control point.

CP-CP sessions . The parallel sessions between twocontrol points, using LU 6.2 protocols.

Cross-domain resource . In VTAM programs, synonym forother-domain resource.

Cross-domain resource manager . The functions of thesystem services control point (SSCP) that control initiationand termination of cross-domain resources.

cryptographic key . A value used to encrypt and decryptdata transmitted in an LU-LU session that uses cryptography.

cryptography . The transformation of data to conceal itsmeaning.

CSA. Common service area.

current request . The request currently being created orchanged by the user of the NetView FTP panels.

daemon . In the AIX operating system, a program that runsunattended to perform a standard service.

daemon process . In the AIX operating system, a processbegun by the root user or the root shell that can be stoppedonly by the root user. Daemon processes generally provideservices that must be available at all times.

DASD. Direct-access storage device.

data control block parameters . The following parameters:Record Format, Logical Record Length, and Physical BlockSize.

data set control block . A control block containingspecifications for data sets that are to be created.

data transfer message unit . The message unit used tosend the data object.

DCB parameters . Data control block parameters.

decompression . A technique for converting compresseddata back into its original form. Contrast with compression.

default first qualifier . Server initialization parameter.Sometimes referred to as the GID initialization parameter.The server uses this parameter as the first qualifier when itcreates a name for the data set.

default value . The value that is assigned to a parameter bya program if no value is specified by a user.

deferred request . A waiting request that is temporarilytrapped in the queue. CSA storage was obtained forNetView FTP, but not enough for the queue handler to passthe request to a server for processing. The request isprocessed later, when more CSA storage is available toNetView FTP.

Glossary 149

delay time . The amount of time a finished request stays inthe request queue before rebuilding the request queuecauses it to be deleted automatically.

direct transfer . Transfer of data from one file to another filewithout first storing the data in an intermediate file.

direct-access storage device . A storage device for whichaccess time is effectively independent of the location of thedata being accessed.

directory file . In the AIX operating system, a file thatcontains information the system needs to access all types offiles.

distribution-service component . A component of NetViewFTP VM that handles communication with the queue handler(such as retrieving requests to be processed), and with thenetwork (such as establishing conversations and transferringfiles). In NetView FTP VM, each server consists of onedistribution-service component and up to 32 file-servicecomponents.

distribution-service machine . With NetView FTP VM, avirtual machine in which a distribution-service componentruns.

DSCB. Data set control block.

DTMU. Data transfer message unit.

dynamic allocation . The allocation of a file when it isneeded, not in advance. Contrast with job allocation.

encrypt . To scramble data or convert data to a secret codethat masks the meaning of the data to any unauthorizedrecipient.

entry sequence . The order in which records are physicallyarranged in auxiliary storage.

entry-sequenced data set . A data set whose records areloaded without respect to their contents, and whose relativebyte addresses cannot change.

ESDS. Entry-sequenced data set.

ESTAE. Extended specify task abnormal exit.

exceptional checkpointing . To take a checkpoint whencertain types of errors occur.

exchange identification . The ID that is exchanged with theremote physical unit when an attachment is first established.

exclude members . To choose those members of a PDSthat are not to be transferred. Contrast with select members.

exit . A point in a program at which control is passed toanother program.

exit routine . A routine that receives control when aspecified event occurs.

Exit(n) Message Unit . The message unit used to conveyinformation provided by the Post-Transfer User Exit routine n(where n is 1 or 2) of the sender to the receiver.

extended specify task abnormal exit . A macroinstructionthat allows a user to intercept a scheduled abnormaltermination.

FAT. File allocation table.

FBA . Feedback area.

feedback area . An area of storage containing informationrelated to a queue handler command. For example, an FBAcan contain a request control block, a query data area, or aserver data area.

file allocation table . A table used by DOS and OS/2 toallocate space on a disk for a file and to locate and chaintogether parts of the file that may be scattered on differentsectors so that the file can be used in a random orsequential manner.

file group . One or more files that reside on one system.For example, all files that are stored in the same directory orwhose file names consist of partly matching character stringsare considered a file group.

file pool . A collection of minidisks managed by SFS. Itcontains user files and directories and associated controlinformation. Many user’s files and directories can becontained in a single file pool.

file transfer . The sending and receiving of the contents of afile.

File Transfer Access and Management . A set ofprograms, such as OSI/File Services, which conforms toFTAM standards to manage and transfer files over an OSInetwork.

file-service component . A component of NetView FTP VMthat handles file access and the taking of checkpoints. InNetView FTP VM, each server consists of onedistribution-service component and up to 32 file-servicecomponents.

file-transfer completion message . A message, sent by aserver to a user after a file transfer, which describes theoutcome of a file transfer.

file-transfer report . A file, sent by a server to a user after afile transfer which describes the outcome of a file transfer.

file-transfer request . A list of parameters and their valuesthat tell NetView FTP (1) that it is to transfer a file from onesystem to another, and (2) about the file transfer and thesending and receiving data sets.

filestore . See local filestore and remote filestore.


filestore nickname . The name of the filestore at the locallevel. It is defined by the filestore owner when registeringthe filestore in the LRD, and is used by authorized localusers to access that filestore.

filestore owner . The single user, local or remote, who hascreated the filestore and who controls the passwords foraccessing it and the filestore accessibility. Each OSI/FileServices user owns one filestore.

filestore subset . A subdivision of the local filestore. It isthe first qualifier of the MVS data-set name. Each local file isregistered in the LRD under a related filestore subset, whichin turn belongs to a local filestore.

filter . In the AIX operating system, a command that readsstandard input data, modifies the data, and sends it to thedisplay screen.

finished request . A request for which the corresponding filetransfer has finished, whether successfully or unsuccessfully.

FIU. File Interchange Unit.

FTAM. File Transfer Access and Management.

FTP level . A character that represents the level ofsophistication of an FTP or NetView FTP program.

FTP V2. File Transfer Program Version 2 Release 2.

FSB. NetView FTP shared block.

FSBX. NetView FTP shared block extension.

GDG. Generation data group.

generation data group . A collection of data sets kept inchronological order; each data set is a generation data set.

generation data set . One generation of a generation datagroup.

GETVIS area. Storage space within a partition or theshared virtual area, available for dynamic allocation toprograms.

GID initialization parameter . See default first qualifier.

GUI. The graphical user interface of NetView FTP forWorkstations.

handle . (1) In the Advanced DOS and OS/2 operatingsystems, a binary value created by the system that identifiesa drive, directory, and a file so that the file can be found andopened. (2) In the AIX operating system, a data structurethat is a temporary local identifier for an object.

HDAM. Hierarchic direct access method.

hex . Abbreviation of hexadecimal.

hierarchic direct access method . A database accessmethod that uses algorithmic addressability of records in ahierarchic direct organization.

hierarchic indexed sequential access method . Adatabase access method that uses indexed access torecords in a hierarchic sequential organization.

High Performance File System . A file organizationavailable under OS/2.

HISAM. Hierarchic Indexed Sequential Access Method.

HPFS. High Performance File System.

ICCF. Interactive computing and control facility.

ICF. Intersystem communications function.

IMS/VS. Information Management System/Virtual Storage.

independent LU . A logical unit (LU) that does not receivean ACTLU over a link. Such LUs can act as primary logicalunits (PLUs) or secondary logical units (SLUs) and can haveone or more LU-LU sessions at a time.

INI file . See initialization file.

initialization file . A file that contains parameters thatdetermine how NetView FTP for Workstations starts running.

input field . An area on a panel in which data is entered.

instance . In the AIX operating system, the concreterealization of an abstract object class. An instance of awidget or gadget is a specific data structure that containsdetailed appearance and behavioral information that is usedto generate a specific graphical object on-screen at run time.

Internet . A wide area network connecting thousands ofdisparate networks in industry, education, government, andresearch. The Internet network uses /IP as the standard fortransmitting information.

Internet Protocol . A protocol used to route data from itssource to its destination in an Internet environment.

Intersystem communications function . Communicationsbetween application programs on an AS/400 system and anapplication program on a remote system are accomplishedusing the AS/400 system intersystem communicationsfunction (ICF) and the underlying support.

IP. Internet Protocol.

ISPF. Interactive System Productivity Facility.

JCL . Job control language.

JES. Job entry subsystem.

job allocation . The allocation of a file by a server startupjob. The allocation takes place when a server is started,

Glossary 151

which is before (sometimes long before) the file transfertakes place. Contrast with dynamic allocation.

job control language . A control language used to identify ajob to an operating system and to describe the job’srequirements.

key sequence . In VSAM, the collating sequence of datarecords as determined by the value of the key field in eachrecord.

key-sequenced data set . A VSAM data set whose recordsare loaded in key sequence and controlled by an index.

keyword . A part of a control statement that consists of aspecific character string.

KSDS. Key-sequenced data set.

LAN . Local area network.

LAN gateway . A functional unit that connects a local areanetwork with another network using different protocols.

LDS. Linear data set.

LEN node . Low-entry networking node. That is a node thatprovides a range of end-user services, attaches directly toother nodes using peer protocols, and derives networkservices implicitly from an adjacent APPN network node, thatis, without the direct use of CP-CP sessions.

linear data set . A VSAM data set that contains data but nocontrol information. A linear data set can be accessed as abyte-string in virtual storage. A linear data set has norecords and a fixed control interval size of 4096 bytes.

local . Refers to one’s own system.

local area network . A data network located on the user'spremises in which serial transmission is used for direct datacommunication among workstations.

local filestore . A collection of local files. Each localfilestore is registered in the LRD with a filestore nickname forlocal access, and a filestore AET for remote access.

Local Resource Directory . The file containing informationon local users, local filestores, filestore subsets, and localfiles necessary for OSI/File Services to run initiator andresponder functions.

local-request handler . A server subtask that can process arequest submitted at the local system and can initiate aconversation.

log file . A file to which a NetView FTP component writesmessages.

logical unit . In SNA, a port through which an end useraccesses an SNA network. Each NetView FTP server is alogical unit.

logical unit name . A name used to represent the addressof a logical unit.

LRD. Local Resource Directory.

LU. Logical unit.

LU name . Logical unit name.

LU 0 conversation . The type of conversation NetView FTPuses for file transfers between a node where NetView FTPV2.1 MVS, NetView FTP V1 VM, or NetView FTP V1 VSE isinstalled and a node where NetView FTP V1 MVS or FTP V2is installed.

LU-LU session . In SNA, a session between two logicalunits (LUs) in an SNA network.

manual transfer restart . NetView FTP’s method forallowing a user to restart a file transfer that was interruptedby submitting a restart request for that file transfer.

master password . A password, set by the NetView FTPsystem programmer that lets those who specify it query,modify, or delete any request in the request queue,regardless of whether or not it is password-protected, andregardless of who added it to the queue.

message area . The area of storage to which NetView FTPwrites the messages it issues to an application program.

mode . The session limits and common characteristics of thesession associated with advanced program-to-program(APPC) devices managed as a unit with a remote location.

mode description . A system object created for advancedprogram-to-program (APPC) devices that describes thesession limits and the characteristics of the session, such asthe maximum number of sessions allowed, maximum numberof conversations allowed, and other controlling information forthe session.

MVS node . A node with MVS as its operating system.

MVS system . A system with MVS as its operating system.

NETBIOS. Network Basic Input/Output System. Anoperating system interface for application programs used onIBM personal computers that are attached to the IBMToken-Ring Network.

NetView FTP administrator . Someone who knows themaster password. A NetView FTP administrator can query,delete, modify, hold, or release any request regardless ofwhether it is password-protected, and regardless of whosubmitted it.

NetView FTP AIX . NetView File Transfer Program Serverfor AIX and NetView File Transfer Program Client for AIX.

NetView FTP application program . An application programthat adds, queries, modifies, or deletes a request, or thatretrieves information about NetView FTP.


NetView FTP batch job . A batch job that adds, queries,modifies, or deletes a request, or that retrieves informationabout NetView FTP.

NetView FTP Client for DOS and Windows . NetView FileTransfer Program &clw..

NetView FTP MVS . NetView File Transfer Program forMVS.

NetView FTP OS/2 . NetView File Transfer ProgramServer/2 and NetView File Transfer Program Client/2.

NetView FTP/400 . NetView File Transfer Program forOS/400.

NetView FTP partition . A VSE partition that contains themain components of NetView FTP VSE.

NetView FTP shared block . An area of CSA storage that isused to pass data between the components of NetView FTP.Any data that does not fit in the FSB is put in the NetViewFTP shared block extension.

NetView FTP shared block extension . An area of ECSAstorage that is used to pass data between the components ofNetView FTP. It contains any data that does not fit in theNetView FTP shared block.

NetView FTP VM . NetView File Transfer Program for VM.

NetView FTP VSE . NetView File Transfer Program for VSE.

network . An interconnected group of nodes.

network drive . With NetView FTP, it is a shared resourcethat can be accessed from each workstation in the LAN.

network job entry facility . A facility that uses the networkjob-interface (NJI) protocols to allow a computer system tocommunicate with other computer systems in a network.

NFTP directory . The directory that contains the NetViewFTP/2 product files.

NFTPWORK directory . The directory that contains allNetView FTP/2 work files, for example, the NetView FTPmessage and log files.

NJE. Network job entry.

NJI. Network job-interface.

node . An endpoint in a link, or a junction common to two ormore links in a network. A deprecated term for server group.

node ID . Deprecated term for server group.

node ID table . Deprecated term for server group table.

not-after time . The time after which NetView FTP is not toprocess a request.

not-before time . The time before which NetView FTP is notto process a request.

numeric literal . A numeric character or string of numericcharacters whose value is implicit in the charactersthemselves; for example, 777 is the literal as well as thevalue of the number 777.

octal . Pertaining to a selection, choice, or condition that haseight possible different values or states.

OEM. Original equipment manufacturer.

Open Systems Interconnection . The seven-layercommunications architecture used for the definition ofprotocol standards for networks.

operation mode . See attended mode and unattendedmode.

operational key . Deprecated term for cryptographic key.

Original equipment manufacturer . A manufacturer ofequipment that may be marketed by another manufacturer.

originator ID . A string of characters that identifies the job,started task, or user that added a request to the requestqueue.

OSI. See Open Systems Interconnection.

other-domain resource . A recommendation for a logicalunit that is owned by another domain and is referenced by asymbolic name, which can be qualified by a networkidentifier.

panel . A predefined image displayed on a terminal screen.

panel flow . The way in which panels are chained togetherso that a user can move from one to another.

panel layout . The way in which the text and the input fieldson a panel are arranged.

partitioned data set . A data set in direct access storagethat is divided into partitions, called members, each of whichcan contain a program, part of a program, or data.

PCF. Programmed Cryptographic Facility.

PDS. Partitioned data set.

path information unit . In SNA, a message unit consistingof a transmission header (TH) alone, or a TH followed by abasic information unit (BIU) or a BIU segment.

phase . The smallest unit of executable code that can beloaded into virtual storage.

ping . The use of the ping command to send an echorequest to a network host or gateway.

port . With NetView FTP, the communication end point inTCP/IP. A port is identified by a port number.

Glossary 153

port number . In TCP/IP, a 16-bit number used tocommunicate between TCP/IP and a higher-level protocol orapplication.

post-conversation user exit . A user exit that passescontrol to a routine at the system at which the file-transferrequest originated. This routine is to run just after theservers terminate their conversation.

post-transfer user exit . A user exit that passes control to aroutine that is to run just after a server closes a file that hasbeen transferred.

pre-queuing user exit . A user exit that passes control to aroutine that is to run just after a request is submitted toNetView FTP and just before NetView FTP adds the requestto the queue.

pre-transfer user exit . A user exit that passes control to aroutine that is to run just before a server opens a file that isto be transferred.

preparation user exit . Deprecated term for pre-transferuser exit.

process (a request) . To obtain and try to carry out (arequest).

program temporary fix . A temporary solution to bypass ofa problem diagnosed by IBM as resulting from a defect in acurrent unaltered release of a program.

PTF. Program temporary fix.

PUBX. Physical Unit Control Block Extension.

QDA. Query data area.

QRA. Query response area.

QSAM. Queued sequential access method.

QSR. Query Status Record.

query (a request) . To ask for information about (a request).

query data area . The area of ECSA storage into whichNetView FTP places either user query records oradministrator query records.

query response area . The area of storage into whichNetView FTP places information it retrieves for an applicationprogram.

queue handler . A NetView FTP component that controlsaccess to the request queue. In NetView FTP MVS, thequeue handler also controls all other NetView FTPcomponents and all communication with the operator.

queue handler command . A command that a componentof NetView FTP issues to the queue handler when it wantsthe queue handler to do something.

queued sequential access method . An extended versionof the basic sequential access method (BPAM). When thismethod is used, a queue is formed of (1) input data blocksthat are awaiting processing or (2) output data blocks thathave been processed and are awaiting transfer to auxiliarystorage or to an output device.

raw device . In the AIX operating system, a device thattreats data I/O as a continuous stream, without considerationfor the data’s logical structure. For example, I/O for fixeddisks and streaming tapes occurs in units of bytes that haveno relationship to characters.

RCB. Request control block.

RCE. Request control element.

RDF. Request definition file.

reason code . A value issued by a program that givesadditional information about a situation described by a returncode.

receiving data set . A data set in which a copy of a file thathas been sent using NetView FTP has been placed.Contrast with sending data set.

receiving file . A data set in which a copy of a file is placedthat has been sent using NetView FTP. Contrast withsending file.

receiving system . The NetView FTP system that receivesthe file being transferred.

regular checkpointing . To take a checkpoint at specifiedregular intervals.

regular file . In the AIX operating system, a file that containsdata. A regular file can be a text file or a binary file. Textfiles contain information readable by the user. Thisinformation is stored in ASCII. Binary files containinformation readable by the computer.

relative record data set . In VSAM, a data set whoserecords are loaded into fixed-length slots and arerepresented by the relative-record numbers of the slots theyoccupy.

remote . Pertaining to a system other than one’s own.

remote filestore . A collection of remote files. OSI/FileServices users can access a file residing in a remote systemonly if they specify the filestore AET of the remote filestore,and the OSI file name of the related file.

remote-request handler . A server subtask that can accepta conversation initiated by a local-request handler at aremote system.

report . Synonym for file-transfer report.

report recipient . A user to whom a server sends afile-transfer report.


request . Synonym for file-transfer request.

request class . A deprecated term for server class.

request control block . A control block that contains someor all of a file-transfer request. Data that does not fit in theRCB is put in the request control block extension.

request control block extension . A control block thatcontains data that does not fit in the request control block.

request control element . An element of the request queuedirectory.

request database . In NetView FTP/400, the database inwhich NetView FTP stores all requests.

request definition file . A file containing NetView FTPcontrol statements, that is, all NetView FTP parameters withtheir appropriate values that are necessary for a file transfer.

request handler . A server subtask. See alsoremote-request handler.

request number . A number that the queue handler assignsto a request when it adds the request to the request queueand that is used to identify the request.

request password . A character string, assigned by a userto a request, that prevents users sharing that user’soriginator ID from deleting or modifying that user’s waitingand active requests. If a user specifies a request passwordfor a request, another user with the same originator ID mustspecify either the request password or the master passwordto be able to delete or modify the request while it is waiting,or to delete the request while it is active.

request priority . A number, assigned by a user to eachrequest, that determines the order in which a server is toprocess it. When a server is ready to process a request andseveral requests are eligible, the server processes therequest with the highest priority first.

request queue . In NetView FTP for MVS, VSE, or VM, thefile in which NetView FTP stores requests that have beensubmitted for processing.

request queue directory . A directory of the contents of therequest queue.

request unit . A message unit that contains controlinformation, end-user data, or both.

request-queue user exit . Deprecated term for pre-queuinguser exit.

requesting system . The system where the file-transferrequest has been initiated.

resident session partner . An FTP V2 MVS or FTP V2VSE server that runs continuously and can perform an

indefinite number of file transfers, however, these filetransfers must all be initiated by servers at remote systems.

responding system . The system responding to afile-transfer request.

return code . A value issued by a program that describesthe outcome of an operation performed by that program.

root . In the AIX operating system, the user name for thesystem user with the most authority.

RRDS. Relative record data set.

RTM. Recovery Termination Manager.

RU. Request unit.

RXB. Request control block extension.

SAF. System authorization facility.

SAM. Sequential access method.

SAS. Spool Access Services.

saved request . A request that has been created with theNetView FTP panels and that has then been saved in anISPF table data set.

scheduling a request . Determining which request is to beobtained, obtaining it, and passing it to a server.

scroll amount . The amount that the list on a panel isscrolled up or down when you enter the UP or DOWNcommand.

SDA. Server data area.

SDMU. Source description message unit.

SDWA. System Diagnostic Work Area.

select members . To choose those members of a PDS thatare to be transferred. Contrast with exclude members.

sending data set . A data set, a copy of which is to betransferred using NetView FTP. Contrast with receiving dataset.

sending file . A file of which a copy is to be transferredusing NetView FTP. Contrast with receiving file.

sending system . The NetView FTP system stores the filethat will be transferred to the receiving system.

sequential access method . See basic sequential accessmethod.

server . (1) A NetView FTP component that establishes oraccepts conversations and that transfers files. (2) WithNetView FTP for Workstations, a NetView FTP Serverprogram that serves as a gateway for one or more NetViewFTP Client programs.

Glossary 155

server class . A number or letter, assigned by a user to arequest, that specifies which servers can process thatrequest.

server data area . The area of ECSA into which NetViewFTP places information about a server or servers.

server group . A group of servers (logical units).

server group table . A data set that specifies which serversmake up each server group, and that contains informationabout each server.

server modification area . An area of storage that containsthe modifications to a server’s session parameters.

session . In SNA, a logical connection between twonetwork-addressable units.

SFS. Shared file system.

SFS directory . A group of files. SFS directories can bearranged to form a hierarchy in which one directory cancontain one or more subdirectories as well as files.

shared file pool . See file pool.

shared file system . A part of CMS that lets users organizetheir files into groups known as directories, and selectivelyshare those files and directories with other users.

single mode . A server running mode in which a serverstops running after it has transferred a file (or attempted totransfer a file and failed).

slot . A space in the request queue directory that is able tohold a request control element (RCE).

SMA. Server modification area.

SMF. System management facilities.

SMS. Storage Management Subsystem.

SNA. Systems Network Architecture.

SNA compaction . The transformation of data by packingtwo characters in a byte that normally would only hold onecharacter.

SNA compression . The replacement of a string of up to 64repeated characters by an encoded control byte to reducethe length of the string.

SNA network . In SNA, the part of a user-applicationnetwork that conforms to the formats and protocols ofSystems Network Architecture. It enables reliable transfer ofdata among end users and provides protocols for controllingthe resources of various network configurations. The SNAnetwork consists of network addressable units, boundaryfunction components, and the path control network.

SNA node . A node that supports SNA protocols.

socket . In the AIX operating system: (1) A unique hostidentifier created by the concatenation of a port identifier witha TCP/IP address. (2) A port identifier. (3) A 16-bit portnumber. (4) A port on a specific host; a communications endpoint that is accessible through a protocol family’s addressingmechanism. A socket is identified by a socket address. Seealso socket address.

socket address . In the AIX operating system, a datastructure that uniquely identifies a specific communicationsend point. A socket address consists of a port number and anetwork address. It also specifies the protocol family.

SRMU. Statistics report message unit.

special file . In the AIX operating system, a file that definesa FIFO (first-in, first-out) file or a physical device.

SSCP. System Services Control Point.

statistics report message unit . A message unit sent bythe target (receiver of the file), at the end of the file transfer.

status . The state of a request in the request queue (MVS,VSE, or VM) or request database (OS/400). In NetView FTPfor MVS, VSE, or VM, the possible statuses are waiting,active, and finished. In NetView FTP/400, the possiblestatuses are held, waiting, active, finished, and failed.

status data area . The area of ECSA into which NetViewFTP places details of the status of a server or servers.

Storage Management Subsystem . An MVS subsystemthat helps automate and centralize the management ofDASD storage. SMS provides the storage administrator withcontrol over data class, storage class, management class,storage group, and ACS routine definitions.

submit (a request) . To give (a request) to NetView FTP sothat NetView FTP can add it to the request queue.

superuser . In the AIX operating system, the user who hasunrestricted authority to access and modify any part of theoperating system, usually the user who manages the system.

supervisor call instruction . An instruction that interrupts arunning program and passes control to the supervisor so thatthe supervisor can perform the service indicated by theinstruction.

SVA. Shared Virtual Area.

SVC. Supervisor call instruction.

symbolic constant . A data item that has an unchanging,predefined value.

system authorization facility . At an MVS or VM location, ageneric interface to security products that is provided by theoperating system. In this way, an installation has thepossibility to run a security program, such as IBM RACF.


System management facilities . An optional controlprogram for MVS that provides the means for gathering andrecording information that can be used to evaluate systemusage.

system services control point . In SNA, a focal point withinan SNA network for managing the configuration, coordinatingnetwork operator and problem determination requests, andproviding directory support and other session services forend users of the network. Several SSCPs, cooperating aspeers, can divide the network into domains of control, witheach SSCP having a hierarchical control relationship to thephysical units within its domain.

Systems Network Architecture . The description of thelogical structure, formats, protocols, and operating sequencesfor transmitting information units through, and for controllingthe configuration and operation of, networks. The layeredstructure of SNA allows the origin and ultimate destination ofinformation to be independent of and unaffected by the SNAnetwork services and facilities used to transfer thatinformation.

table display panel . A panel that contains a scrollable list.

Target Information Message Unit . A message unit sent bythe receiving node after it receives an SDMU. A TIMUupdates the original request, to inform the sender where tostart or restart sending, and, to convey statistical information.

TCP. Transmission Control Protocol.

TCP/IP. Transmission Control Protocol/Internet Protocol. Aset of communication protocols that support peer-to-peerconnectivity functions for both local and wide area networks.

TIMU. Target Information Message Unit.

token-ring network . A network that uses a ring topology, inwhich tokens are passed in a circuit from node to node. Anode that is ready to send can capture the token and insertdata for transmission.

Transfer Request Message Unit . A message unit used tosend or receive a file, or to restart a previously interruptedfile transfer.

Transmission Control Protocol . A communicationsprotocol used in Internet and in any network that follows theU.S. Department of Defense standards for inter-networkprotocol. TCP provides a reliable host-to-host protocolbetween hosts in packet-switched communications networksand in interconnected systems of such networks. It assumesthat the Internet protocol is the underlying protocol.

TRMU. Transfer Request Message Unit.

unattended mode . An operating mode of NetView FTP forWorkstations that assumes that a user is not available at theworkstation, for example, to load devices such as diskettesor tapes. Contrast with attended mode.

unused slot . A slot that does not contain a request controlelement (RCE).

user exit . A point in an IBM-supplied program at which auser-exit routine is given control.

user interface . Hardware, software, or both that allows auser to interact with and perform operations on a system orprogram.

user query command . A type of command that causesNetView FTP to retrieve information about the requests in therequest queue; the information retrieved is intended for usersof NetView FTP. Contrast with administrator querycommand.

user query record . A record containing the informationNetView FTP retrieves when a user issues a user querycommand. Contrast with administrator query record.

user-exit routine . An exit routine written by a user.

user-written file handler . An exit routine, written by a user,that gains access to a file and passes its records to NetViewFTP, or that retrieves the records from NetView FTP andwrites them to a file.

virtual storage access method . An access method forindexed or sequential processing of fixed- and variable-lengthrecords on direct-access storage devices. The records in aVSAM data set can be organized (1) in logical sequence bymeans of a key field (key sequence), in the physicalsequence in which they are written in the data set (entrysequence), or (2) by means of a relative-record number.

Virtual Telecommunications Access Method . SeeAdvanced Communications Function for the VirtualTelecommunications Access Method.

VM node . A node with VM as its operating system.

VM system . A system with VM as its operating system.

VSAM. Virtual storage access method.

VSE node . A node with VSE as its operating system.

VSE system . A system with VSE as its operating system.

VTAM. Virtual Telecommunications Access Method. SeeAdvanced Communications Function for the VirtualTelecommunications Access Method.

waiting request . A request that is waiting to be processed.

WAN. Wide area network.

Wide area network . A network that providescommunication services to a geographic area larger than thatserved by a local area network and that may use or providepublic communication facilities.

Glossary 157

wildcard character . Either a question mark (?) or anasterisk (*) used as a variable in a file name or file nameextension when referring to a particular file or group of files.

WTO. Write-to-operator.

XID. Exchange identification.

XnMU. Exit(n) message unit.


Bibliography

The NetView FTP Library

This manual is part of a library of publications that describeNetView FTP and explain how to use it. The publications inthis library are:

NetView File Transfer Program for VSE:

NetView FTP Licensed Program Specifications,GH12-5485NetView FTP VSE User’s Guide, SH12-5673NetView FTP VSE Installation, Operation, andAdministration, SH12-5674NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program for VM:

NetView FTP General Information, GH12-5480NetView FTP Licensed Program Specifications,GH12-5485NetView FTP VM User’s Guide, SH12-5675NetView FTP VM Installation, Operation, andAdministration, SH12-5676NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483

NetView File Transfer Program for OS/400:

NetView FTP General Information, GH12-54801

NetView FTP V1 for OS/400 Licensed ProgramSpecifications, GH12-5777NetView FTP V3 for OS/400 Licensed ProgramSpecifications, GH12-6176NetView FTP V1 for OS/400 Installation and User’sGuide, SH12-5776NetView FTP V3 for OS/400 Installation and User’sGuide, SH12-6177

NetView File Transfer Program Version 2 for MVS:

NetView FTP Licensed Program Specifications,GH12-5485NetView FTP V2 MVS User’s Guide, SH12-5656NetView FTP V2 MVS Installation, Operation, andAdministration, SH12-5657NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program Server for AIX,NetView File Transfer Program Client for AIX:

NetView FTP for Workstations: AIX Installation andUser’s Guide, SH12-6187NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program Server/2,NetView File Transfer Program Client/2NetView File Transfer Program Client for DOS andWindows:

NetView FTP for OS/2, DOS, and WindowsWorkstations: Installation and User’s Guide,SH12-6080NetView FTP Parameter Reference, SH12-6052

The unlicensed manuals with prefix SH are also available assoftcopy on the following collection kits:

IBM Networking Softcopy Collection Kit, SK2T-6012IBM Online Library Omnibus Edition: MVS Collection,SK2T-0710IBM Online Library Omnibus Edition: VM Collection,SK2T-2067IBM Online Library Omnibus Edition: VSE Collection,SK2T-0060IBM Online Library Omnibus Edition: AIX Collection,SK2T-2066

Related PublicationsISO FTAM-IS-Standard Part 3, ISO 8571-3

ISPF V3 for MVS Dialog Management Services andExamples, SC34-4215

ISPF Dialog Management Services and Examples,SC34-4156

ISPF V3 for VM Dialog Management Services andExamples, SC34-4223

MVS/DFP V3: Macro Instructions for VSAM Data Sets,SC26-4569

MVS/DFP V3: Macro Instructions for Non-VSAM DataSets, SC26-4558

MVS/DFP V3.3: System Programming Reference,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.


MVS/ESA Application Development Reference: Servicesfor Assembler Language Programs, GC28-1642

MVS/XA VSAM Administration: Macro InstructionReference, GC26-4152

MVS/XA Data Administration: Macro InstructionReference, 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 CryptographicFacility: Installation Reference, SC28-0956

VM/ESA CMS Application Development Reference forAssembler, 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 DevelopmentReference, 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 MacroReference, 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


VSE/System Package Messages and Codes Version 4Volume 1, SC33-6407

Using VSE/VSAM Commands and Macros, SC24-5144

VTAM Programming for LU 6.2, SC31-6410

VTAM Programming, SC31-6409

Bibliography 161

Your comments, please ...

NetViewFile Transfer ProgramVersion 2 for MVSVersion 1 for VSE and VMMessages 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 opinionabout 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, youshould talk to your IBM representative or to your IBM authorized remarketer. This form is provided for comments about theinformation 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 itbelieves 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.

Cut or FoldAlong Line

Cut or FoldAlong Line

Your comments, please ...SH12-5483-07 IBM

Fold and Tape Please do not staple Fold and Tape

PLACEPOSTAGESTAMPHERE

IBM Deutschland Entwicklung GmbHInformation Development, Dept. 0446Postfach 138071003 BoeblingenGermany

Fold and Tape Please do not staple Fold and Tape

SH12-5483-07

IBM

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

Printed in Denmark by IBM Danmark A/S

SH12-5483-ð7

Messages & Codes

Documents

Transcript of Messages & Codes