EZX Manual - ETI-NET

HP NonStop – MVS Transfer Over XP Array Version 1.58 Configuration and User’s Manual CREATION DATE: REVISION DATE: July 7, 2005 March 10, 2016 ETI-NET 180, Rene-Levesque Blvd. East, Suite 320 Montreal, Quebec (Canada) H2X 1N6 Tel.: (514) 395-1200 Fax: (514) 395-9080 HCOM, BCOM, BACKHOME, BACKBOX AND EZX-GATEWAY ARE THE PROPRIETARY AND CONFIDENTIAL INFORMATION OF ETI-NET AND MAY BE USED AND DISCLOSED ONLY AS STIPULATED IN THE LICENSE AGREEMENT CONTROLLING SUCH USE AND DISCLOSURE. NO PART OF THIS SOFTWARE MAY BE DISCLOSED OR REPRODUCED IN ANY FORM WITHOUT THE PRIOR WRITTEN CONSENT OF ETI-NET MANAGEMENT. Table of Contents i Table of Contents EZX-GATEWAY SYSTEM............................................................. 1 PREFACE ................................................................................... 1 Technical Support ....................................................................................... 2 Summary of Changes .................................................................................. 3 PRODUCT DESCRIPTION ............................................................... 5 EZX-Gateway Components........................................................................... 6 Product Requirements ................................................................................. 9 Basic Functions ........................................................................................ 10 NONSTOP APPLICATION INTERFACE .............................................. 13 TACL Macros ............................................................................................ 14 EZX_START_XFER Macro ........................................................................... 15 EZX_FREE_MVS_DATASET Macro ................................................................ 19 EZX_REMOTE_SUBMIT .............................................................................. 19 Tools Reporting the Completion of a Transfer ............................................... 20 GETEVOL[E] Program ................................................................................ 21 EZXVUTL[E] Library .................................................................................. 25 Header file ............................................................................................... 30 MVS APPLICATION INTERFACE .................................................... 34 Datasets Read or Written by EZX Transfers .................................................. 34 Description of the Control Dataset .............................................................. 35 INSTALLATION ......................................................................... 36 1. Design the EZX Network Topology ...................................................... 38 2. Configure the TCP/IP LISTNER for the Domain Manager ........................ 40 3. Install the VTC Hardware................................................................... 40 4. Install HP XP Software and Test the XP Connection ............................... 40 5. Install the Guardian Software ............................................................ 40 6. Define the Virtual Devices in Guardian SCSI Connection ........................ 44 7. VT Controller Internal Emulator Configuration ...................................... 45 8. Set Up the Domain Manager Address for Each VT Controller .................. 45 9. Configure the EZX Domain ................................................................ 46 10. Configure and Start the EMS Extractor ................................................ 47 11. Customize the NSK TACL Macros ........................................................ 50 12. NSK Test Programs ........................................................................... 50 13. Set Up for Recovery .......................................................................... 52 OPERATIONS ........................................................................... 53 VT Controller Startup ................................................................................ 53 VT Controller Shut Down ........................................................................... 53 Tape Device Reset .................................................................................... 53 VT Controller Reset ................................................................................... 54 Disabling the Automatic Mounting of Volumes .............................................. 54 Enabling the Automatic Mounting of Volumes ............................................... 55 Manual Load and Unload ............................................................................ 55 Table of Contents ii WEB USER INTERFACE ............................................................ 56 STANDARD PAGE ELEMENTS ........................................................ 56 Banner .................................................................................................... 56 Navigation Bar ......................................................................................... 57 Tabbed Pages ........................................................................................... 57 SIGN IN ................................................................................. 58 Sign In Tab .............................................................................................. 58 Domain Address Tab ................................................................................. 59 Domain Address Detail .............................................................................. 60 HOME ..................................................................................... 61 Virtual Device Status ................................................................................. 62 Pending Mounts ........................................................................................ 62 CONFIGURATION ....................................................................... 63 Domain ................................................................................................... 64 VT Controller ............................................................................................ 65 Data Store ............................................................................................... 68 Volume Group .......................................................................................... 70 VOLUME .................................................................................. 72 Volume List .............................................................................................. 72 Volume List Filter ...................................................................................... 73 Volume Details ......................................................................................... 75 Update of a Volume Entry in the EZX-Gateway Catalog ................................. 78 Create Volume ......................................................................................... 79 Data Exchange ......................................................................................... 81 APPENDIXES ............................................................................. I Appendix A – ASCII-EBCDIC Conversion Table ............................................... I Appendix B – JIS-EBCDIK Conversion Table .................................................. II Appendix C – Error Message Table .............................................................. III EZX-Gateway System 1 EZX-Gateway System Preface This User Manual contains reference information for the configuration and operation of the EZX-Gateway system. EZX-Gateway transfers data files between an HP NonStop and IBM MVS disks located in an HP XP Array disk system. EZX-Gateway works along with another ETI-NET legacy product, BCOM, which is documented by the regular BCOM manuals. Related ETI-NET documentation for the EZX-Gateway: Virtual Tape Controller Preparation Notes about the prerequisites in Windows 2003 Installation procedure for the SCSI card and its driver Installation procedure for the FC-SCSI Router and its firmware VT Controller Software Installation Procedure for installing the ETI-NET application in a VTC unit Related ETI-NET documentation for the EZX-Gateway: BCOM for MVS V5 User's Guide BCOM for NSK Guardian V5 User's Guide ETI-NET Messages Manual BCOM NSK - EZX Installation guide BCOM OS390 - EZX Installation guide BCOM OS390 - EZX Upgrade procedure Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 2 Technical Support You can reach our Technical Support department for information on any ETI-NET product by: Phone: (514) 395-1200 ext. 336 Fax: (514) 395-9080 Email: support1@ETINET.com Please visit our Website at www.ETINET.com for our latest technical documentation or for information about other ETI-NET products. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 3 Summary of Changes Version V1.51 – September 2005  The lock requested to MVS agent on MVS datasets is always exclusive against other MVS applications, whatever the transfer direction.  Volumes identified in EMS messages EMS message #640 ‘UNREQUESTED ANSI TAPE id ONLINE' are unloaded automatically.  The severity level is included in the EMS message #3118 reporting the MVS dataset freeing and number of transferred records.  Retries are implemented in the EZX_START_XFER macro, and controlled by new parameters in EZXSETUP.  New parameter STOREID for the EZX_FREE_MVS_DATASET macro.  Support tools TAPERD and TAPEWR are included in the package. Version V1.52 – September 29th, 2005  Validation of the DCB of a dataset to create Version V1.52 – October 6th, 2005  New tool EZXVUTL/GETEVOL to report the completion of a transfer Version V1.52 – October 12th, 2005  Revision of input parameters of EZXVUTL/GETEVOL Version V1.53 – November 9th, 2005  New value OVERRIDE available for the R_FCREATE parameter of the EZX_START_XFER macro.  Addition of the MVS timestamp in EMS message reporting error occurring on the MVS platform. Version V1.54 – November 29th, 2005  New field “Current Operation” in the volumes search engine.  New read-only volumes attribute “Severity”. Version V1.55 – December 9th, 2005  Automatic unload on devices that appear unloaded from NSK Guardian but are internally loaded in the VTC emulator. This helps managing the consequences of severe tape IO errors (such as SMD timeout) leading to discrepancy between the apparent state of a device in the Guardian tape system, and the internal state of the same device in the VTC emulator. Version V1.56 – December 23rd, 2005  EZXVUTL[E] new field currentOperation in parameter  GETEVOL[E] ABEND when the current operation is POST_TRF. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 4 Version V1.57 – March 30th, 2006  New optional parameter EZX_TIMEOUT in EZXSETUP for the macros EZX_START_XFER and EZX_FREE_MVS_DATASET, to replace the default value of 5 minutes.  Adjustments to EMS messages 3112, 3140, 3141  New automatic retry to communicate to MVS the result of a transfer, after a TCPIP failure. New parameter <volume-scan-interval> in BBEXTCFG.  Reduction of IPC traffic between BBEXT[E] and the EMS distributor. New parameters <EMSCOLLECTOR> & <EMSFILTER> in BBEXTCFG.  Better still partial support of 3380 disk geometry, for test purpose only.  OBEY file to list EMS messages related to tapes ($ZSVR and EZX messages), New files EMSFILT2 and OEMS. Version V1.58 – June 2nd, 2006  EZXVUTL[E] modified to continue to wait when the volume state is POST_TRF.  New optional TACL PARAM EZXVUTL-MAXIMUM-WAIT containing EZXVUTL[E] (except GETEVOL[E]). for programs EZXVUTL-MAXIMUM-WAIT overrides the maximum wait time passed by call parameter to the EZXVUTL[E] library. When this PARAM is not set, the minimum wait time is 30 seconds whatever the value passed by call parameter. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 5 Product Description The EZX-Gateway system consists of software and hardware dedicated to massive data transfers between the HP NonStop platform and IBM MVS disks located in an HP XP Disk Array. The hardware component provided with the EZX-Gateway product is one or several Virtual Tape Controllers (VTC) that physically connects HP NonStop servers (NSK) with HP XP Array. Transfers can performed to or from the HP NonStop, by regular NSK Guardian tape applications writing or reading a tape file on tape. For example, FUP can be used to copy a Guardian disk file to an MVS dataset. The MVS dataset appears to the Guardian operating system as a tape file on a tape volume with ANSI labels. A VTC emulates tape drives, accepts the tape SCSI data stream from the NonStop server and directly writes/reads data to MVS Data/Exchange volumes in the XP Array, using the FAL API provided with the XP Array. The VTC connects to NSK through SCSI or Fibre cables. For Fibre connections, the current VTC model includes an internal Fibre/SCSI router and SCSI cards. A Fibre only solution is being developed. The EZX-Gateway interfaces the NSK tape system to manage the application, especially to automate the tape mount requests. It also communicates with the MVS system to create the MVS datasets or verify their characteristics, and to locks these MVS datasets to preserves the integrity of MVS files while they are accessed by a VTC. EZX-Gateway is supported by the legacy ETI-NET product BCOM, which offers IP connectivity for remote job submission between the NSK and IBM MVS platforms. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 6 EZX-Gateway Components The hardware provided with the EZX-Gateway is one or several VT Controllers. Software is supplied on the VT Controllers, on the NSK and on the MVS platforms. Virtual Tape Controllers The hardware part of the solution is a dedicated to Windows 2003 system with two essential functions: o The emulation of tape drives compatible with the NonStop platform. Each VTC can provide up to four SCSI ports or two Fibre ports with internal conversion to four SCSI ports. Several virtual devices can be defined on each port; however, they share the bandwidth of the port connection. o The FAL library that allows direct access to the XP Array transfer volumes without any staging, using special Data Exchange (DE) XP volumes. In the emulator, a discover function recognizes DE XP volumes configured and formatted by the HP XP software on the Windows 2003 server. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 7 This server also contains an IIS Web server that supports the Web User Interface designed to easily configure and set up the Domain. Web Application The user interface is a regular Web User Interface, for configuration and exceptional manual operations. Regular EZX operations are automated. The configuration mainly consists of: Defining the VT Controllers and their virtual tape drives. Defining the MVS partner EZX Agent. Creating virtual NSK tape volumes that will be used as medium for transfers. This Web application is also used in case of operational problems for queries and manual interventions. Domain Manager One or more Guardian nodes connected to one or more VT Controllers are referred to as an EZX domain. An EZX domain is managed by a server hosted by a Guardian node that replies to requests issued by a Web User Interface, by the EMS Extractor or by an EZX macro. The Domain Manager: o Maintains the configuration of the domain, the configuration of the VT Controllers, the MVS partner EZX Agent and the arrangement of the DE XP volumes in logical groups named “EZX Data Stores” o Maintains the list of virtual tape volumes o Manages the transfer: solves the tape mount requests, synchronizes the lock and unlock of MVS dataset with the start and end of the transfers. EMS Extractor Each Guardian node that has a virtual tape drive runs an Event Extractor. The Event Extractor, from the Guardian’s point of view, automates the mounting of the virtual volumes for a NSK node. The Event Messaging System (EMS) Extractor is a permanent process that must run on all NonStop nodes of a Domain. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 8 NonStop EZX Guardian Utilities These utilities are presented through TACL macros used by Guardian applications to: Prepare EZX transfers: create/verify the MVS datasets and create the TAPE DEFINE for the tape application responsible for the reading and writing of virtual EZX tape volumes. Using the macro is mandatory. Use BCOM services for generic remote job submissions, for example to trigger the MVS application reading the data transferred from the NonStop node. NonStop and MVS BCOM Services The classic ETI-NET product BCOM offers several transfers over IP between NonStop and IBM MVS: file transfer, remote job, and remote spooling. For the EZX product, BCOM is used for: Classic remote job from NSK to MVS and vice versa. Hosting the EZX MVS Agent in BCOM on MVS. This product is not described in the EZX manual, as the legacy BCOM user interfaces are the same when operated for EZX. New user interfaces were implemented for the EZX MVS Agent and are described in this EZX manual: On NSK: the TACL macro EZX_START_XFER and the Web User Interface. On MVS: A file available for programmatic interface which contains the EZX transfer statistics. EZX MVS Agent The EZX MVS Agent is a server for requests coming from the NSK platform. provides: The optional creation of MVS datasets. The query of the MVS catalog to find: The collection of MVS continuation datasets involved by a single large transfer (when the size exceeds the capacity of a single DE volume) The volume name and other characteristics of the MVS files involved in a transfer. The lock of MVS datasets during the transfer. Last Revised: Mar. 10, 16 Version 1.58 It EZX-Gateway System 9 Product Requirements NonStop Server Components TCP/IP connection (to VTCs) Fibre or SCSI connection (to VTCs) with controller device support for tape drive Guardian version G06.23 or later TCP/IP Tape subsystem with support of labelled tapes. Expand connectivity between all NSK nodes of a Domain Workstation Requirements Computer with TCP/IP connection (to VTCs) Microsoft Internet Explorer Web browser with: TCP/IP JavaScript enabled Cookies accepted HTML 4 support Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 10 Basic Functions After installation and configuration, NSK Guardian tape applications transfer data over a virtual tape drive by using: The provided TACL macro EZX_START_XFER to prepare the transfer. A regular NSK tape program that reads or writes an ANSI tape volume. Virtual Tape Volumes A volume label is a mandatory parameter for the EZX_START_XFER macro for all transfers. The tape application uses virtual tape volumes that must be created through the Web User Interface before being used, in the same way real tapes must be labelled before being used. In EZX, tape volumes are ANSI tape volumes that must be not catalogued in DSM/TC or other tape catalogs. Two concurrent transfers cannot use the same volume. A volume is associated to a given transfer only during the transfer execution. After the transfer, the volume holds transfer statistics that can be seen through a Web User Interface (using a browser), until the volume is reused by another transfer. Virtual Volume Mounts Virtual volumes follow the standard cycle of tape mount request, volume mount, and volume recognition by $ZSVR. The volume label present in the EMS message lets the EZX software know whether the requested volume is a virtual volume to handle or a standard real volume to ignore. Automatic Mount The EZX EMS Extractor automates the mount process. It listens to mount requests events and sends the required command to the VT Controller. Manual Mount In case of difficulty, a mount can be manually initiated through the Web application. This manual mount can only be executed by selecting a pending mount on the Home page. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 11 Tape Device Assignment When the tape device is not specified in the EZX_START_XFER macro, the Domain Manager assigns a virtual device. To be assigned, a device must be: Free. Connected to the Guardian node from where the mount request is issued. Connected to a VT Controller that is configured as a route to the Data Store “containing” the tape volume, as set at the creation of the volume. Not configured as a device reserved for explicit allocation (with an Only attribute) Explicit The device assignment distributes the workload across available ports and VT Controllers. Drives on a bus with fewer jobs are preferred. Between buses of equal workloads, drives connected to a VTC with fewer jobs are preferred. The priority configured in the Data Store route (rank) overrides the spreading of the workload. All devices associated with the lowest rank are allocated before the devices of the next highest rank are allocated. To distribute the tape jobs to all VTCs, the devices of a Domain are assigned in a round robin fashion. The round robin allocation will eventually reach all devices, if the user does not submit a transfer over a specified device, and if all VTCs are configured as route to the target Data Store. MVS dataset lock While they are read or written by a VTC during a transfer, MVS datasets are locked by the EZX MVS Agent. This protects the integrity of the data when the datasets are accessed outside the control of the MVS operating system. Multi volume MVS datasets To allow transfer sizes that are larger than a single DE XP volume, the MVS dataset can be defined as a series (up to 255) of distinct datasets, which will be considered as a logical target or origin of a transfer. By naming convention, specifying a dataset name by ending it with ".EZX" in the TACL EZX_START_XFER macro will have them processed as a group of datasets from "prefix.EZX0001" to "prefix.EZXnnnn". Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 12 MVS dataset creation From the TACL EZX_START_XFER macro, the MVS dataset can be created. The creation is controlled by: o The EZX_START_XFER parameters o The EZX Data Store configuration The dataset creation is required (in megabytes); EZX computes the number of required datasets according to the disk geometry and the requested dataset DCB. Control of Access to Virtual Volumes The access to virtual volumes can be authorized depending on the Guardian User ID running the Nonstop tape application. This security is inherited from the parent BackBox product, where each volume has its own security specification that protects the data of this particular volume. In EZX, this security is rather a way to reserve the usage of tape labels to some users. If the security specification of all virtual volumes is tightly controlled, this security can also contribute to restrict the access to the DE XP volumes through EZX. All datasets on DE XP volumes will have the same exposure, defined as the sum of all accesses allowed by all tape volumes of the Data Store. Security attributes are stored in the EZX catalog for each virtual volume: The Guardian owner (Guardian node and Guardian User ID) The first owner is the User ID entered to start the Web User Interface that created the volume. This owner can be changed by the Web application’s Volume Edit page. Three access authorizations: Read, Write and Control: “Read” allows the user to read the volume data. “Write” allows the user to read, write and delete the volume data. “Control” allows the user to modify the volume security through the Web User Interface. The first access authorizations are set by the default values specified in the Volume Group configuration. They are kept unmodified until they are explicitly changed by the Web application Volume Edit page. The security attributes are checked at each load and at other volume operations, against the user. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 13 Authorization specification: Each of the three access authorizations (Read, Write and Control) specifies how the user should compare with the owner to get access to the volume. The user can be: N Any node, any User ID C Any node, same group number U Any node, same User ID A Same node, any User ID G Same node, same group number O Same node, same User ID NonStop Application Interface From the application point-of-view, an MVS dataset on a DE XP volume appears as a tape file on a labelled ANSI tape volume. By writing or reading a NSK tape volume, the application actually writes or reads records in the remote MVS dataset. The application must prepare the transfer by running the EZX_START_XFER TACL macro. This macro will communicate with the Domain Manager and with the remote EZX MVS Agent in order to: Query and possibly create the remote MVS dataset(s). Create in the current TACL context a TAPE DEFINE whose attributes are according the macro parameters (such as VOLUME and FILE ID), and the information returned by the EZX Agent on the MVS platform Then the application must open the prepared TAPE DEFINE. It must expect ANSI labels and a single tape file per volume. The data must be accessed only sequentially. TAPECATALOG DEFINE is not used, as there is no permanent relation between a tape volume label and data content. The correspondence between a virtual volume and specific data is guaranteed during a transfer only. The correspondence is then lost when the MVS system changes the dataset, or when the tape volume is re-used for another transfer. Processing of ANSI Tape Labels The Guardian system must be set for processing of labelled tapes, as usual. The application will not access these labels, as usual. The Guardian tape system ($ZSVR) will see the labels and will write them. These labels are not stored in the MVS file, but generated on the fly by the VT Controller. The MVS data is seen as a single tape file by the Guardian application, even if the size of the transfer requires distributing the data across several DE XP volumes. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 14 Record and Block Processing The VT Controller assumes that the transferred file is structured in records, and takes charge of the unblocking on one side and the re-blocking on the other. The VTC supports any block Fixed and variable record formats are supported. The EZX_START_XFER macro will set the record format (fix/variable) of the TAPE DEFINE equal to the format of the MVS dataset reported by the EZX MVS Agent. When the format is variable: The VTC assumes the VARIN-VAROUT format, which FUP supports. The regular variable unblocked format is not supported. The tape define is created with RECFORM U (default value). The application must provide or accept the VARIN-VAROUT format. The EZX application in the VT Controller takes charge of the blocking/unblocking on the Guardian side. The VTC supports any block length (up to 52 KB) requested by the IO of the Guardian application. The Guardian side always provides the IO length in the SCSI IO command, whether for reading or writing. The FAL XP library executes the blocking/unblocking of records for the MVS file. ASCII-EBCDIC and JIS-EBCDIK Translations The conversions are available in both transfer directions, and enabled by the CONVERSION parameter of the EZX_START_XFER macro. See Appendix A.1 and A.2 for the ASCII-EBCDIC and the JIS-EBCDIK conversion tables. TACL Macros The application must load the two TACL libraries EZXSETUP and EZXLIB before using the three macros: EZX_START_XFER prepares an EZX transfer. EZX_FREE_MVS_DATASET emergency tool to free MVS dataset. EZX_REMOTE _SUBMIT submits a JCL job to the MVS system. When these macros detect an error, the standard TACL completion code is explicitly set. (:_completion^procdeath:z^completion^code is set to a non-zero value). Here is an example of transfer towards MVS, followed by the triggering of the MVS application that reads the transferred data: LOAD $SYSTEM.EZX.EZXSETUP $SYSTEM.EZX.EZXLIB EZX_START_XFER =TAPE1 & VOLUME DE0001, & FILE ID EXCHANGE.APPL1.TRANS.FILE FUP COPY $DATA15.APPL1.FILE1, =TAPE1, VAROUT EZX_REMOTE_SUBMIT #DE0001J MVS1.JCL.CNTL(JOB02) Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 15 In this example, the Guardian file $ DATA15. APPL1.FILE1 is transferred to an MVS dataset named EXCHANGE.APPL1.TRANS.FILE that already exists. The VOLUME, here DE0001, must be one of the virtual tape volumes defined in the EZX-Gateway catalogue of volumes at setup time. Concurrent transfer must use different volumes. The USE OUT, assumed by default, specifies the transfer direction from NonStop to MVS. Depending on the context of the running TACL session and the completion code of FUP, the OBEY file will continue to execute and the MVS job will be submitted to exploit the transferred data. EZX_START_XFER Macro EZX_START_XFER has syntax similar to TACL ADD DEFINE. This macro runs the EZX program BBCMD to communicate with the NSK EZX Domain Manager and EZX MVS Agent to: Prepare the MVS datasets and create them if requested. Add a TAPE DEFINE in the current TACL process, according to the macro parameters and the information returned by the MVS. Similarly to the TACL ADD DEFINE, the DEFINE must not exist before running the macro. If there is any error: :_completion^procdeath:z^completion^code is set to a non-zero value. The DEFINE is not created. Syntax: EZX_START_XFER =define_name [, attribute value] [, attribute value] … Attributes Related to the Adding of a TAPE DEFINE: BLOCKLEN Number. Optional. Forces the BLOCKLEN attribute in the TAPE DEFINE to be added. Same value range as in regular tape defines. If not specified, the macro will compute the largest BLOCKLEN lower than 32,760 compatible with the format (fix/variable) and record length of the MVS dataset. DEVICE $tape-device Optional, same possibilities as in regular tape defines. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 16 FILEID File name. Mandatory, names the MVS dataset. It also names the tape file in the labels of the virtual volume. Up to 44 characters are supported, even if the actual FILEID is truncated to 17 characters. The virtual HDR1 label will be limited to 17 characters. By convention, a dataset name ending by ".EZX" is a group of datasets of the same characteristics (same DCB) that may span across several DE XP volumes to accommodate a single large transfer size. The actual name of a group of datasets identified by the FILEID "MVS.FILE3.EZX", will be "MVS.FILE3..EZXZ0001", "MVS.FILE3.EZX0002", "MVS.FILE3.EZX0003”, etc. SYSTEM \node-name Optional, same possibilities as in regular tape defines. USE {IN, OUT} Optional, default value is OUT. Same usage as in regular tape defines. VOLUME Tape label. Required, existing virtual tape volume. Attributes Related to the MVS Dataset(s) Creation: R_FCREATE {YES, NO, OVERRIDE} Optional, default value is NO. If YES, the MVS dataset(s) will be created. The macro will fail if the datasets already exist. If OVERRIDE, the existing MVS dataset(s) will be deleted, then new datasets will be created. R_RECFM {F, FB, V, VB} Record format of the MVS dataset to be created. Mandatory, if R_FCREATE is set to YES. R_LRECL Number. Record length of the MVS dataset to be created, as specified in MVS DCB. Mandatory, if R_FCREATE is set to YES. R_BLKSIZE Number. Block length of the MVS dataset to be created, as specified in MVS DCB. Mandatory, if R_FCREATE is set to YES. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 17 R_VOL Disk label Optional, usually not specified. MVS disk volume where the MVS dataset is to be created. Do not specify if a group of datasets spanning several volumes must be created. R_DATACLAS Class-name Optional, MVS DATACLAS of the dataset to be created. R_MGMTCLAS Class-name Optional, MVS MGMTCLAS of the dataset to create. Other Attributes: AVRRECLEN Number of bytes. Optional. Estimated average record length in the Guardian tape file. This is a complement to the TRFSIZE parameter for disk space computations when processing files with variable record format. See TRFSIZE. CONVERSION conversion-id Optional, the supported conversions are ASCII-EBCDIC and JIS-EBCDIK. See Appendix A.1 and A.2. TRFSIZE {number-of-MB | Guardian-file-name} Optional. When R_FCREATE is set to YES, TRFSIZE is the total data size of the MVS dataset(s) to be created. The number of tracks/cylinders is computed according to the disk geometry and the block size of the dataset. The maximum size allocated per MVS dataset is the space specified in the Domain configuration, in the Data Store associated to the tape volume. If the dataset name (FILE ID) ends by ".EZX", EZX will create as many datasets as required (up to 255) to contain the specified size. When R_FCREATE is set to NO, TRFSIZE is an expected transfer size to check against the MVS dataset size. For a transfer from NSK to MVS, the transfer will be rejected if TRFSIZE is higher than the dataset size. For a transfer from MVS to NSK, EZX assumes that the MVS dataset(s) are full and the transfer will be rejected if TRFSIZE is lower than dataset size. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 18 TRFSIZE can be specified as a Guardian-file-name. For transfer from NSK to MVS, TRFSIZE is set to the file aggregate EOF, rounded to the upper MB. For transfer from MVS to NSK, TRFSIZE is set to the aggregate filesize (that includes the potential additional extents), rounded to the lower MB, assuming a file type Entry Sequenced. Notes: The computations with TRFSIZE are approximated, working more straightforwardly with Fixed rather than Variable record format. The computation assumes that TRFSIZE estimates only the pure data, and does not include any header for block or record length Experimentation and manual adjustment might be required especially when the record format is Variable. Adjustments can be done by adjusting the value of TRFSIZE and by specifying the expected average size of a record by AVRRECLEN It is suggested not to specify a Guardian file name when the record format is Variable. Implicit DEFINE Attributes Set by the Macro. CLASS TAPE LABELS ANSI RECFORM F Set to F if the remote MVS dataset is F or FB RECLEN Number. Set to remote MVS dataset LRECL, if it is set to F or to FB. Notes about the MVS dataset to be created: Unit type The value can only be set in the Domain configuration (Data Store tab in the web application) Storage class Optional. Can be set only in the Domain configuration (Data Store tab in the web application) Allocated space Value computed according to the TRFSIZE parameter. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 19 EZX_FREE_MVS_DATASET Macro This macro is reserved to exceptional cases where: An EZX transfer was initiated and did not complete successfully. The MVS dataset(s) are still looked by the MVS EZX agent. There is no 'Current operation' associated anymore to the tape volume. Therefore, manual freeing of the MVS dataset(s) is not possible using the web application. This macro is then the last manual emergency tool to free the MVS dataset(s). It will not change any status on the Guardian and Windows platforms. EZX_FREE_MVS_DATASET FILEID mvs-dsn, & {VOLUME label | STOREID store} FILEID File name. Mandatory, names the MVS dataset. Must be specified as it was set in the EZX_START_ZFER macro. Ends by ".EZX" when a group of datasets was involved in the transfer. VOLUME STOREID Tape label. Identifies the virtual tape volume specified EZX_START_XFER macro that was executed. in the Data Store ID. Identifies the DataStore, as known in the Domain configuration. Either VOLUME or STOREID must be specified to identify (directly or indirectly) the MVS Agent that will execute the dataset freeing. EZX_REMOTE_SUBMIT EZX_REMOTE_SUBMIT submits an MVS remote job whose Job Control Language (JCL) is stored in the remote MVS system. This macro enables the BCOM product. To use different or complex remote job setups, the regular interface to BCOM is used. EZX_REMOTE_SUBMIT #bcom-request-name remote-dataset-name The two parameters are mandatory. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 20 #bcom-request-name The request ID in the local BCOM environment. It begins by “#” and is limited to eight characters. remote-dataset-name The name of the MVS dataset that will be submitted. Tools Reporting the Completion of a Transfer Normally, the NSK tape application is aware of any error occurring in a transfer, because the VTC emulator will return a SCSI sense code when a SCSI command cannot be executed successfully. This sense code is then translated in a Guardian error code returned to the application by the Guardian tape system. However, when an NSK tape application writes to an MVS dataset on a DE XP volume, an error occurred at the very end of the transfer might not be seen by the NSK application program. Inside the VTC emulator, the IO to the DE XP volume are buffered by the FAL library. When a tape application closes the tape file, the VTC emulator receives a write file mark, holds the reply until the FAL buffer is flushed. If there is any error, an error condition is returned to the SCSI write file mark. This error signal can make the writing of trailing labels by $ZSVR fail, but is not reported to the tape application program. The error is known in the VTC that reports the transfer completion statistics and the severity level to the NSK Domain manager. The transfer completion is then forwarded to the MVS AUDIT dataset. To get the status of the transfer’s completion status on the NSK side, two NSK tools are available: o The program GETEVOL[E] displays these statistics and Guardian completion code if any error occurred in processing or in the queried transfer. sets the its own o Two C functions in the NSK library EZXVUTL[E] (getVolumeRecStat() and getVolRecStatWithTapeDefine()) return a structure similar to the record of the AUDIT MVS dataset. The source of the GETEVOLC, providing EZXVUTL[E]. GETEVOL[E] program is distributed in file an example of how to use the library These tools query the catalog of virtual volumes (VOLUME file in the NSK EZX installation subvol) maintained by the NSK Domain manager. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 21 GETEVOL[E] Program GETEVOL[E] sets a completion code in the context of an NSK OBEY file, according to the severity level reported by the VTC at the completion of a transfer. GETVOL[E] always ABENDs (completion code = 5): o When there is any error in the processing of GETEVOL[E]. OR o When the transfer does not complete with a success indication. Incidentally, GETEVOL[E] displays statistics about the queried transfer. Syntax, when the tape volume is identified by a tape DEFINE: RUN GETEVOL[E] wait-time volume-fname define-name wait-time Maximum number of seconds. GETEVOL[E] waits for the end of a transfer not yet completed. volume-fname Name of the VOLUME file in the EZX installation subvol. Can be a DEFINE class MAP. define-name Name of the tape DEFINE prepared by the EZX_START_XFER macro. Syntax, when the tape volume is identified by a volume label: RUN GETEVOL[E] wait-time volume-fname volume-label [dataset name] wait-time Maximum number of seconds. GETEVOL[E] waits for the end of a transfer not yet completed. volume-fname Name of the VOLUME file in the EZX installation subvol. Can be a DEFINE class MAP. volume-label Label of the virtual tape volume, i.e. parameter VOLUME in the EZX_START_XFER macro. dataset name Optional MVS dataset name. If entered, GETEVOL[E] will check that the tape volume is currently associated to this expected dataset name (not case sensitive) Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 22 Sample obey file LOAD /KEEP 1/ $SYSTEM.EZX.EZXSETUP $SYSTEM.EZX.EZXLIB DELETE DEFINE =OUTTAPE EZX_START_XFER =OUTTAPE, VOLUME TAP001, & CONVERSION JIS-EBCDIK, & FILEID MVS.HPJ2.EZX FUP COPY FILE80, =OUTTAPE RUN $SYSTEM.EZX.GETEVOLE 10 $SYSTEM.EZX.VOLUME =OUTTAPE #output completion code=[:_completion^procdeath:z^completion^code] Sample identifying the volume by its label ADD DEFINE =VOL, CLASS MAP, FILE $SYSTEM.EZX.VOLUME RUN $SYSTEM.EZX.GETEVOLE 10 =VOL TAP001 Successful transfer LOAD /KEEP 1/ $SYSTEM.EZX.EZXSETUP $SYSTEM.EZX.EZXLIB DELETE DEFINE =OUTTAPE EZX_START_XFER =OUTTAPE, VOLUME TAP001, & CONVERSION JIS-EBCDIK, & FILEID MVS.HPJ2.EZX <VolumeLabel> TAP001</VolumeLabel> <Conversion>JIS-EBCDIK</Conversion> <FileId> MVS.HPJ2.EZX</FileId> I3112 MVS dataset MVS.HPJ2.EZX ready for transfer through EZX volume TAP001 for \ET103.$Y2L2 SUPER.ETI-NET. DEFINE =OUTTAPE added I4001 MVS Storage size = 2560000 bytes FUP COPY FILE80, =OUTTAPE 20000 RECORDS TRANSFERRED RUN $SYSTEM.EZX.GETEVOLE VOLUME 10 $SYSTEM.EZX.VOLUME : TAP001 LAST OPERATION Guardian node : \ET103 GuardianMountId: 805 Loaded Device : $T911555 Last Revised: Mar. 10, 16 Version 1.58 =OUTTAPE EZX-Gateway System 23 EZX VTC : Operation : Severity : Load time : Unload time : Xfer direction : Existing files : Processed files: Data byte count: Record count : REMOTE DATASET SIM3 TRF_OUT SUCCESS 2005-10-25 10:30:00 2005-10-25 10:30:10 NSK to MVS 1 1 1600000 20000 Dataset Name : MVS.HPJ2.EZX DCB : (RECFM=FB,LRECL=80,BLKSIZE=32000) LOCAL TAPE DEFINE Recform : F Reclen : 80 Blocklen : 32720 #output completion code=[:_completion^procdeath:z^completion^code] completion code=0 Unsuccessful transfer LOAD /KEEP 1/ $SYSTEM.EZX.EZXSETUP $SYSTEM.EZX.EZXLIB DELETE DEFINE =OUTTAPE EZX_START_XFER =OUTTAPE, VOLUME TAP001, & CONVERSION JIS-EBCDIK, & FILEID MVS.HPJ2.EZX <VolumeLabel> TAP001</VolumeLabel> <Conversion>JIS-EBCDIK</Conversion> <FileId> MVS.HPJ2.EZX</FileId> I3112 MVS dataset MVS.HPJ2.EZX ready for transfer through EZX volume TAP001 for \ET103.$Y2L2 SUPER.ETI-NET. DEFINE =OUTTAPE added I4001 MVS Storage size = 2560000 bytes FUP COPY FILE80, =OUTTAPE ERROR - =OUTTAPE ($T911553): ERR 120 *ABEND* RUN $SYSTEM.EZX.GETEVOLE VOLUME 10 $SYSTEM.EZX.VOLUME : TAP001 Last Revised: Mar. 10, 16 Version 1.58 =OUTTAPE EZX-Gateway System 24 LAST OPERATION Guardian node : \ET103 GuardianMountId: 804 Loaded Device : $T911553 EZX VTC : SIM3 Operation : TRF_OUT Severity : ERROR Load time : 2005-10-25 10:28:05 Unload time : 2005-10-25 10:28:20 Xfer direction : NSK to MVS Existing files : 1 Processed files: 1 Data byte count: 2560000 Record count : 32000 REMOTE DATASET Dataset Name : ETI-NET.LSAL.HPJ2.EZX DCB : (RECFM=FB,LRECL=80,BLKSIZE=32000) LOCAL TAPE DEFINE Recform : F Reclen : 80 Blocklen : 32720 ABENDED: 1,1040 #output completion code=[:_completion^procdeath:z^completion^code] completion code=5 Unsuccessfull start of transfer LOAD /KEEP 1/ $SYSTEM.EZX.EZXSETUP $SYSTEM.EZX.EZXLIB DELETE DEFINE =OUTTAPE EZX_START_XFER =OUTTAPE, VOLUME TAP001, & CONVERSION JIS-EBCDIK, & FILEID MVS.HPJ2.EZX <VolumeLabel> TAP001</VolumeLabel> <Conversion>JIS-EBCDIK</Conversion> <FileId> MVS.HPJ2.EZX</FileId> EXZ JOB LS3001 from EZX003 failed to create/query NET.LSAL.HPJ22.EZX: 2 (. TBINFOVOL, rc 8, reason 8 ). FUP COPY FILE80, =OUTTAPE COPY FILE80, =OUTTAPE -- ^ -ERROR - COULD NOT FIND DEFINE. Last Revised: Mar. 10, 16 Version 1.58 ETI- EZX-Gateway System 25 *ABEND* ABENDED: 0,209 RUN $SYSTEM.EZX.GETEVOLE 10 $SYSTEM.EZX.VOLUME =OUTTAPE GETEVOL error=-2, severity=ERROR, errorMessage=DEFINEINFO error=2051 ABENDED: 1,1058 #output completion code=[:_completion^procdeath:z^completion^code] completion code=5 EZXVUTL[E] Library EZXUTL[E] is a static library with two public routines that return the statistics and the severity level of the last transfer executed through a given tape volume. getVolRecStatWithTapeDefine() returns the statistics and severity level of a transfer identified by a tape define in the context of the current TACL process. getVolumeRecStat() returns the same data, identified by a tape label. for a transfer The source of the program GETEVOL (TNS/R) / GETEVOLE (TNS/E) is distributed in GETEVOLC file and is a sample of usage of these two functions. Program and routines are coded in ANSI C, assuming NULL delimited strings. C++ comments (//) are used and must be allowed in the compiling (ALLOW_CPLUSPLUS_COMMENTS pragma) Note about the maxWaitTime call parameter The two functions test for the presence of "PARAM EZXVUTL-MAXIMUM-WAIT number-of-seconds" in the context of the TACL process. If present, this TACL PARAM will override the value received in maxWaitTime parameter. If this TACL PARAM is absent, maxWaitTime values under 30 seconds will be ignored and the function will wait for 30 seconds. The number-of-seconds specified in this PARAM must be in the range 0 to 32767. This note does not apply to GETEVOL[E], although it uses EZXVUTL[E]. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 26 getVolRecStatWithTapeDefine() function int getVolRecStatWithTapeDefine (char * GuardianVolFileName, char *tapeDefine, short maxWaitTime, return_code_def *retCodeStr, /*output*/ volumeInfoDef *volInfo /*output*/ ); Parameter char *GuardianVolFileName In/Out In Description Name of the VOLUME file in the EZX installation subvol. Can be a DEFINE class MAP. char *tapeDefine In Tape DEFINE prepared by the EZX_START_XFER macro for the transfer to query. short maxWaitTime In Maximum number of seconds the routine will wait for the transfer completion and registration before issuing a timeout. return_code_def *retCodeStr Out Structure reporting the processing of the routine. If retCodeStr->severity is zero, the routine executed without any error. If it is not zero, retCodeStr>messageText gives details about the error, and the return code is EZXVUTL_ERROR or NO_COMPLETED_TRANSFER. volumeInfoDef *volInfo Out Structure reporting the transfer statistics and severity level. If volInfo->lastOper.severity = 0, the VTC did not detect any errors in the transfer. If volInfo->currentOperation > OPER_NONE, the volume is still in use by an operation. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 27 getVolRecStatWithTapeDefine() return-codes: Symbolic value Numeric value COMPLETED_TRANSFER NO_COMPLETED_TRANSFER 0 Meaning The routine executed without any error. Check completion in volInfo.lastOper.severity -1 Partial data returned in volInfo. volInfo.lastOper.severity is not applicable. EZXVUTL_ERROR -2 Unable to access the VOLUME record. No data returned in volInfo. getVolumeRecStat () function int getVolumeRecStat (char * GuardianVolFileName, char *tapeVolLabel, char *dataSetName, short maxWaitTime, return_code_def *retCodeStr, /*output*/ volumeInfoDef *volInfo /*output*/ Parameter In/Out char *GuardianVolFileName In ); Description Name of the VOLUME file in the EZX installation subvol. Can be a DEFINE class MAP. char *tapeVolLabel Last Revised: Mar. 10, 16 In Tape volume label associated to the transfer to query. Version 1.58 EZX-Gateway System 28 char *dataSetName In Optional name of the IBM dataset. If this address is not NULL, the routine will check that *datasetName is the latest transferred MVS dataset through the requested tape volume label. short maxWaitTime In return_code_def *retCodeStr volumeInfoDef *volInfo Maximum number of seconds the routine will wait for the transfer completion and registration before issuing a timeout. Out Structure reporting the processing of the routine. If retCodeStr->severity is set to zero, the routine executed without errors. If it is not zero, retCodeStr>messageText gives details about the error and the return code is EZXVUTL_ERROR or NO_COMPLETED_TRANSFER. Out Structure reporting the transfer statistics and severity level. If volInfo->lastOper.severity = 0, the VTC did not detect any errors in the transfer. If volInfo->currentOperation > OPER_NONE, the volume is still in use by an operation. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 29 getVolRecStatWithTapeDefine() return-codes: Symbolic value COMPLETED_TRANSFER Numeric value Meaning 0 The routine executed without any error. Check completion in volInfo.lastOper.severity NO_COMPLETED_TRANSFER -1 Partial data returned in volInfo volInfo.lastOper.severity is not applicable. EZXVUTL_ERROR -2 Unable to access the VOLUME record. No data returned in volInfo. Sample usage error = getVolRecStatWithTapeDefine (GuardianVolFileName, tapeVolLabel, maxWaitTime, &retCodeStr, &volInfo); switch (error) { case COMPLETED_TRANSFER: /* tape volume was loaded and unloaded */ if (volInfo.currentOperation <= OPER_NONE) { /* transfer completion was reported to IBM */ if (volInfo.lastOper.severity == NO_SEVERITY) { /* everything completed with success */ else /* error occured during the data transfer */ } } break; case NO_COMPLETED_TRANSFER: /* tape volume was not loaded and unloaded */ break; case EZXVUTL_ERROR: /* function did not execute correctly */ Break; } /* end switch */ Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 30 Header file //******************************************************** // // file : EZXVUTL.h // Description: EZX VOLUME UTILILITY external header file // //******************************************************** #ifndef ZSYS_VAL_LEN_FILENAME #define ZSYS_VAL_LEN_FILENAME 47 #endif #define TRUE 1 #define FALSE 0 #define #define #define #define #define #define #define #define #define #define NO_SEVERITY 0 WARNING 2 ERROR 3 FATAL 4 ABEND 5 TXT_NO_SEVERITY TXT_WARNING TXT_ERROR TXT_FATAL TXT_ABEND #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define TXT_RECFORM_VARINOUT "VARINOUT" TXT_RECFORM_F "F" TXT_RECFORM_U "U" RECFORM_VARINOUT 1 RECFORM_F 2 RECFORM_U 3 BBEZX_MVS_TO_NSK 2 BBEZX_NSK_TO_MVS 1 TXT_OPER_NONE "" TXT_OPER_UNKNOWN "" TXT_OPER_LOAD "LOAD" TXT_OPER_EXPORT "EXPORT" TXT_OPER_IMPORT "IMPORT" TXT_OPER_TRFIN "TRF_IN" TXT_OPER_TRFOUT "TRF_OUT" TXT_OPER_POSTTRF "POST_TRF" OPER_UNKNOWN 0 OPER_NONE 1 OPER_LOAD 2 OPER_EXPORT 3 Last Revised: Mar. 10, 16 "SUCCESS" "WARNING" "ERROR" "FATAL" "ABEND" Version 1.58 EZX-Gateway System 31 #define #define #define #define #define OPER_IMPORT 4 OPER_TRFIN 5 OPER_TRFOUT 6 OPER_POSTTRF 7 OPER_LAST_DEVICE 99 #define BB_CARDMODEL_LEN 30 #define BB_DOMAINID_LEN 8 #define BB_DOMAINKEY_LEN 30 #define BB_LICENSEKEY_LEN 255 #define BB_BACKBOXID_LEN 30 #define BB_LABELTYPE_LEN 10 #define BB_STOREID_LEN 30 #define BB_STOREFOLDER_LEN 1024 #define BB_TCP_ADDR_LEN 255 #define BB_TSM_NODE_LEN 64 #define BB_TSM_PASSWORD_LEN 140 #define BB_TSM_MC_LEN 30 #define BB_VOLGROUPID_LEN 30 #define BB_GUARDIANNODE_LEN 8 #define BB_GUARDIANDEVICE_LEN 8 #define BB_GUARDIANUSERNAME_LEN 32 #define BB_GUARDIANUSERID_LEN 20 /* ASCII representation of userid: nnnn,nnnn */ #define BB_WINDISK_USER_LEN 30 #define BB_WINDISK_PSWD_LEN 60 #define BB_SCRIPT_NAME_LEN 1024 #define BB_SCRIPT_PARAM_NAME_LEN 32 #define BB_SCRIPT_PARAM_VALUE_LEN 256 #define ZSYS_VAL_RCV_IOTYPE_SYSTEMMSG 0 #define BB_KEY_LEN 64 #define BB_WIN_DEVICE_LEN 64 #define BB_GUARDIANDEVICE_LEN 8 #define BB_DEXPVOLUME_LEN 6 #define BB_DEXP_EMUL_LEN 15 #define BB_MVSDSN_LEN 44 #define BB_MVSUSERID_LEN 8 #define BB_ACCESSUSERID_LEN 30 #define BB_NULL_PATH "K:\\UNSPECIFIED_BBPATH\\" #define BB_EZX_OPER_LEN 9 #define BB_EZX_MAX_FILES_PER_TRF 255 #define BB_EZX_CONVID_LEN 30 #pragma section ezxvutl_return_code #define COMPLETED_TRANSFER 0 /* check completion in lastOPer.severity */ #define NO_COMPLETED_TRANSFER -1 /* partial data returned, severity is not applicable */ #define EZXVUTL_ERROR -2 /* unable to access the VOLUME record */ Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 32 #pragma section ezxvutl_defines #define EZXVUTL_MAXIMUM_WAIT "EZXVUTL-MAXIMUM-WAIT" #pragma section return_code_def #pragma fieldalign shared2 __return_code typedef struct __return_code { int error; short severity; char messageText[4096]; } return_code_def; #pragma section volumeid #pragma fieldalign shared2 __volumeid typedef struct __volumeid { char labelPrefix[3]; char label[7]; } volumeid_def; #pragma section bb_timestamp #pragma fieldalign shared2 __bb_timestamp typedef struct __bb_timestamp { short timeElement[8]; } bb_timestamp_def; #pragma section dexp_packed_file typedef struct __dexp_packed_file { char DEXPVolume[BB_DEXPVOLUME_LEN]; char diskModel; unsigned long trackCount; } dexp_packed_file_def; #pragma section ezxinfo typedef struct __ezxinfo{ short mvsConnected; short xferDirection; long fileCount; long processedFileCount; long long trfSize; /* estimate */ long long dataByteCount; long long recordCount; char convId[BB_EZX_CONVID_LEN+1]; struct _remote { unsigned short lrecl; long blksize; Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 33 char char char } remote; struct _local { short unsigned short long } local; dexp_packed_file_def } ezxInfoDef; recfm[5]; dataset[BB_MVSDSN_LEN+1]; vol[7]; recform; reclen; blocklen; file[BB_EZX_MAX_FILES_PER_TRF]; #pragma section volume_info_def typedef struct __volumeInfoDef { volumeid_def volumeid; bb_timestamp_def creationTime; short currentOperation; struct { long long readByteCount; int guardianMountId; int error; short operationType; short severity; bb_timestamp_def startTime; bb_timestamp_def loadTime; bb_timestamp_def unloadTime; char guardianNode[BB_GUARDIANNODE_LEN+1]; char loadedDevice[BB_GUARDIANDEVICE_LEN+1]; char EZX_VTC[BB_BACKBOXID_LEN+1]; char accessUser[BB_ACCESSUSERID_LEN+1]; } lastOper; ezxInfoDef ezxInfo; }volumeInfoDef; int getVolumeRecStat (char * GuardianVolFileName, char *tapeVolLabel, char *dataSetName, short maxWaitTime, return_code_def *retCodeStr, /*output*/ volumeInfoDef *volInfo /*output*/ ); int getVolRecStatWithTapeDefine (char * GuardianVolFileName, char *tapeDefine, short maxWaitTime, return_code_def *retCodeStr, /*output*/ volumeInfoDef *volInfo /*output*/ ); int BBSVUT_TimeStampGmtToLocalEdited1 (char *fieldName, bb_timestamp_def *gmt, char *outStr); Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 34 MVS Application Interface Besides the dataset (written or read by the transfers), the only available EZX interface on the MVS platform is a control file accessible by program. This control file contains transfer statistics that can be verified by the MVS application involved in the data transfer. Datasets Read or Written by EZX Transfers The MVS dataset must be catalogued in the MVS file system catalog. To accommodate transfers whose data size exceeds the size of a DE XP volume, the MVS data must be split into several MVS datasets, all with the same DCB. Such a group of continuation datasets must have a name ending by ".EZX0001", ".EZX0002", etc… On the NonStop platform, this group is identified by a “name pattern”, a name ending by ".EZX". Note that the ".EZX" name end is reserved and cannot be used to identify an MVS dataset involved in an EZX transfer. A group is composed of a maximum of 255 datasets. For transfers from NonStop to MVS, the JCL concatenation of all datasets on a single DD statement allows the receiving MVS application to process a single logical file. For transfers from MVS to NonStop, the MVS application is responsible for preparing a set of datasets on the DE XP volumes. Supported dataset characteristics: o Organization: sequential only (DSORG=PS) o RECFM: F, FB, V or VB o Single volume dataset During a transfer, the MVS dataset(s) involved in the transfer is(are) locked by the EZX MVS Agent. If the transfer direction is towards MVS, the lock is exclusive. If not, the lock allows sharing. The EZX MVS Agent rejects two consecutive locks without intermediate unlocks, unless the second lock comes from the same EZX Domain ID and from the same tape volume. In this later case, the second lock is considered as a restart after a failure. Note that failures are normally monitored by EZX and the sequence of lock and unlock is regular. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 35 Description of the Control Dataset The default dataset name of this control file is BCOM.BRMV40.EZXAUDIT. There is a record per transfer. The key is the MVS dataset name. For transfers involving a group of datasets, the dataset name is the name pattern ending by ".EZX" and the statistics correspond to the total of the datasets of the group. File is a VSAM KSDS and is accessed using VSAM records I/O methods. All character fields are in EBCDIC, padded with blanks when necessary and are not null-terminated. A record from a previous execution is deleted at the beginning of the transfer; new records are created at the end of the transfer. typedef struct EZX_AUDIT_RECORD { /* key starts at offset 0 and is 44 bytes BTT June-27-2005 */ char dsn[44]; /* the MVS Dataset Name */ char domainId[8]; /* EZX Domain Manager id */ char jobname[6]; /* Guardian tape volume */ char guardianNode[8]; /* Tandem node using the Tape device */ char xferDirection; /* 0x01: NSK2MVS, 0x02: MVS2NSK*/ char _futuruse_1[5]; /* reserved and alignment */ struct { short severity; /* 0x00=OK, 0x02=warning, 0x03=error, 0x04=fatal */ /* note: an ABEND in the NSK tape application is not seen by EZX, this severity corresponds to transfer seen by the tape emulator in VTC */ char startTime[34]; /* yyyy-mm-ddThh:mm:ss.thmsns-ZZ:ZZ*/ char endTime[34]; /* yyyy-mm-ddThh:mm:ss.thmsns-ZZ:ZZ*/ short filecount; /* number of existing MVS datasets */ short processedFilecount; /* datasets accessed during the transfer */ char _futuruse1[6]; long long recordCount; /* data records transferred */ long long dataByteCount; /* data bytes, excluding the LLZZ fields containing record and block lengths */ } result; char futuruse2[40]; }EZX_AUDIT_RECORD; Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 36 Installation The table below provides a summary of the sequence of steps necessary in order to install the ETI-NET components of an EZX-Gateway solution. The VT Controllers are usually delivered with controller cards and ETI-NET software already installed. If needed, an installation procedure of the EZX software for Windows is included in the distribution CD. EZX Installation Step 1. Design the EZX Network Topology Description Design the network topology for the VT Controller(s), the Domain Manager, and the IIS control paths. Updates to the TCP/IP network and firewalls depending on your site setup might be required. In some production environments, these changes might require advanced planning. 2. Configure the TCP/IP LISTNER for the Domain Manager Modify PORTCONF file and restart the LISTNER. 3. Install the EZX hardware Unpack and set up the EZX unit. 4. Install and test the HP XP software Refer to HP XP documentation. 5. Install the Guardian software Extract the EZXvvv PAK file. 6. Define the virtual devices in Guardian Configure the virtual devices in Guardian with Guardian SCF commands. Last Revised: Mar. 10, 16 In some production environments, these changes might require advanced planning. Executes a transfer with HP FCU utility. Version 1.58 EZX-Gateway System 37 Step 7. VT Controller internal emulator configuration Description The internal VTC configuration is normally not modified for SCSI connection. Contact ETI-NET Technical Support to change this configuration. The DE XP volumes are automatically discovered by the EZX software at startup. Changes in the DE XP configuration only require a restart of the two Windows services: VTC Admin and VTC Virtual Tape Devices. Refer to: - Virtual Tape Controller Preparation Notes about the prerequisites in Windows 2003: Installation procedure for the SCSI card and it’s driver. Installation procedure for the FC-SCSI Router and its firmware. - VT Controller Software Installation Procedure for installing ETI-NET application in a VTC unit. Related ETI-NET Documentation: -BCOM for MVS V5 User’s Guide -BCOM for NSK Guardian V5 User’s Guide -ETI-NET Messages Manual -BCOM NSK – EZX Installation Guide -BCOM OS390 – EZX Installation Guide -BCOM OS390 – EZX Upgrade Procedure 8. Set up the Domain Manager address for each VTC Update the Domain Manager address through the Web User Interface for each VTC. 9. Configure the EZX Domain Define the VTCs, their virtual devices, the Data Stores and the Volume Groups through the Web interface. 10. Configure and start the EMS Extractor on each Guardian node where a virtual tape drive is configured. Update the BBEXTCFG Guardian file using TEDIT utility. Start BBEXT. 11. Customize the Guardian TACL macros Update the EZXSETUP Guardian file using TEDIT utility. 12. Set up for recovery Prepare for the recovery of the virtual volume catalog and of the Domain configuration in case of file loss or site disaster. Last Revised: Mar. 10, 16 Optional: Use the Guardian SCF Kernel to define the EMS Extractor as an application process started automatically at each system boot. Version 1.58 EZX-Gateway System 38 1. Design the EZX Network Topology All the control commands between the EZX components are carried over TCP/IP. The Domain Manager accesses remote Guardian services over Expand to respect the local security settings. The Domain Manager accesses remote nodes over Expand to get the MEDIACOM status of virtual devices and the details of pending mounts. The MEDIASRV information is used to manage mount requests. It is also displayed on the Web Home page upon interactive request. Network Topology Configuration a. Select the Guardian node that will host the Domain Manager. b. Assign to each VTC a permanent TCP/IP address. c. Decide on IIS functionality if more than one VTC is part of the topology. If one VTC can be favoured for regular interactions with the Domain Manager, each VTC IIS must remain available for an exceptional local setup operation: set Domain address. d. BCOM: Decide how many NonStop servers will host a BCOM environment and how many servers and requesters per environment there will be. e. As BCOM is only used for remote jobs, there are no massive transfers to spread across several BCOM servers and requesters. At least one server and one requester per environment should be set in order to allow remote jobs to be initiated from both NonStop and MVS sides. f. EZX Agent on MVS: one additional TCP/IP port per BCOM MVS environment is reserved for EZX functionality inside the BCOM framework. g. Revise the TCP/IP traffic for local network routing and firewalls. EZX port numbers are configurable. See the TCP/IP Traffic Port Configurations in the following table, for default port configurations. TCP/IP Traffic Port Configurations Client Server Standard Port Workstation (Web User Interface) VTC (ISS Web server) VTC (Web application) NonStop (Domain Manager) 4561 NonStop (EMS Extractor) NonStop (Domain Manager) 4561 Last Revised: Mar. 10, 16 Version 1.58 80 EZX-Gateway System 39 Client Server Standard Port Workstation (Windows Remote Desktop client) VTC (Windows Remote Desktop server) 3389 Nonstop (Domain Manager) VTC (Emulator service) 8765 Nonstop (Domain Manager) VTC (Administrative service) 8766 Nonstop (Domain Manager) MVS (EZX Agent in BCOM server) 1965 Nonstop (BCOM requester) MVS (BCOM server) A single MVS IP port serves all remote requesters MVS (BCOM requester) Nonstop (BCOM server) A distinct NSK IP port per NSK server Considerations about the Scope of a Domain Number of Nodes per EZX Domain The number of nodes has no hard-coded limit, but more than about five to ten nodes might slow down the response time of some operations of the Web User Interface and the host processing for loading a volume, all depending on the performance of Expand. Adding nodes to a Domain also creates dependencies across nodes. Number of EZX Domains per Node It is possible to concurrently operate several EZX domains per node; each domain must have its own and separate: Virtual tape drive address (bus + target ID) Domain Manager (distinct TCP/IP port) Domain disk subvol (catalog and configuration) EMS Extractors (BBEXT processes) Number of EZX Domains per EZX VT Controller It is possible to concurrently operate several EZX domains in a single VTC. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 40 2. Configure the TCP/IP LISTNER for the Domain Manager The Domain Manager program file BBSV is started by the Guardian LISTNER for each service request. BBSV must be defined to the LISTNER. a. Update the TCP/IP PORTCONF file with Guardian tools. Below is an example of a PORTCONF file, where $DATA05.BBOX.BBSV is the program name and 4561 is the assigned port. ftp $system.zTCP/IP.ftpserv finger $system.zTCP/IP.fingserv 7 4561 $system.zTCP/IP.echoserv $data05.BBOX.BBSV Phiwsock $DSMSCM.ZDSMSCM.PDPEXE b. Restart the Guardian LISTNER process. 3. Install the VTC Hardware a. Connect the VTC to a NonStop server with a Fibre or SCSI cable. b. Connect the VTC to the Ethernet network. c. Connect the VTC to the XP Array d. Log on to the VTC operating system to set a permanent TCP/IP address for the VTC. 4. Install HP XP Software and Test the XP Connection Install the HP software for XP Array, including FAL and FCU. Execute a transfer with the FCU utility. 5. Install the Guardian Software Upload the PAK file EZXvvv (EZX153 for V1.53), with binary transfer, to the Guardian node where the Domain Manager is installed. Content of the EZXvvv File BBCMD Client program run by the EZX_START_XFER macro BBCMDE Itanium TNS/E version of BBCMD BBEXT EMS Extractor program BBEXTE Itanium TNS/E version of BBEXT Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 41 BBEXTCFG EMS Extractor configuration BBSV Domain Manager program BBSVE Itanium TNS/E version of BBSV BBSVCFG Startup Domain configuration EMSFILT1 Source EMS filter used by BBEXT EMSFILT2 Object EMS filter used by OEMS EMSFUPIN FUP source used in the TACL OEMS EZXLIB TACL macro library, contains macro code EZXSETUP TACL macro, contains TACL variables to customize EZXVUTL C library reporting the completion of a transfer EZXVUTLE Itanium TNS/E version of EZXUTL EZXVUTLH Header file for EZXVUTL/EZXVUTLE GETEVOL Utility reporting the completion of a transfer GETEVOLC Source of GETEVOL/GETEVOLE GETEVOLE Itanium TNS/E version of GETEVOL MACROS TACL macro to browse the Domain Manager traces OEMS Obey file to extract EMS messages related to tapes OEMSFILT Object EMS filter generated/used by BBEXT OEXT Obey file to manually start the EMS Extractor OEZX1 Sample Obey file executing a transfer OEZX2 Sample Obey file executing a transfer OPER Data file storing the latest volume load SCFIN1 Registration of the EMS enables an automatic startup SCFIN2 Virtual tape devices definition STATE Storage of various EZX states TAPERD Performance test utility to read from IBM-MVS TAPERDE Itanium TNS/E version of TAPERD TAPEWR Performance test utility to write to IBM-MVS TAPEWRE Itanium TNS/E version of TAPEWR UTFINFO File info utility used in TACL macros UTFINFOE Itanium TNS/E version of UTFINFO VOLUME Empty virtual volumes catalog VOLUME0 Alternate key file for VOLUME Last Revised: Mar. 10, 16 Version 1.58 Extractor to SCF, which EZX-Gateway System 42 Guardian TACL Commands for a first installation > UNPAK EZXvvv, *.*.*, LISTALL, MYID, OPEN, AUDITED, MAP NAMES *.*.* TO $<disk>.<subvol>.* Guardian TACL Commands for an update from a compatible version The suggested procedure consists in: Stopping the extractor Backing up the whole old EZX subvol Restoring the new programs to overwrite the old version 1. stoping the extractor > STOP $BBEXT (or SCF ABORT PROCESS $ZZKRN.#BBOXEXT if the extractor was registered in the NSK Kernel) 2. backing up the whole old EZX subvol > PAK BACKUP.EZXVxxx, ($<disk>.<subvol>.*), & AUDITED,OPEN,LISTALL 3. restoring the new programs overwriting old version > UNPAK EZXyyy, *.*.* WHERE FILECODE = 700 OR FILECODE = 800, LISTALL, MYID, OPEN, AUDITED, MAP NAMES *.*.* TO $<disk>.<subvol>.* & & 4. start the extractor > OBEY OEXT (or SCF START PROCESS $ZZKRN.#BBOXEXT if the extractor was registered in the NSK Kernel) TMF Protection of the Disk Files: These files are distributed with the AUDIT attribute, as it is suggested to protect them by TMF: STATE VOLUME (and VOLUME0) The other data files, including OPER, cannot be audited by TMF. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 43 Security Notes: The Domain Manager BBSV is started by the Guardian LISTNER, with SUPER.SUPER as User ID (by default) If the Web User Interface establishes the TCP/IP connection, a Guardian login is executed with the user name and the password entered by the user. Other TCP/IP connections initiate a BBSV process that will not execute a login, and will execute with SUPER.SUPER: The EMS extractor BBEXT sends load requests. The client BBCMD sends requests to prepare the MVS datasets. The VTCs provide asynchronous data or updating the state of virtual volumes. feedback for logging in EMS Any missing data file, except BBSVCFG, is recreated empty on the fly by BBSV, with the default security of the running User ID. This default security is often not adequate and must be reviewed. Any BBSV session must have these minimal authorizations: Read access to the BBSVCFG file. Read/write access to the VOLUME and VOLUME0 files. Authority to start MEDIASERVE on all Guardian nodes processed in the session and to execute query commands. A BBSV session initiated by the EMS Extractor BBEXT or by a VTC must also have these authorizations: Read/write access to the OPER and the STATE files A BBSV session initiated by an interactive user must have additional authorizations depending on the executed functions: Update of the Domain configuration requires Delete/Write access BBSVCFG. Restriction to delete/write authorization is recommended. to Manual volume load requires Read/write access to the OPER and STATE files. Creation and deletion of virtual volumes catalogued in Guardian requires a user in the SUPER group and read/write access to the STATE file. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 44 6. Define the Virtual Devices in Guardian SCSI Connection The following SCF command is an example of the configuration for two virtual tapes drives in a SCSI PMF CRU setup. DEVICEID refers to the SCSI target ID. Devices connected to a SCSI host port usually do not require any corresponding hardware configuration inside the VT Controller. They simply need to be registered in the Domain configuration, by using the Web application described in the second part of this manual. ADD TAPE $VT553, & SENDTO STORAGE, & DEVICEID 3, & LOCATION (1, 1, 55) ADD TAPE $VT554, & SENDTO STORAGE, & DEVICEID 4, & LOCATION (1, 1, 55) Fibre connection The following SCF command is an example of the configuration for a virtual tape drive that connects to a Fibre port on the NSK host. ADD tape $t911501, & SENDTO STORAGE , & BACKUPCPU 2, & PRIMARYCPU 1, & LOCATION (111,3,2), & SAC 1, & PROGRAM $SYSTEM.SYSTEM.OTPPROCP , & PORTNAME 2100001086129884 , & lun 1 Devices connected to a Fibre host port require corresponding hardware configuration in routers and / or in the VT Controller. They also need to be registered in the Domain configuration. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 45 7. VT Controller Internal Emulator Configuration This configuration enables the emulator response to a list of buses, SCSI target IDs, and LUNs. By default, the distributed configuration responds to SCSI IDs 0 to 5 for all included SCSI connectors. There is no need to change this configuration for SCSI connections. 8. Set Up the Domain Manager Address for Each VT Controller Each VTC includes a Microsoft IIS that serves the Web User Interface. If the VTC software has been installed with default values, a Microsoft IE browser can access a VTC Web User Interface at the following URL: http://VTC-address/Admin. For regular sessions with the Domain Manager, the session is initiated by a Guardian logon, and any VTC set for the Domain can be accessed. For a setup of the Domain Manager addresses, the VTC to setup must be addressed by the URL http://VTC-address/Admin. The session is controlled by a Microsoft Windows logon in this VTC. The address of the Domain Manager is stored in the VTC for three purposes: Set the destination of the Web User Interface requests to the Domain Manager, such as the Guardian sign on, the creation of virtual volumes, the query of the device status in Guardian, or the manual load of a volume. Set the destination of asynchronous data feedback initiated by a VTC: virtual volume state and log messages to propagate to the Guardian EMS subsystem. Filter incoming control requests. Incoming control requests that do not origin from one of the Domain Manager addresses will be rejected. If the Domain Manager can be seen as a TCP/IP partner on several addresses, all of these addresses must be registered. a. Choose an EZX Domain name to store on the VTCs. This same Domain name will also be entered in the following installation step 8 in order to be stored on the NonStop server. b. Connect to each VTC, via a Web User Interface, using the address: http://VTC-address/Admin c. Select the Domain Address tab (the default tab is the Sign in tab) d. When prompted for a User name and a Password, enter a user in the Administrators group, or in the BACKBOX_MANAGERS group of Microsoft Windows operating system. e. Enter by domain: The Domain name The Domain Manager IP address(es) Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 46 The Domain Manager IP port The propagation of EMS messages to EMS Note: Refer to details and screen captures in the Web User Interface section of this manual. 9. Configure the EZX Domain The EZX Domain configuration defines the VT Controller(s), their virtual devices, the Data Stores, and the Volume Groups. This configuration is updated through the Web User Interface. Note: For a full description of this process, please see Configuration, in the Web User Interface section of this manual. The configuration can be found in the BBSVCFG file, which contains XML syntax. This file is located in the same disk subvol as the Domain Manager program BBSV. Domain There are a few global attributes in the Domain. The Domain name must be entered; this Domain name must match the name entered in the VTCs (in the installation step 7) before creating and using virtual volumes. VT Controllers and Virtual Devices The VTC configuration defines the VTC units present in the Domain and their SCSI attachments to Guardian nodes or to Fibre-SCSI converters. Note: Define the devices in Guardian using SCF define the devices in the EZX Domain configuration. commands before you One to six virtual devices (SCSI ID 0 to 5) can be configured per dedicated SCSI connection. The SCSI connection on the VTC is referred to as the Virtual Bus number in the configuration panel and is identified by a physical label close to the SCSI connector. Configuration of Additional Devices on the Same Bus Reduces the conflicts for allocating tape devices that cannot be shared. Maximizes the use of the available bandwidth of the SCSI bus. Increases the overhead in the SCSI bus, even if extra devices are unused. Data Stores In the parent EZX-Gateway software, a Data Store is a data repository for virtual tape volumes. In EZX, a Data Store corresponds to a collection of Data Exchange (DE) XP volumes that will be accessed by the FAL API. Two entities must be created to configure a Data Store in a Domain. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 47 The Data Store itself. Most attributes depend on the Data Store type. A The routes to the Data Store. A route is a VTC that can access the Data Store, i.e. which is connected to the DE XP volumes associated to the Data Store. Volume Groups A volume group is a group of volumes that share the same set of attributes. Attributes Data Store in which the tape image is kept. Authorized access to the volume. 10. Configure and Start the EMS Extractor Each Guardian node where a virtual device is operating must run the EMS Extractor program file BBEXT, as a permanent process. BBEXT receives the new tape mounts from EMS events and regularly checks in the list of virtual volumes pending mounts to see whether there are any pending mounts of which BBSV was not aware of, through EMS event. This periodic check is executed every failsafe-retry-interval. For every new pending mount, a load command is sent to the Domain Manager. When BBEXT receives a device busy reply, it retries the load every busycheckretry-interval seconds. The load is also attempted when an unload EMS event is received. When max-busycheck-retries is reached, the retries are only executed at the failsafe timer below. When BBEXT receives a severe error reply, it retries the load every failsafe-retryinterval seconds. The retries executed at failsafe timer stop when max-failsafe-retries is reached. A new load attempt can only be executed manually, through the Web User Interface. Restarting BBEXT is another mean to restart the loop of retries for all pending mounts. The EMS extractor is also used as a triggering mechanism to retry the TCPIP communication with the MVS system to report the control information of a for POST_TRF tape volumes. Every <volume-scan-interval> seconds, a message is sent to the Domain manager that will retry the communication to MVS. Usually, only the EMS extractor running on the same node as the Domain manager is configured to initiate retries to connect to the MVS system. There are two types of scan:  at BBEXT startup and every 24h after BBEXT startup, all records of the VOLUME file are browsed Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 48  each <volume-scan-interval> seconds, only the OPER file is browsed. The OPER file contains a special pointer record for each VOLUME record that is in state POST_TRF BBEXT Configuration File BBEXT reads its configuration from its standard input file. It expects the following XML syntax: <BACKBOX-EMS-EXT-CONFIG> <awaitio-timeout>600</awaitio-timeout> <max-failsafe-retries>-1 </max-failsafe-retries> <failsafe-retry-interval>900</failsafe-retry-interval> <max-busycheck-retries>-1</max-busycheck-retries> <busycheck-retry-interval>120</busycheck-retry-interval> <BBSV-tcp-addr>127.0.0.1</BBSV-tcp-addr> <BBSV-tcp-port>4561</BBSV-tcp-port> <trace-on>0</trace-on> <trace-file>$data05.bbox.bbexttrc</trace-file> <emsCollector>$0</emsCollector> <emsFilter>$DATA15.lsBBOX.EMSFILT1</emsFilter>  <GuardianDefine> <name>=TCP/IP^PROCESS^NAME</name> <File>$ZTC0</File> </GuardianDefine> </BACKBOX-EMS-EXT-CONFIG> Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 49 Tag Definitions <awaitio-timeout>: Maximum waiting time (in seconds) for a response from the Domain Manager. <max-failsafe-retries>: Maximum number of time a volume load is retried after an error or after max-busycheck-retries is reached. Value 0 to suppress any retry. Value -1 to get infinite retries. <failsafe-retry-interval >: Delay (in seconds) between two checks of pending mounts. <max-busycheck-retries>: Maximum number of times a volume load is retried when no virtual device is free. Value 0 to suppress any retry. Value -1 to get infinite retries. <busycheck -retry-interval >: Delay (in seconds) between two retries to load a volume on a busy virtual device. <BBSV-tcp-addr>: Domain Manager address. <BBSV-tcp-port>: Domain Manager port. <trace-on>: Enables an internal trace (if not zero) <trace-file>: Guardian file name of an edit file for the trace. An existing file is extended and a missing file is created. <emsCollector>: EMS collector from which events are extracted. <emsFilter>: EMS distributor filter that limits the number of events that are passed to BBEXT. The distributed filter does not need to be modified. <volume-scan-interval>: Delay (in seconds) between two checks of the status of tape volumes. The communication with MVS will be retried for POST-TRF volumes. Value 0 to suppress any retry. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 50 This value should be set only in the BBEXT running on the same node as the Domain manager. <GuardianDefine>: Sets the required TCP/IP defines to communicate with the Domain Manager. <Name>: Name of the TCP/IP Define. <File>: File name for the TCP/IP Define. Sample BBEXT Startup BBEXT must run under a Guardian User ID in the SUPER group. This sample is available in the distributed OEXT obey file. RUN BBEXT /IN BBEXTCFG, NOWAIT, NAME $BBEXT/ Automatically Start BBEXT BBEXT can be started automatically by the Guardian system at each system boot. Below is a sample SCF command to register BBEXT and initially start it. ADD PROCESS $ZZKRN.#BBOXEXT, & PROGRAM $DATA05.BBOX.BBEXT,& NAME $BBEXT, & AUTORESTART 3, CPU FIRST, & & HOMETERM $ZHOME, & INFILE $DATA05.BBOX.BBEXTCFG, & STARTMODE APPLICATION, & USER ID SUPER.OPER START PROCESS $ZZKRN.#BBOXEXT 11. Customize the NSK TACL Macros TEDIT the EZXSETUP text file to customize the execution of TACL macros. 12. NSK Test Programs TAPERD and TAPEWR (TAPERDE and TAPEWRE for TNS/E) are support tools that can be used to test the EZX environment, especially to test the performance excluding the NSK local ios. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 51 TAPERD TAPERD reads data from the specified TAPE DEFINE. Read data is simply discarded. The record length of the MVS dataset can be either fix or variable. RUN TAPERD =tapedef blocklen =tapedef specifies the TAPE DEFINE to read Blocklen specifies the length of IOs posted by TAPERD TAPEWR TAPEWR generates blocks of data and writes them to the specified TAPE DEFINE. The MVS dataset must have variable length record format. The blocks written by TAPEWR to tape will have the VAROUT format. RUN TAPEWR =tapedef blocklen VolumeSizeInMB minRecordLenInBytes maxRecordLenInBytes =tapedef Specifies the TAPE DEFINE to write on Blocklen Specifies the length of IOs posted by TAPERD VolumeSizeInMB Number of MB of data to write minRecordLenInBytes Minimum record length to write maxRecordLenInBytes Maximum record length to write Sample OBEY file for TAPEWR, which writes 500 MB of data: CLEAR ALL LOAD /KEEP 1/ EZX.EZXSETUP EZX.EZXLIB DELETE DEFINE =TAPE1 EZX_START_XFER =TAPE1, VOLUME EZX001, & BLOCKLEN 56000, FILEID MFS.FILE.NAME, USE OUT RUN EZX.TAPEWR =TAPE1 56000 500 100 200 Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 52 13. Set Up for Recovery To recover an EZX environment in the event of a site disaster or of a simple file loss, the two groups of data, part of the EZX application, must be considered: The data on NonStop server(s), the Domain Manager configuration and catalog and one or several configurations for EMS Extractor(s). The configuration data kept in the VT Controller(s) In a multi domain environment, the data of each domain must be recovered separately, with its own complete processing environment. Refer to “Considerations about the scope of a Domain” in “Network Topology Configurations” of the Installation section, for multi-domain and multi-nodes environments. Data on the NonStop Servers Save the configuration file BBSVCFG, of the EZX domain, as well as the EMS extractor configuration file BBEXTCFG for each running EMS Extractor. These two text files contain configuration information and are only updated when the user enters configuration changes. Save the catalog of virtual volumes, stored in two Inscribe files: VOLUME0. These files are required to re-execute transfer OBEY files. VOLUME, As the latest version of VOLUME* files are not required to execute EZX transfers, a recovery could start with an empty VOLUME and simple instructions to recreate the same volume labels in the same volume groups. A two-fold protection is suggested: a. Each time the Domain configuration is changed, or the list of virtual volumes is changed: b. Save the whole domain subvol using BACKUP or PACK. c. Save the configuration BBSVCFG in a separate text file available for browsing to workstations. d. Enable the TMF protection on the VOLUME* files. Configuration Data on Each VT Controller a. The internal emulation configuration is in the VTConfig.txt and BBSL.OPT text files. b. The TCP/IP address of the EZX Domain Manager must be set in the recovery VTC. In case of site recovery, this address will typically be different from the address in the original production site, and will be set the same Web User Interface page that was used at installation time. The recovery uses manually recorded information. Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 53 Operations Basic EZX operational procedures are presented below. VT Controller Startup 1. Stop all the virtual NSK tape devices with the Guardian SCF command: TACL> SCF STOP TAPE $VT55* 2. Power on the VTC unit. 3. Wait for the following two EMS messages to be displayed on the Guardian node where the EZX Domain Manager is installed: BBOX-103 Service started (VTC Virtual Tape Devices) BBOX-103 Service started (VTC Admin) 4. Start the virtual tape devices with the Guardian SCF command: TACL> SCF START TAPE $VT55* VT Controller Shut Down 1. Stop the virtual tape devices with the Guardian SCF command: TACL> SCF STOP TAPE $VT55* 2. Log on to the VTC Windows operating system using the locally attached keyboard and monitor, or by using a Remote Desktop Connection. 3. Use the Windows Shut Down menu to enter the reason for the shutdown. Tape Device Reset If the usual restart by SCF (STOP $tap-device, then START $tape-device) does not solve the problem, follow this procedure, which requires to have the command file that redefines the tape device. 1. Abort the tape process with the Guardian SCF command: TACL> SCF RESET TAPE $VT554, FORCE 2. Delete the virtual tape devices with the Guardian SCF command (be sure you have the SCF command to add the device again, before deleting the definition): TACL> SCF DELETE TAPE $VT554 3. Redefine the tape devices to SCF: SCF ADD TAPE $VT554, … 4. Start the tape devices: SCF START $VT554 Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 54 VT Controller Reset If the normal state of some virtual tape devices of a VTC cannot be restored individually by SCF command, the VTC should be reset. 5. Abort the tape process with the Guardian SCF command: TACL> SCF RESET TAPE $VT55*, FORCE 6. Delete the virtual tape devices with the Guardian SCF command (be sure you have the SCF command to add the device again, before deleting the definition): TACL> SCF DELETE TAPE $VT55* 7. Log on to the VTC Windows operating system using the locally attached keyboard and monitor, or by using a Remote Desktop Connection. 8. Use the Windows menu to Shut Down (not restart). 9. Use the Power button, or a remote control equipment to power on the VTC 10.Wait for the following two EMS messages to be displayed on the Guardian node where the EZX Domain Manager is installed: BBOX-103 Service started (VTC Virtual Tape Devices) BBOX-103 Service started (VTC Admin) 11.Logon in the VTC to verify that the following Non plug and play device drivers are not started (Device manager, Show Hidden Devices): SYM_HI SYMC810 SYM8XX SYMMPI If one of them is started, refer to the “VT Controller Preparation” manual, Driver Troubleshooting section 12.Redefine the tape devices to SCF, SCF ADD TAPE $VT555, 13.Start the tape devices SCF START $VT55* Disabling the Automatic Mounting of Volumes Volumes are not automatically mounted anymore when the EMS Extractor process is stopped. The mount requests will stay pending until a manual load, or until the restarting of the EMS Extractor BBEXT that will begin by checking pending mounts. If the EMS Extractor is not registered in the Kernel subsystem, simply stop the process: TACL> STOP $BBEXT If the EMS Extractor is registered in the Kernel subsystem, stop it through SCF. If #EZXEXT was the registered name: TACL> SCF ABORT PROCESS $ZZKRN.#EZXEXT Last Revised: Mar. 10, 16 Version 1.58 EZX-Gateway System 55 Enabling the Automatic Mounting of Volumes The permanent EMS Extractor process must be restarted. Before listening to the new mount requests, it will process the requests already pending. If the EMS Extractor is not registered in the Kernel subsystem, use the provided sample OBEY file to start it: TACL> OBEY OEXT If the EMS Extractor is registered in the Kernel subsystem, restart through SCF. If #EZXEXT was the registered name: TACL> SCF START PROCESS $ZZKRN.#EZXEXT Manual Load and Unload Manual load is executed only as a manual recovery from severe errors. A volume load is manually commanded by using the Web User Application. To Load a Volume 1. Log in to the Domain Manager through the Web User Interface, using a Guardian user in the SUPER group. 2. Wait until the EMS tape mount request appears in the Home page of the Web User Interface. 3. Locate the Load button associated with the pending mount request. 4. Click on Load. The configured devices are presented for load selection. A page showing the configured Guardian nodes and virtual devices is presented to the user who chooses the mount point. The virtual device can be left unspecified to enable auto-assign processing. To Unload a Volume 1. Locate the drive in the Web User Interface Home page. 2. Navigate to the Unload button associated with this drive. 3. Click on Unload. The tape volume is unloaded. Refer to the Web User Interface section for more information and for the procedure to preload a volume from the list of virtual volumes. Note: This operation will cancel any transfer executing on that specific device. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 56 Web User Interface Standard Page Elements Each page of the Web User Interface contains the page elements listed below: Banner: Located at the top of the page. Navigation Bar: Located on the left side of the page. Main Area: Located in the center of the page (with or without tabs) Note: The content of the main pages varies based on the functionality you select. Banner The top banner displays the EZX logo as well as information about the current session. Section Elements The EZX-Gateway Logo on the left corner of the page. The Guardian User ID used for signing in. A Sign Out link to close the session. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 57 Navigation Bar The navigation bar is located on the left side of the page. It allows users to access and to navigate through the main functionality of the EZX-Gateway Web User Interface. The current location is highlighted as shown below: Please note that the links only become active after a successful sign in to the Domain Manager. Tabbed Pages Some of the Web User Interface pages are subdivided. Tabs across the top of the main page provide easy navigation between subsections. Each tab is highlighted when selected. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 58 Sign In The Sign In page allows users to log into the EZX-Gateway Web User Interface. A successful sign in to the Domain Manager is required before any other page becomes visible. Sign In Tabs Sign in Tab: signs the user into the Domain Manager. Domain Address Tab: maintains the TCP/IP Domain address list. Sign In Tab The Sign in tab gives access to the Web User Interface Sign in page. This page allows you to sign in to the Domain Manager on the NonStop server. The User ID and password are communicated to the NonStop server to log on to Guardian. Note: A successful sign in is required for the display of the navigation bar and gain access to the main functions of the Web User Interface. Page Elements Domain: The Domain Name and the Domain Manager selected for the session. Domain addresses are managed using the Domain Address tab. Guardian User ID: A Guardian User name (Group.User) that allows the sign in to the Domain Manager. Guardian Password: The Guardian password associated with the User ID. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 59 To sign out Click on the Sign Out link located on the upper right corner of the Web User Interface to close the session. Sessions are automatically timed out after 20 minutes of inactivity. Any attempt to access the Web User Interface after a timeout returns the user to the Sign In page to log in again. Domain Address Tab By definition, a domain address contains the information necessary to the Web application for communicating with the Domain Manager on the NonStop server. This information must be entered for each VT Controller at the time of installation. It is kept in a VTC Windows file. The Domain Address tabbed page allows the creation, the edition or the deletion of a domain address. If several domains share a VT Controller, there will be at least one entry for each domain. If a Domain Manager initiating a TCP/IP session with the VT Controller can connect from several TCP/IP addresses, all theses addresses must be entered because the VTC filters connections are initiated from unknown addresses. The Domain Address tab is protected by a successful login in the Microsoft Windows operating system of the VT Controller running the IIS Web server. When prompted for a Microsoft Windows User name and Password, the user must enter a user in the Administrators or the BACKBOX_MANAGERS group. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 60 Page Elements Action: Allows editing or deleting of existing domains. Domain ID: Identifies the domain that will communicate with the VT Controller. Note: This ID must be the same as the Domain ID entered in the Domain configuration kept on the NonStop server. Discrepancy on domain ID is tolerated in the configuration activity, but must be solved before the actual operation on virtual volumes. This domain ID will also appear at the beginning of the messages logged by the Domain Manager in EMS. Log Messages: see the Domain Address Detail section below. IP Port: see the Domain Address Detail section below. Actions Click on the Add Domain button or on the Edit or Delete links. Domain Address Detail Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 61 Page Elements Domain Name: Identification of the EZX Domain (user defined) It is limited to eight characters. Guardian IP Port: IP Port used by the VT Controller to connect to the Domain Manager. Log Messages: Check to have the main log messages initiated by the VT Controller, propagated to the EMS subsystem of the NonStop server running the Domain Manager. This box should always be checked, unless the VTC communicates with two domains running on the same NonStop node; the second domain is then unchecked to avoid double logging in EMS. Note: This must match the Domain Manager port specified in the PORTCONF of the Guardian LISTNER on the NonStop server. IP Address List: IP address used by the VT Controller for two purposes:  To connect to the Domain Manager, the VTC takes the first address of the list.  To filter inbound connections, the VTC will accept any address in the list of addresses of any domain specified to the VTC. Multiple addresses are to be entered when the TCP/IP sessions initiated by the NonStop can originate from several controllers. Home The Home link opens the Overview tabbed page. This page displays a list of virtual devices and pending operations. It also provides basic functionality to manually load or unload virtual volumes. The Overview tabbed page contains two sections: Virtual Device Status: Displays the virtual devices status. Pending Mounts: Lists the pending tape mounts. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 62 Virtual Device Status Page Elements Node: Guardian node where the tape process for virtual devices is defined. Device: Guardian tape process that interacts with the virtual devices. Status: Status of the virtual volume device, as reported by MEDIACOM. The possible values are DOWN, FREE, INUSE, and UNAVAL. Label Mode: Label type of the volume currently loaded. The possible values are ANSI, BACKUP, OMITTED and TMF. Volume: Label of the volume currently loaded, as reported by MEDIACOM. Action: Unload the volume. Pending Mounts The Pending Mount section of the page only appears when there are pending mount requests in the NonStop tape subsystem. This section contains a data grid that displays volumes eligible for automatic mounts, as well as volumes requiring manual intervention. Page Elements Node: Guardian node reporting the manual intervention. ID: Tape mount ID as reported by MEDIACOM on the NonStop Server. Device: Guardian Tape process where the intervention is required. Volume: Volume serial of the volume to be mounted (or SCRATCH if the NonStop application requests a SCRATCH volume) Label Type: Label type of the volume currently loaded. The possible values are ANSI, BACKUP, OMITTED and TMF. Mount Message: Mount message for the operator specified on the volume. Action: Load the virtual volume. To Manually Load a Volume Click on Load next to the volume you want to manually mount. The Load window is then displayed. Specify on which device to load the volume (if given a choice of devices) Note: Manual load can also be achieved from other pages, but to load from this list of pending mounts is preferred in order to have the control of volume access executed against the User ID running the Guardian tape application. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 63 Configuration The Configuration tabs allow easy navigation through the main configuration pages, as well as the option to save changes to your configuration. Figure 1. Configuration Page in View Mode Figure 2. Configuration Page in Edit Mode Page Elements Domain Tab: Access to the Domain identity and to the configuration parameters for the Domain Manager. VT Controller Tab: Management of VT Controller servers and the virtual devices configured on each one. Data Store Tab: Management of the stored virtual volumes data and location. Volume Group Tab: Specifications on how virtual volumes are created. Switch to Edit Mode Link: Entrance to the Edit mode. Cancel Link: Reverts to the last saved configuration. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 64 Domain It is in the Domain tabbed page that changes to the Domain Manager identity, or the activation of Domain Manager traces can be done. Page Elements Domain ID: Unique name of the Domain. It must match the Domain ID entered in the EZX-Gateway Manager through the Domain Address tab. EMS Collector Process: Guardian process name for the destination of the EMS log messages. Trace Level: Trace used to troubleshoot problems (zero for no trace (off) and 1 to activate the trace on the Domain Manager) Note: Reserved use by ETI-NET only. Activating the trace on the Domain Manager will create of lot of trace files, and may cause performance degradation. Trace Sub Volume: Valid Guardian Disk and Sub volume where the trace files will be stored (see the Trace Level description above) VT Controller Timeout: Maximum waiting time (in seconds) the EZX MVS agent waits for a response before forcing a timeout. To Modify the Domain 1. Click on the Domain tab. 2. In Domain ID, type the change(s) 3. Click on Update Domain. 4. Click on Save Configuration to activate your changes. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 65 VT Controller The VT Controller tabbed page contains information concerning the VT Controller configuration. This is where you add or change a VTC configuration and set the TCP/IP Guardian Defines and virtual devices emulated on the VTC. Page Elements Top Section: Lists each VT Controller configured on the Domain Manager. It is displayed even when no VTC is selected. VT Controller General Information: Displays the selected VTC details and allows them to be updated as well as to create new VTC definitions. Guardian Defines: Sets the TCP/IP Guardian Defines to access the VT Controller from the NSK node (displayed when a VTC is selected) Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 66 Port: Defines the SCSI connections between the VT Controller and the NSK node(s) (displayed when a VT Controller is selected) Virtual Devices: Defines the virtual tape devices emulated on the selected VTC. General Information Section Elements VT Controller ID: Identifies the VTC to the Domain Manager. Must be unique and cannot be changed after being added. Physical Location: Optional field describing the physical location of the VTC unit. TCP/IP Address: TCP/IP address or TCP/IP Host name used by the Domain Manager to communicate with the VT Controller. Emulation TCP/IP Port: TCP/IP port on the VTC used by the emulation of the Virtual Tape Devices (8765 by default) This TCP/IP port is mainly used by the Domain Manager to communicate tape mount requests to the VTC. Admin TCP/IP Port: TCP/IP port on the VT Controller used by the administration services (8766 by default) This TCP/IP port is mainly used by the Domain Manager to create new virtual volumes on the VT Controller. Comments: Optional field for further description, available to the user. Trace Level: Trace level emulator. Consult ETI-NET to set it to a different value from zero. Guardian Define This section manages the TCP/IP Guardian Define used by the Domain Manager to communicate with the selected VT Controller. For further information about the Guardian Define, please consult the Guardian TCP/IP Configuration manual. Section Elements Guardian Defines: Valid Guardian Define name supported by the TCP/IP stack. File Name: Value associated with the Guardian Define. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 67 Ports A Virtual Bus definition is required for each VT Controller SCSI port connected to a NonStop server (i.e. SCSI card connectors) Section Elements Port Number: SCSI bus address of the one connected to the NonStop Server. It identifies the physical SCSI connector on the VT Controller. Virtual Device This section configures the virtual tape devices for the selected VT Controller. Section Elements Node: Guardian Node name of the NonStop server connected to the SCSI port. Guardian Device: Name of the Guardian tape device defined by SCF. Port: Port Address. It must be consistent with the Adapter location corresponding to the Guardian tape devices defined by SCF. SCSI Target: SCSI Target ID assigned to the Guardian tape device by SCF. SCSI LUN: SCSI LUN ID assigned to the Guardian tape device by SCF. Explicit Only: “Yes” to exclude this device from the automatic device assignment provided by the Domain Manager. Only mount requests that explicitly specify this device will use it. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 68 Data Store The Data Store tabbed page contains information concerning the Data Store configuration. Page Elements Top Section: Lists the Data Stores configured in the Domain Manager and is displayed even when no Data Store is selected. Data Store Information: Displays selected Data Store details and allows information to be updated, or a new Data Store definition to be added. EZX MVS Agent – Detail Information: Allows configuring communications with the EZX MVS Agent. It also configures the MVS Dataset creation. Storage Route: Manages which VT Controller, and in what priority, is used to reach a Data Store (displayed when a Data Store is selected) Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 69 Common General Information for all Store Types Section Elements Store ID: Identifies the Data Store. Must be unique and cannot be modified after being added. Store Type: Indicates the Data Store type and cannot be modified after being added. Use EZX. Description: Optional user description. EZX MVS Agent Section Elements TCP/IP Address: BCOM MVS address. TCP/IP Port: Port number for the EZX service in BCOM. Unit Type: Unit type for the datasets to be created in MVS. All DE XP volumes associated to the Data Store should have the same track length, as seen by MVS. If there is a mix of 3380 and 3390 track lengths, the creation of MVS datasets from the EZX_START_XFER macro will not work properly. Storage Class: Optional storage class for the datasets to be created in MVS. Space Allocation: Maximum space allocated per MVS dataset to be created. Quantity and space unit (Tracks/Cylinders). This space amount should fit in all DE XP volumes associated to the Data Store. If there is a mix of different models, several datasets might be created for the same group ".EZX" on the largest disk models. The space allocation should be carefully planned to maximize the space occupancy. Timeout: Maximum waiting time (in seconds) the EZX MVS Agent waits for a response before forcing a timeout. Guardian Define This section manages the TCP/IP Guardian Define used by the Domain Manager to communicate with the EZX MVS Agent. For further information about the Guardian Define, please consult the Guardian TCP/IP configuration manual. Section Elements Guardian Defines: Valid Guardian Define name supported by the TCP/IP stack. File Name: Value associated with the Guardian Define. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 70 Store Route Rank: Indicates the route priority to reach a DataStore. The rank zero has the highest priority. VT Controller ID: Indicates the VT Controller used to reach a DataStore. Volume Group The Volume Group tabbed page contains information about volume management and configuration. Page Elements Top Section: Lists the Volume Groups configured in the Domain Manager. It is displayed even when no Volume Group is selected. Volume Group Information: Displays and updates the selected Volume Group information and creates new Volume Group definitions. Authorized Access Information: Displays and updates the default access authorization set for volumes (when being written) Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 71 Volume Group Information Section Elements Volume Group ID: Identifies the unique Volume Group and cannot be modified after being added. Description: Optional user description. Store ID: Specifies in which Data Store the virtual volume is created. This value applies to new virtual volumes created in this group. This will not change the location of previously created volumes. Authorized Access Information This section defines the default authorizations set for the volumes each time they are loaded for output. Refer to “Control of Access to Virtual Volumes” in the first section. Each element of the Authorized Access section defines a group of User IDs, depending on the owner of the volume: N Any node, any User ID C Any node, same group number U Any node, same User ID A Same node, any User ID G Same node, same group number O Same node, same User ID Section Elements Read Authorization: User IDs allowed to read the volume data. Write Authorization: User IDs allowed to read/write/delete the volume data. Control Authorization: User IDs allowed to modify the owner or the authorizations of the volume in the VT Controller catalog. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 72 Volume The virtual volumes catalog of a domain is accessed through the Volume tabs. Page Elements Volume List Tab: Display and browse through a list of virtual volumes. Allow checking and deleting a several volumes in a single operation. Allow selecting a particular volume to get the Volume detail page. Volume Operations Tab: Direct access to the Volume Detail page, which displays the detailed data cataloged for the volume and allows operations on the volume. Create Volume Tab: Create and label new virtual volumes and add them to the domain catalog. Volume List The Volume List page allows the virtual volumes listing of the VT Controller catalog. The output is limited by a page size, which is defined as the maximum number of returned volumes. The Next and Previous buttons allow scrolling the complete list of volumes. The list can be filtered according to the selection criteria. Page Elements Top Section: The Filter section allows selecting the volumes to be listed. Second Section: The volume list appears when the Display button is pressed. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 73 Volume List Filter The Volume List Filter section allows specifying selection criteria of the volumes to be listed. To filter the entire list: 1. Do not change the default values. 2. Click on Display. The list will appear on the same page. Section Elements Note: Only the volumes matching all specified criteria will be listed. Labelled / Unlabelled Radio-box: Select labelled or NL volumes. Volume Label: Volume label to select. Blank indicates that no filtering is applied to the volume name. Wildcard characters are accepted: “*” and “?”. Label Type: Filters volumes based on the Label Type. Select Any to avoid Label Type filtering. Volume Group: Filters volumes based on the Volume Group. Select Any to avoid Volume Group filtering. Data Store: Filters volumes based on the Data Store where they reside. Select Any to avoid Data Store filtering. Current Operation: Filters volumes based on the current operation being performed on the volume. Select Any to avoid current operation filtering. Page Size: Maximum number of volumes to return in the reply page. The user can browse a large list by pressing the Previous and the Next buttons. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 74 Volume List The Volume List section displays the list of virtual volumes that match the specified Filter. Section Elements Delete Checked Volume: Deletes all the volumes that are checked in the page. All (checkbox): Checks or unchecks all volumes in the page. Volume (checkboxes): checkbox. Checks or unchecks the volume next to the Volume Label: Label of the volume. It is a link to the Volume Detail page. Type: Label type of the volume. Data Store: Identifies the Data Store in which the virtual volume resides. Volume Group: Identifies the virtual volumes group. Current Operation: Identifies the current operation of the volume. Comment: Identifies the user comments. Action: Displays possible action(s) to be performed on the volume. Use the Next Page (>)/ Previous Page (<) links located at the bottom of the data grid to navigate through the list. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 75 Volume Details The Volume Details page displays the available data in the VT Controller catalog for a virtual volume and allows requesting of operations on it. Page Elements Back Button: Returns to the previous page. Edit Button: Links to the Edit Volume page. Delete Button: Deletes the virtual volume. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 76 Refresh Button: Refreshes the displayed data. Volume Label: Identifies the virtual volume. Label Type: Label type (NL, ANSI, BACKUP or TMF) Volume Lock: Manual lock prohibiting the volume data update by a tape application. It is equivalent to the lock found on some physical media. Store ID: Identifies the data storage for the volume and its type (WINDISK or TSM) Automatic Mount: Manual setting enabling the automatic mounts when a volume mount request is issued by a tape application. Current Operation: LOAD: volume loaded for a Guardian tape application. EXPORT: volume being cloned in a VT Controller (blank if the volume is not currently used) Last Update: Last update user name and timestamp of the entry in the catalog. The user name can be an interactive user, AUTOMATE for an update executed by the EMS Extractor when loading the volume on a drive or a VT Controller ID that notified the end of a volume operation. Comment: Free text entered by a user for this catalog entry. Creation Time: Time when the virtual volume was created and registered in the catalog. Last Load for Output: Timestamp of the last load for output. Write Byte Count: Number of bytes that were written by the NonStop node during the last operation. Last Load Time: Timestamp of the last load of this volume. Last Unload Time: Timestamp of the last unload of this volume. Severity: Severity (success, error, information, etc.) operation of this volume. of the current Last Loaded Device: Last loaded device which performs the current operation of this volume. Read Byte Count: Number of bytes that were read by the tape NonStop node during the last operation. Guardian Owner: Node and User ID running the last tape application that requested a load for output. This User ID can be identified only if the load was executed in the context of a load request, i.e. automatically or manually requested from a pending mount listed in the Home page. For other manual loads, the owner will be the login information entered when accessing the Web User Interface. Authorized Access: Authorizations set the last time the volume was loaded for output. Guardian Status: Status of the volume in the Guardian tape catalog (DSM/TC or TMF), if any (unused in EZX product) Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 77 DSM/TC File ID: First non-expired File ID associated to this volume in DSM/TC (unused in EZX product) Statistics about the Latest EZX Transfer Guardian Tape DEFINE EZX_START_XFER macro. Block Size: Block size set by the MVS Dataset: Name of the MVS dataset (name pattern when a group of datasets is involved) MVS Dataset DCB: Displays the RECFM, the LRECL and the BLKSIZE values. File Count: Number of existing MVS dataset(s) in the group. Total Allocated Tracks: Total space for all datasets involved in the transfer. Processed File Count: Number of datasets accessed during the transfer. Total Record Count: Number of records transferred in the VT Controller. Total Data Byte Count: Number of bytes transferred in the VT Controller (excluding length fields) MVS Volume(s): Name of the DE XP volumes where the datasets are located. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 78 Update of a Volume Entry in the EZX-Gateway Catalog Page Elements Volume Label: Volume label to update. Last Update: Date and time of the last update. Volume Lock: Manual lock prohibiting volume data update by a NonStop tape application. It is equivalent to the lock found on some physical media. Check to lock the volume. Automatic Mount: Enable the automatic mount by the EMS Extractor. Current Operation: Checkbox to reset the current operation of the volume to “none” (applicable if the volume is currently in use), only as a bypass of an operational problem. The current operation status (LOAD, EXPORT or none) is set when an operation starts and is reset when the VT Controller returns feedback and statistics to the Domain Manager. It might happen that the Domain Manager does not register this end of the operation signal. For example, when the TCP/IP connection is lost between the EZX-Gateway and the NonStop server. The VT Controller retries to communicate the end of the operation up to 7 days before simply purging this end of operation feedback. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 79 This current operation status is used as a lock to avoid concurrent operations on the same volumes. To force a load that is rejected because it is already in use, check the Reset box. Comment: Optional field associated with the volume. Guardian node owner, Guardian User ID Owner: Owner of the volume, used to control the access to the volume data. Only updateable if the User ID logged in the Web User Interface has control access to the volume (or if it is SUPER.SUPER) Authorized Accesses: Only updateable if the User ID logged in the Web User Interface has control access to the volume, or if it is SUPER.SUPER. Read Access: Accessors allowed to read the volume data through the SCSI bus. Write Access: Accessors allowed to read/write/delete the volume data through the SCSI bus. Control Access: Accessors allowed login the Web User Interface and changing the volume security. Create Volume The Create Volume tabbed page allows you to create new volumes, label them, add them to the library or catalog them in an external catalog (DSM/TC or TMF) Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 80 Page Elements Volume Label: Specifies the label of the first volume to create. The volume label you specified must terminate with numerical digits if you intend to create more than one tape volume. The numerical portion is incremented as the volumes are created. Label Type: Indicates the type of label to create (Unlabel, ANSI, Backup, and TMF) Comment: User comment describing the purpose or the content of the volume. This comment is preserved with the volume in the catalog. Volume Group: Selects the Volume Group where the volume is created. The Volume Group determines in which DataStore the volume is created as well as other characteristics of the virtual volume (capacity, external catalog, etc.) Quantity: Indicates the number of volumes to be created (from 1 to 999) The volume label you specified must end with numerical digits if you intend on creating more than one tape volume. The numerical portion is incremented by one for each volume created. Allow Volume to be automatically mounted: Check to have the volume(s) to be created automatically loaded when a mount request is issued in the EMS subsystem. This does not apply to NL volumes. Tape Creation – Progress The Tape Creation - Progress page appears when the volume creation is in progress. A message appears on the page when the process is completed. Last Revised: Mar. 10, 16 Version 1.58 Web User Interface 81 Data Exchange The Data Exchange tabbed page allows visualizing the DE XP volumes (visible by the VT Controllers of the Domain) For each VT Controller, the defined routes to Data Stores and the DE XP devices discovered by the VT Controller are displayed. Last Revised: Mar. 10, 16 Version 1.58 Appendixes I Appendixes Appendix A – ASCII-EBCDIC Conversion Table EBCDIC 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F ASCII 0x00 0x01 0x02 0x03 0x9C 0x09 0x86 0x7F 0x97 0x8D 0x8E 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x9D 0x85 0x08 0x87 0x18 0x19 0x92 0x8F 0x1C 0x1D 0x1E 0x1F EBCDIC 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2A 0x2B 0x2C 0x2D 0x2E 0x2F 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x3A 0x3B 0x3C 0x3D 0x3E 0x3F ASCII 0x80 0x81 0x82 0x83 0x84 0x0A 0x17 0x1B 0x88 0x89 0x8A 0x8B 0x8C 0x05 0x06 0x07 0x90 0x91 0x16 0x93 0x94 0x95 0x96 0x04 0x98 0x99 0x9A 0x9B 0x14 0x15 0x9E 0x1A EBCDIC 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0x5B 0x5C 0x5D 0x5E 0x5F ASCII 0x20 0xA0 0xA1 0xA2 0xA3 0xA4 0xA5 0xA6 0xA7 0xA8 0xD5 0x2E 0x3C 0x28 0x2B 0x7C 0x26 0xA9 0xAA 0xAB 0xAC 0xAD 0xAE 0xAF 0xB0 0xB1 0x21 0x24 0x2A 0x29 0x3B 0x7E EBCDIC 0x60 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 0x71 0x72 0x73 0x74 0x75 0x76 0x77 0x78 0x79 0x7A 0x7B 0x7C 0x7D 0x7E 0x7F ASCII 0x2D 0x2F 0xB2 0xB3 0xB4 0xB5 0xB6 0xB7 0xB8 0xB9 0xCB 0x2C 0x25 0x5F 0x3E 0x3F 0xBA 0xBB 0xBC 0xBD 0xBE 0xBF 0xC0 0xC1 0xC2 0x60 0x3A 0x23 0x40 0x27 0x3D 0x22 EBCDIC 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x8A 0x8B 0x8C 0x8D 0x8E 0x8F 0x90 0x91 0x92 0x93 0x94 0x95 0x96 0x97 0x98 0x99 0x9A 0x9B 0x9C 0x9D 0x9E 0x9F ASCII 0xC3 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 0x69 0xC4 0xC5 0xC6 0xC7 0xC8 0xC9 0xCA 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 0x71 0x72 0x5E 0xCC 0xCD 0xCE 0xCF 0xD0 EBCDIC 0xA0 0xA1 0xA2 0xA3 0xA4 0xA5 0xA6 0xA7 0xA8 0xA9 0xAA 0xAB 0xAC 0xAD 0xAE 0xAF 0xB0 0xB1 0xB2 0xB3 0xB4 0xB5 0xB6 0xB7 0xB8 0xB9 0xBA 0xBB 0xBC 0xBD 0xBE 0xBF ASCII 0xD1 0xE5 0x73 0x74 0x75 0x76 0x77 0x78 0x79 0x7A 0xD2 0xD3 0xD4 0x5B 0xD6 0xD7 0xD8 0xD9 0xDA 0xDB 0xDC 0xDD 0xDE 0xDF 0xE0 0xE1 0xE2 0xE3 0xE4 0x5D 0xE6 0xE7 EBCDIC 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0xC6 0xC7 0xC8 0xC9 0xCA 0xCB 0xCC 0xCD 0xCE 0xCF 0xD0 0xD1 0xD2 0xD3 0xD4 0xD5 0xD6 0xD7 0xD8 0xD9 0xDA 0xDB 0xDC 0xDD 0xDE 0xDF ASCII 0x7B 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0xE8 0xE9 0xEA 0xEB 0xEC 0xED 0x7D 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0xEE 0xEF 0xF0 0xF1 0xF2 0xF3 EBCDIC 0xE0 0xE1 0xE2 0xE3 0xE4 0xE5 0xE6 0xE7 0xE8 0xE9 0xEA 0xEB 0xEC 0xED 0xEE 0xEF 0xF0 0xF1 0xF2 0xF3 0xF4 0xF5 0xF6 0xF7 0xF8 0xF9 0xFA 0xFB 0xFC 0xFD 0xFE 0xFF ASCII 0x5C 0x9F 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0xF4 0xF5 0xF6 0xF7 0xF8 0xF9 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0xFA 0xFB 0xFC 0xFD 0xFE 0xFF Appendixes II Appendix B – JIS-EBCDIK Conversion Table EBCDIK 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F JIS 0x00 0x01 0x02 0x03 0x9C 0x09 0x86 0x7F 0x97 0x8D 0x8E 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x9D 0x85 0x08 0x87 0x18 0x19 0x92 0x8F 0x1C 0x1D 0x1E 0x1F EBCDIK 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2A 0x2B 0x2C 0x2D 0x2E 0x2F 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x3A 0x3B 0x3C 0x3D 0x3E 0x3F JIS 0x80 0x81 0x82 0x83 0x84 0x0A 0x17 0x1B 0x88 0x89 0x8A 0x8B 0x8C 0x05 0x06 0x07 0x90 0x91 0x16 0x93 0x94 0x95 0x96 0x04 0x98 0x99 0x9A 0x9B 0x14 0x15 0x9E 0x1A Last Revised: Mar. 10, 16 EBCDIK 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0x5B 0x5C 0x5D 0x5E 0x5F JIS 0x20 0xA1 0xA2 0xA3 0xA4 0xA5 0xA6 0xA7 0xA8 0xA9 0xA0 0x2E 0x3C 0x28 0x2B 0xE0 0x26 0xAA 0xAB 0xAC 0xAD 0xAE 0xAF 0xE1 0xB0 0xE2 0x21 0x5C 0x2A 0x29 0x3B 0xE3 EBCDIK 0x60 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 0x71 0x72 0x73 0x74 0x75 0x76 0x77 0x78 0x79 0x7A 0x7B 0x7C 0x7D 0x7E 0x7F Version 1.58 JIS 0x2D 0x2F 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 0x7C 0x2C 0x25 0x5F 0x3E 0x3F 0x5B 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 0x60 0x3A 0x23 0x40 0x27 0x3D 0x22 EBCDIK 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x8A 0x8B 0x8C 0x8D 0x8E 0x8F 0x90 0x91 0x92 0x93 0x94 0x95 0x96 0x97 0x98 0x99 0x9A 0x9B 0x9C 0x9D 0x9E 0x9F JIS 0x5D 0xB1 0xB2 0xB3 0xB4 0xB5 0xB6 0xB7 0xB8 0xB9 0xBA 0x71 0xBB 0xBC 0xBD 0xBE 0xBF 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0xC6 0xC7 0xC8 0xC9 0x72 0xE4 0xCA 0xCB 0xCC EBCDIK 0xA0 0xA1 0xA2 0xA3 0xA4 0xA5 0xA6 0xA7 0xA8 0xA9 0xAA 0xAB 0xAC 0xAD 0xAE 0xAF 0xB0 0xB1 0xB2 0xB3 0xB4 0xB5 0xB6 0xB7 0xB8 0xB9 0xBA 0xBB 0xBC 0xBD 0xBE 0xBF JIS 0x7E 0xE5 0xCD 0xCE 0xCF 0xD0 0xD1 0xD2 0xD3 0xD4 0xD5 0x73 0xD6 0xD7 0xD8 0xD9 0x5E 0xE6 0xE7 0x74 0x75 0x76 0x77 0x78 0x79 0x7A 0xDA 0xDB 0xDC 0xDD 0xDE 0xDF EBCDIK 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0xC6 0xC7 0xC8 0xC9 0xCA 0xCB 0xCC 0xCD 0xCE 0xCF 0xD0 0xD1 0xD2 0xD3 0xD4 0xD5 0xD6 0xD7 0xD8 0xD9 0xDA 0xDB 0xDC 0xDD 0xDE 0xDF JIS 0x7B 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0xE8 0xE9 0xEA 0xEB 0xEC 0xED 0x7D 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0xEE 0xEF 0xF0 0xF1 0xF2 0xF3 EBCDIK 0xE0 0xE1 0xE2 0xE3 0xE4 0xE5 0xE6 0xE7 0xE8 0xE9 0xEA 0xEB 0xEC 0xED 0xEE 0xEF 0xF0 0xF1 0xF2 0xF3 0xF4 0xF5 0xF6 0xF7 0xF8 0xF9 0xFA 0xFB 0xFC 0xFD 0xFE 0xFF JIS 0x24 0x9F 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0xF4 0xF5 0xF6 0xF7 0xF8 0xF9 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0xFA 0xFB 0xFC 0xFD 0xFE 0xFF Appendixes III Appendix C – Error Message Table This section lists the messages that can be logged in EMS or simply displayed by the Web User Interface. Messages are displayed along with their message number suffixed by a letter reporting the event severity. Event Severity I Information / Normal completion W Warning E Error F Fatal error A Program ABEND The message text is prefixed by an identifier when logged on to EMS. This identifier shows what initiated the message. Message Identifier Origin Prefix VT Controller VTC ID Domain Manager Domain name EMS Extractor EMS Extractor process name Sample message logged to EMS by the VT Controller VTC1 when starting up: VTC1-103I Service started (VTC Virtual Tape Devices) Last Revised: Mar. 10, 16 Version 1.58 Appendixes IV Table 4. Error Messages Msg Num 1 Message Text Explanation %1 Action An error occurred in the VT Controller during the Write or the Read to a virtual volume. TSM DataStore: Refer to the IBM Tivoli Messages manual. Windows file DataStore: Refer to the Microsoft documentation. 103 Service started (VTC Admin) The service implementing the administrative service in the VT Controller has started. None. 104 Service stopped (%1) A service stopped in the VT Controller. None. 106 Could not initialize WinSock DLL, error %1 Internal error at service startup in a VT Controller. Contact ETI-NET Technical Support 107 Service handler is not installed Internal error at service startup in a VT Controller. Contact ETI-NET Technical Support. 108 Service is not installed: %1, %2 (%3) Internal error at service installation in a VT Controller. Contact ETI-NET Technical Support. 109 Service is not updated: %1 (%2) Internal error at Windows service installation in a VT Controller. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes V Msg Num Message Text Explanation Action 110 Access Service error: %1 (%2) Internal error at Windows service installation in a VT Controller. Contact ETI-NET Technical Support. 111 Service RegKey error: %1 (%2) Internal error at Windows service installation in a VT Controller. Contact ETI-NET Technical Support. 1001 Guardian error %1 from %2 %3 A Guardian procedure call failed. Refer to the Guardian Procedure Errors and Messages manual. 1002 AWAITIOX completes with error %1, %2 tag %3 Guardian AWAITIOX procedure call failed. Refer to the Guardian Procedure Errors and Messages manual. 1003 AWAITIOX completes with warning %1, %2 tag %3 Guardian AWAITIOX procedure call ended with a warning. Refer to the Guardian Procedure Errors and Messages manual. 1004 Abort in %1 %2, error code %3 %4 Severe internal error. Refer to the Guardian Procedure Errors and Messages manual. 1005 No memory available for %1 Memory allocation failed. Contact ETI-NET Technical Support. 1006 Unexpected tag %1 Internal error. Contact ETI-NET Technical Support. 1007 Guardian Error %1 detail %2 from %3 %4 A Guardian procedure call failed. Refer to the Guardian Procedure Errors and Messages manual. 1101 Warning: trace file %1 unavailable, errno: %2 Error accessing the Domain Manager trace file. Refer to the Guardian Procedure Errors and Messages manual. Last Revised: Mar. 10, 16 Version 1.58 Appendixes VI Msg Num Message Text Explanation Action 2001 Idle session terminates TCP/IP session started but did not receive a command. None, if no other symptom appears. 2002 Timeout during processing state No reply from a Guardian or a VT Controller service before the configured Processing Timeout value. Fix cause of error, or increase the Processing Timeout in the Domain configuration. 2003 Config file %1 unavailable The BBSVCFG file is not available. Check that the file is created, and that the Guardian User ID in session has authorized access and is not locked by an application outside the Domain Manager. 2501 XML parse error in %1 line %2 col %3: ‘%4’ An XML syntax error is detected at the specified location. Manual XML syntax: Fix the syntax. Unknown element name %1 in %2 An XML tag is not known by the Domain Manager. Manual XML syntax: Fix the syntax. Invalid %1 in %2: %3 Invalid content for an XML tag. Manual XML syntax: Fix the syntax. 2502 2503 BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes VII Msg Num 2506 Message Text Explanation Action End tag %1 does not match start tag %2 in %3 Invalid XML syntax. Manual XML syntax: Fix the syntax. Most often a consequence of a previous error. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. 2507 Unexpected element name %1 as root in %2 An XML document name is unknown. Contact ETI-NET Technical Support. 2508 Config file %s not available for rewrite, errno: %Id Guardian error when accessing the configuration file BBSVCFG for update. Check the error code, the file definition, and the security attributes. 2509 Can not save the current config file in the backup file %s, errno: %Id Guardian error when saving the previous version of BBSVCFG. Check the error code, the file BBSVCFGO definition, and the security attributes. 2510 Can not re-open config file %s for backup, errno: %Id Guardian error when saving the previous version of BBSVCFG. Contact ETI-NET Technical Support. 2511 Config file updated. Backup in %s The Domain configuration file BBSVCFG has been updated. None. 2601 Maximum number of TCP/IP out buffers exceeded %1 Internal buffers for the socket reply are insufficient. Contact ETI-NET Technical Support. 2602 Out of memory to allocate output buffer Internal buffers for the socket reply are insufficient. Contact ETI-NET Technical Support. 2603 Socket error %1 on %2 TCP/IP error. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. Last Revised: Mar. 10, 16 Version 1.58 Appendixes VIII Msg Num Message Text Explanation Action 2604 Socket error %1 on completion of %2 TCP/IP error. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 2605 Program parameter missing: accept address. The Domain Manager does not receive the expected parameter from the LISTNER. Contact ETI-NET Technical Support. 2606 TCP accept address ‘%1’ should contain a dot The Domain Manager does not receive the expected parameter from the LISTNER. Contact ETI-NET Technical Support. 2607 TCP accept address ‘%1’ should be numeric The Domain Manager does not receive the expected parameter from the LISTNER. Contact ETI-NET Technical Support. 2608 TCP accept address ‘%1’ rejected by inet_addr() The Domain Manager does not receive the expected parameter from the LISTNER. Contact ETI-NET Technical Support. 2609 Inbound socket closed when processing %1 The TCP/IP client closed the session before receiving the reply. None, if no other symptom shows up. Might be caused by a Web User Interface session abruptly closed. 2610 Unable to solve TCP/IP address name %1 Last Revised: Mar. 10, 16 The TCP/IP configuration in use does not resolve the address name. Version 1.58 Check spelling of the address name. Check the configured TCP/IP DEFINEs. Appendixes IX Msg Num 2611 Message Text Explanation Socket error %1 at connect to address %2 port %3 Unable to establish a TCP/IP session with the specific address. Action Refer to the TCP/IP Programming HP NonStop manual. Check spelling of the address and the port. Check the configured TCP/IP DEFINEs. 3001 Volume not found in catalog %1 %2 A volume name to mount is not found in the catalog of virtual volumes. None. The volume is not virtual. 3003 Invalid device %1 for mounting virtual volume %2 Cannot mount a virtual volume on a real tape device. Check the TAPE DEFINE of the tape application. If specified, both the device and the volume should be real, or virtual. 3004 Invalid volume label %1 to be mounted on a virtual device Cannot mount a real volume on a virtual tape device. Check the TAPE DEFINE of the tape application. If specified, both the device and the volume should be real, or virtual. 3005 Management of SCRATCH tapes not available An application TAPE DEFINE specified a SCRATCH volume. Management of SCRATCH tapes not available in the EZX-Gateway software. Use TAPECATALOG DEFINE, or specify a specific volume label. 3006 3007 Volume must be specified MountId: %1.%2. No free virtual device to mount %3 Last Revised: Mar. 10, 16 An application TAPE DEFINE did not specify a volume label. Specify the tape volume. No free device. Manual mount: Retry later. Version 1.58 BackBox product: alternatively use TAPECATALOG DEFINEs. Automatic mount: None, the mount will be retried. Appendixes X Msg Num 3008 Message Text Explanation Action MountId: %1.%2. Can not mount %3 on device %4: device not free Device is not free. MountId: %1.%2. Error %3 loading %4 on %5 %s. An error occurred in the VT Controller. Fix error according to the text message. 3012 Device %1 unknown by DSM/TC A Guardian device name in the Domain configuration is unknown by DSM/TC. Fix the Guardian device name in the Domain configuration. 3013 No virtual device defined in node %1 to mount %2 A mount command is received for a Guardian node that has no virtual device. Check the Domain configuration. 3015 VT Controller %1 in drive %2 definition is unknown Referential integrity error in the Domain configuration. BBSVCFG updated by the Domain Manager. Contact ETI-NET Technical Support. 3016 MountId: %1.%2. Volume %3 %4 is not defined for automatic load Automatic load is rejected because the volume was created with the attribute “No automatic load”. Issue a manual mount. 3018 DataStore %1 recorded for volume %2-%3 is unknown The DataStore where a volume was stored is no longer defined in the Domain configuration. Define the DataStore in the Domain configuration. 3011 Last Revised: Mar. 10, 16 Manual mount: Retry later. Automatic mount: None, the mount will be retried. Version 1.58 If the problem cannot be solved, please contact ETI-NET Technical Support. Do not run BBEXT on a Guardian node that has no virtual device. Appendixes XI Msg Num 3019 Message Text Explanation Duplicate routes for DataStore %1, VT Controller = %2 Error in the Domain configuration. Action BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. BBSVCFG modified by TEDIT: Fix error. 3020 DataStore Id %1 is unknown Error in the Domain configuration. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. BBSVCFG modified by TEDIT: Fix error. 3021 MountId: %s. No active VTC is a route between the NSK node and the DataStore %s for mounting %s. The Domain configuration does not contain an active VT Controller route to access the named DataStore. Configure or activate a VTC that: - has a/the tape device connected to the NSK node where to mount the volume - is a route to the DataStore where the volume was created. 3022 MountId: %1.%2. Mount id for volume %3 is no more pending The tape mount id associated with a load request is not in the list of pending mounts in MEDIACOM. Check pending mounts. 3023 MountId: %1.%2. Volume %3 loaded on device %4. %5 A mount request was successfully executed. None. 3024 Invalid user name or password A Guardian logon procedure failed. Check Guardian user name and password. 3025 Add volume %1 label Type %2 in pool %3 catalog %4 rejected by MEDIASRV code %5 An error occurred while updating a DSM/TC catalog. Refer to the DSM/TC Management Programming HP NonStop manual. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XII Msg Num Message Text Explanation Action 3026 Must be logged SUPER group to execute this command An error occurred while updating a DSM/TC or TMF catalog. Sign off using a Guardian User ID on the EZX-Gateway Web user interface. 3027 Adding volume %1 in pool %2 of catalog %3 is rejected by DSM/TC An error occurred while updating a DSM/TC catalog. No error code supplied. Try to use MEDIACOM to catalog the virtual volume. 3028 VT Controller %1 is unknown Referential integrity error in the Domain configuration. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. BBSVCFG modified by TEDIT: Fix error. 3029 Volume %1 not added in DSM/TC catalog – invalid volume catalog %2 Invalid volume catalog name in the Domain configuration. Fix the configuration of Volume Group. 3030 Volume %1 not added in DSM/TC catalog – invalid pool %2 Invalid pool name in the Domain configuration. Fix the configuration of Volume Group, or 3031 Drive %1 declared invalid by MEDIASRV Invalid Guardian device name in the Domain configuration. Fix the Guardian device name or Guardian node name in the VT Controller definition. 3032 Volume group %1 is unknown Requested volume group is unknown in the Domain configuration. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. Create the missing pool using MEDIACOM. BBSVCFG modified by TEDIT: Fix error. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XIII Msg Num Message Text Explanation Action 3033 Info volume %1 label Type %2 in pool %3 catalog %4 rejected by MEDIASRV code %5 An error occurred while accessing a DSM/TC catalog. Refer to DSM/TC Management Programming HP NonStop manual. 3034 No available route to DataStore %1 There is no VT Controller defined as route to the specified DataStore, when creating or deleting a volume. Define a route to the DataStore in the Domain configuration. 3035 Numeric suffix in ‘%1’ not sufficient to compute %2 labels When requesting the creation of a number of volumes, the label of the 1st volume does not allow all the requested labels to be created. Reduce the number of volumes to create, or 3036 Unable to create %1 volumes starting at label %2: %3-%4 already exists in domain catalog. One of the volume labels to be created already exists in the catalog of virtual volumes. Specify a series of labels that are not already registered as virtual volumes. 3037 Invalid DataStore Id %1 in volume group %2 Referential integrity error in the Domain configuration. BBSVCFG updated by the Domain Manager: Contact ETI-NET Technical Support. Use more numeric characters at the end of the 1st label to be created. BBSVCFG modified by TEDIT: Fix error. 3038 Volume %1 not added in DSM/TC catalog – already exists with label type %2 and status %3 in pool %4 of volcat %5 Last Revised: Mar. 10, 16 The creation of volumes that must also be in DSM/TC stops because a volume is already cataloged with a status different from SCRATCH. Version 1.58 Check the status of the volume in DSM/TC. Create volumes with different labels. Appendixes XIV Msg Num 3039 Message Text Explanation Action TMF tapemedia %1 already exists on node %2 with incompatible status or medium (not SCRATCH or not TAPE) The creation of volumes that must also be cataloged in TMF stops because a volume is already cataloged with a status different from SCRATCH. Check the status of the tape media in TMF. 3040 TMF is not configured on node %1 The Domain configuration specifies a TMF catalog on a Guardian node that is not configured for TMF. Check the TMF Guardian node in the Volume Group configuration. 3041 Add TMF media %1 on node %2 is rejected by TMFSERVE code %3 The cataloging of volumes in TMF catalog is rejected by TMF. Refer to the TMF Management Programming HP NonStop manual. 3042 Cannot start SPI %1 on node %2. Error %3 The Guardian node name of the Guardian tape catalog, DSM/TC or TMT, is unknown. Fix the Volume Group definition in the Domain configuration. Create volumes with different labels. Check the value of the TMF Guardian node, or DSM/TC Volcat that is started by a Guardian node. 3043 Info TMF media %1 on node %2 is rejected by TMFSERVE code %3 Access to the TMF catalog is rejected. Refer to the TMF Management Programming HP NonStop manual. 3044 Can not communicate with node %1 to start SPI %2 Access to the remote node is rejected by Expand. Refer to the Guardian Procedure Errors and Messages manual. 3045 Invalid configuration for Domain Manager. %1 The Domain configuration is invalid. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XV Msg Num 3045 Message Text Explanation A Volume Group is defined for cataloging the created volume in TMF, but the label type to create is not TMF. Fix the configurations of the Volume Group, or The volume group %1 catalogs in DSM/TC and allows only labelled volumes. A Volume Group is defined for cataloging the created volume in DSM/TC, but the label type to create is Unlabelled. Fix the configuration of the Volume Group, or 3048 Delete volume %1 in pool %2 catalog %3 rejected by MEDIASRV code %4 An error occurred while accessing a DSM/TC catalog. Refer to the DSM/TC Management Programming HP NonStop manual. 3049 Delete volume %1 in pool %2 catalog %3 failed An error occurred while accessing a DSM/TC catalog. No error code was supplied. Try to un-catalog the volume with a manual command in MEDIACOM. 3050 Delete media %1 in TMF catalog on node %2 rejected by TMFSERVE code %3 An error occurred while accessing a TMF catalog. Refer to the TMF Management Programming HP NonStop manual. 3052 Uncommitted transaction is aborted A TMF transaction did not end normally. Verify the results of the latest operation. 3053 SPI return-code %d in %s. %s An error code is returned by an SPI program. Refer to the TMF Management Programming, or DSM/TC Management Programming HP NonStop manual. 3047 The volume group %1 allows only TMF label type. Action Last Revised: Mar. 10, 16 Version 1.58 Create TMF label type. Create volume label type: ANSI or BACKUP. Appendixes XVI Msg Num Message Text Explanation Action 3054 Volume group cataloged for volume %s is unknown (%s) There is a discrepancy between the VT Controller catalog file (VOLUME) and the configuration file (BBSVCFG). Use the Web User Interface to recreate the Volume Group entry in the configuration. 3055 Invalid action %s in service %s Internal error. Contact ETI-NET Technical Support. 3056 Volume unloaded from device %s.%s. %s Feedback for successful load. None, unless the warning is issued. Then the unload was initiated by the domain manager to free a device that appears disfunctional. Check the is back to normal state – see message 5065. A warning can be associated: "Automatic UNLOAD on volume %s was performed. Virtual device %s is now deactivated." 3057 Error compiling regular expression %s for %s pattern %s. %s Internal error. Contact ETI-NET Technical Support. 3058 Update of %s rejected because it has been changed in parallel by %s at %s In the Web User Interface, the updated data was modified by another user since the data was read. Restart the operation for the beginning to check if the new data is still compatible with your targeted modification. 3059 Error for volume %s. The volume group %s allows only TMF label type Creating TMF volumes in a Volume Group from TMF is forbidden. Reserve TMF Volume Groups for TMF volumes. 3060 Error for volume %s. The volume group %s catalogs in DSM/TC and allows only labelled volumes It is not possible to create Unlabelled tapes in a Volume Group defined for tape cataloging with DSM/TC. Use specific Volume Groups that do not catalog the volumes to be created as Unlabelled volumes. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XVII Msg Num 3061 Message Text Explanation Action The status of TMF tapemedia %s on node %s must be SCRATCH or BAD, and its medium must be TAPE to allow deletion. It is not possible to delete a volume that contains a dump according to the TMF catalog. Correct the volume label to be deleted. 3062 MountId: %s.%Id. The volume label must be specified Internal error. Contact ETI-NET Technical Support. 3063 Invalid timestamp in %s. %s Internal error. Contact ETI-NET Technical Support. 3064 Incomplete %s reply from %s. Internal error or broken communication. Contact ETI-NET Technical Support if the problem repeats. 3065 Version %d not supported for document %s There is a version mismatch between EZX-Gateway components. Verify the installation. 3066 The volume group %s does not allow TMF label type TMF volumes can be created only in a Volume Group that asks for media cataloging in a TMF catalog. Use specific Volume Groups for TMF tapes, when a Guardian node is specified for the TMF cataloging. 3067 Invalid store type %d for store %s or volume %s A discrepancy occurred between the VOLUME file and the configuration file. Modify the Domain configuration to allow the operation to complete. Last Revised: Mar. 10, 16 Version 1.58 If you really want to destroy an active TMF dump, use TMFCOM to un-catalog the volume before the dump, or delete the tape media. Appendixes XVIII Msg Num 3068 Message Text Explanation Action Unexpected catalog status for the virtual volume %s. LabelType %s, lbMethod %d, defineClass %d, catalogStatus %d. Internal error. MountId: %s.%Id. Tape label mismatch, label in received request: %s, in pending mount: %s Internal error. Info pool %s catalog %s rejected by MEDIASRV code %d. %s Error querying a pool. 3071 Errors while analyzing the scratch status of virtual volume %s. LabelType %s, IbMethod %d, defineClass %d. Autoscratch not executed Internal error disabling the auto-scratch feature. Contact ETI-NET Technical Support. 3072 Virtual volume %s requested in DSMTC volcat:%s pool:%s, associated to volume group %s defined with volcat:%s and pool:%s. Check configuration The catalog location of a volume that is being loaded is not the same in DSM/TC and in the Domain configuration. Update the Volume Group configuration, or recatalog the volume(s) in DSM/TC to have the Domain configuration fit the DSM/TC catalog. 3069 3070 Last Revised: Mar. 10, 16 Contact ETI-NET Technical Support. Set the Volume Group to Auto-Scratch = False to bypass. Contact ETI-NET Technical Support. Set the Volume Group to Auto-Scratch False to bypass. Check the error explanation returned by MEDIASRV and included in the message. Refer to the DSM/TC Management Programming HP NonStop manual. Version 1.58 Appendixes XIX Msg Num Message Text Explanation Action 3073 MountId: %1.%2. Volume %3 loading on device %4. %5 A mount request was successfully initiated. The DataStore being configured with scripting, the execution of the restore script might delay the completion of the mount. None. 3074 Obsolete configuration tag '%s' in %s The Domain configuration contains obsolete parameters that block regular operations. Use the Web User Interface to edit the configuration, check the interpreted configuration parameters, and save the configuration to store it in the new format. 3075 Incompatible tags '%s' and '%s' in %s. An error is detected in Domain configuration. Use the Web interface to fix the configuration. 3076 Obsolete configuration tag '%s' converted in %s - check the conversion When reading the Domain configuration by the Web User Interface, obsolete parameters are interpreted to be presented to the user. Verify the parameters and update the configuration to have it saved in the new format. 3077 The disk pool is missing in the configuration of DataStore %s An error is detected in Domain configuration. Use the Web User Interface to fix the configuration. 3078 The password update of TSM node %s by %s at %s is not registered because of a newer update by %s at %s. Updates of the TSM node Password are not notified to the Domain Manager in chronological sort order. If connections to the TSM server are rejected for Authentication error, use the Web User Interface to reset the password in the Domain configuration. If required, set a new password in both the TSM server and the EZX-Gateway configuration. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XX Msg Num Message Text Explanation Action 3079 Unable to register the update of TSM node %s password by %s at %s Error prohibits the registration of a new TSM password in the Domain configuration. Fix any error logged in the previous minutes, re-enter the password in the Domain configuration. 3080 TSM password is missing for store %s. The Domain configuration contains an incomplete TSM DataStore definition. Enter the TSM node and password in the configuration of the DataStore. 3081 Sign on required to load %s without association to a mount request. Unexpected control flow makes the Domain Manager reject a load request. Contact ETI-NET Technical Support. 3082 Unexpected unload of %s-%s at %s not registered in the catalog. The unload refers to the operation %s at %s. The volume state in catalog is %s. The asynchronous feedback of statistics for the end of an emulator operation is rejected. Check the status of the volume (Current operation) in the domain catalog. Reset the “Current operation” if required. The stats of last operation might be lost. 3083 Message from %s %s %s received for the domain '%s', domain '%s' is expected. There is a discrepancy between the Domain configuration and a VT Controller control message. Make sure the Domain ID stored in all VT Controllers (entered in the “Domain Address” after a MS-Windows log-in) is equal to the Domain ID entered in the Domain configuration 3084 Volume %s not available, in use by %s operation started at %s. A load or an export operation is rejected because the volume is already in use. If the Current operation associated to the volume is out of sync, use the Web User Interface to update the Volume in the VT Controller catalog (Reset the current operation) Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXI Msg Num Message Text Explanation Action 3085 VT Controller %s is not a route to the store %s. The VT Controller specified for an Export or Import operation cannot access the DataStore holding the involved virtual volume. Check the Domain configuration and retry. 3086 Access to volume %s denied, %s. An operation on a volume is rejected because the user has not the required authorization. Check the volume owner and access authorizations in the Web User Interface. Eventually update this security setting on the volume to bypass the error. Revise the default access authorizations in the Volume group, the TAPE DEFINE of the application writing the volume (special keyword bbox-secure=rwc) 3087 The config dir is missing in the configuration of route %s to DataStore %s. The configuration of a DataStore in the Domain configuration is incomplete. Complete the Domain configuration 3088 MountId: %s. Invalid BBOXSECURE specification in the DEFINE mount message: %s. Invalid authorization specification. Refer to the Product description chapter of the Control of access to virtual volumes section. 3089 Invalid session key received from %s %s. Key length=%ld. %s. Internal error. Contact ETI-NET Technical Support. 3090 RSA error using public key of requester %s. %s. Internal error. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXII Msg Num Message Text Explanation Action 3091 RSA error using public key of server %s. %s. Internal error. Contact ETI-NET Technical Support. 3092 RSA error using public key of requester %s. %s. Internal error. Contact ETI-NET Technical Support. 3093 Encryption error %s. Internal error. Contact ETI-NET Technical Support. 3094 Volume %s is member of the volume group %s defined with DSMTC volcat %s and pool %s, but the tape volume is found in DSMTC volcat:%s pool:%s. Check configuration. Inconsistence between the state of a volume in DSM/TC and the state of the volume in the Domain catalog and configuration. Make sure the Domain configuration (specially the Volume groups) corresponds to the Guardian tape catalogs. 3095 Volume %s is member of the volume group %s defined with DSMTC volcat %s and pool %s, but the tape volume is not found in DSMTC catalog. Check configuration. Discrepancy between the state of a volume in the Guardian subsystem and the state of the volume in the VT Controller catalog and configuration. Make sure the VT Controller configuration (specially the Volume groups) corresponds to the Guardian tape catalogs. 3096 Volume %s is member of the volume group %s defined with TMF catalog %s, but the tapemedia is not found in TMF catalog. Check configuration. Discrepancy between the state of a volume in the Guardian subsystem and the state of the volume in the VT Controller catalog and configuration. Make sure the VT Controller configuration (specially the Volume groups) corresponds to the Guardian tape catalogs. 3097 Hash mismatch. Internal error. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXIII Msg Num Message Text Explanation Action 3098 Hash error %s. Internal error. Contact ETI-NET Technical Support. 3099 Volume %s label %s already exists in the domain catalog. An import operation must create a virtual volume. Import to another volume label, or delete the existing virtual volume. 3100 VT Controller %s is deactivated in the Domain configuration. An operation is rejected because the specified VT Controller is de-activated by configuration. Enable the specified VT Controller, or use another one. 3101 Volume %s label %s must be cataloged in %s %s before being imported, to be consistent with volume group %s. An import is requested for a volume that is not cataloged as specified in the volume group. Catalog the volume in DSMTC or TMF before importing it. 3102 VT Controller %s did not reply to a Connect message. A message is rejected by a VT Controller, most probably because IP filtering. Check the Domain address page in the Web page /Admin of this VT Controller. Check the MS Windows Event Viewer. 3103 BBCMD requires 2, but received %ld command parameters. Internal error in the EZX_START_XFER TACL macro. Contact ETI-NET Technical Support. 3104 Invalid version of VOLUME file: '%d', expected: '%d'. Discrepancy between the version of the VOLUME data file and the running BBSV program. Check the installation/upgrade just executed. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXIV Msg Num Message Text Explanation Action 3105 Excessive length of %s's reply: %u. Total expected: %u. Already received: %u. Internal error in TCPIP communications with an EZX MVS Agent. Contact ETI-NET Technical Support if the problem repeats. 3106 Invalid length in header received from %s: %u. Maximum expected length. Internal error in TCPIP communications with an EZX MVS Agent. Contact ETI-NET Technical Support if the problem reoccurs. 3107 MountId: %s. Volume %s. Invalid keyword '%s' in the mount message of TAPE DEFINE. A load request is rejected because an unexpected content of the TAPE DEFINE. BackBox product: check the bbox-secure syntax. MountId: %s. Volume %s. Equal sign missing after keyword '%s' in the mount message of TAPE DEFINE.. A load request is rejected because an unexpected content of the TAPE DEFINE. BackBox product: check the bbox-secure syntax. 3109 MountId: %s. Volume %s. MVS Dataset name '%s' exceeds 44 characters in the mount message of TAPE DEFINE. The DSN of an MVS dataset is limited to 44 characters Check the execution of the EZX_START_XFER macro that must be run to build the TAPE DEFINE. 3110 MountId: %s. Volume %s. MVS Conversion id '%s' exceeds %d characters in the mount message of TAPE DEFINE The conversion specification is limited to 12 characters. Check the execution of the EZX_START_XFER macro that must be run to build the TAPE DEFINE. 3108 Last Revised: Mar. 10, 16 Version 1.58 EZX product: be sure to use the EZX_START_XFER macro to build the TAPE DEFINE. EZX product: be sure to use the EZX_START_XFER macro to build the TAPE DEFINE. Appendixes XXV Msg Num Message Text Explanation Action 3111 MountId: %s. Volume %s. MVS Dataset name (DSN=) is missing in the mount message of TAPE DEFINE. A TAPE DEFINE asking for a virtual volume created for EZX operation was not correctly created by the EZX_START_XFER macro. Check the execution of the EZX_START_XFER macro that must be run to build the TAPE DEFINE. 3112 %ld MVS datasets %s ready for transfer through EZX volume %s for %s.%s %s. (%ld tracks, %s bytes). %s. (MVS time: %s) The EZX_START_XFER macro prepared successfully the MVS datasets for the transfer, eventually created them. None. 3113 MountId: %s. EZX MVS Agent reject the transfer through EZX volume %s. %s. The execution of the EZX_START_XFER macro or the processing of a mount request for EZX is rejected by the EZX MVS Agent. Check the error text returned by MVS at the end of this message. The Domain Manager receives a mount request that is no more in the list of MEDIACOM pending mounts. Check the EMS log to identify why the mount request was cancelled. 3114 Pending mount request not found for the EZX volume %s Check the MVS console. Verify the EZX_START_XFER macro parameters. Resubmit the job. 3115 Invalid store type %d in catalog record to write for the virtual volume: %s-%s. Internal error. Contact ETI-NET Technical Support. 3116 Specified number of MVS file segments: %ld ignored, actual number processed: %ld for EZX volume %s. Unexpected number of dataset names returned by the EZX MVS Agent. Contact ETI-NET Technical Support if the problem repeats. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXVI Msg Num Message Text Explanation Action 3117 Number of MVS file segments specified at start time: %ld ignored, actual number processed: %ld for EZX volume %s. The number of MVS datasets returned by the EZX MVS Agent changed between the time of EZX_START_XFER macro and the time of load request. Verify the variation of the number of MVS datasets in the group participating to a transfer. 3118 MVS Dataset(s) %s deallocated after EZX operation on volume %s. Transfer ended with %severity [, forced unload | at load time]. %s records transferred. EZX MVS Agent released the datasets, after a transfer is executed or aborted. None. Current operation (%s) of volume %s manually reset in the catalog of virtual volumes A user reset the current operation by using the Web application. 3119 The message severity is set according the severity reported by the VTC. None. The MVS dataset are released. Any running transfer with the same tape volume is not impacted. There should normally be no running transfer when a user reset the current operation. 3120 Volume %s manually unloaded. Last Revised: Mar. 10, 16 A manual unload is commanded by the Web application, cancelling any running transfer in hard way. Version 1.58 None. Appendixes XXVII Msg Num Message Text Explanation Action 3121 Current operation (%s) of volume %s not reset because of error in communication with EZX MVS Agent that has allocated the dataset(s) An attempt to “Reset current operation" of the volume by the Web application is rejected because of an error in the communication with the MVS Agent. Wait for MVS Agent availability to retry the “Reset current operation”. 3122 The configuration of DataStore %s contains an invalid Guardian User ID pattern: '%s' Syntax error in BBSVCFG file. Fix the Guardian User ID pattern using the Web application. 3123 MountId: %s. Guardian User ID %s not authorized to access the DataStore %s (volume %s) The User ID running the tape application is not authorized to access the DataStore. Update the security table of the DataStore using the Web application. 3124 VT Controller %s returned code %ld to the query of DE XP configuration The discovery of DE XP volume in a VTC does not work. Check the connection to the XP Array. 3125 Error communicating with VT Controller(s):%s List of VT Controllers that the Domain manger attempted to contact without success. Refers to detailed error messages in the EMS log. The EZX_START_XFER macro is requested for an unknown tape volume. Check VOLUME parameter of the EZX_START_XFER macro. FILE ID is a mandatory parameter. Check FILE ID contains a valid MVS DSN. 3127 3128 EZX_START_XFER VOLUME '%s' is missing or unknown (%s.%s %s) "EZX_START_XFER FILE ID '%s' missing or invalid (%s.%s %s) Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXVIII Msg Num Message Text Explanation Action 3129 START_XFER CONVERSION '%s' should be 'ASCII-EBCDIC' or 'JIS-EBCDIC' (%s.%s %s) Invalid CONVERSIN Parameter. Check CONVERSIN parameter. 3130 Error computing MVS track capacity for MVS volume %s, EZX volume %s. %s Internal error. Contact ETI-NET Technical Support. 3131 MountId: %s. USE %s in the TAPE DEFINE does match and overrides the USE %s recorded by EZX_SETUP_XFER The attributes of a mount request does not match the parameter of the latest EZX_START_XFER macro executed for the tape volume. Check the proper execution of the EZX_START_XFER. This is a warning. 3132 EZX_START_XFER R_BLKSIZE is missing (%s.%s %s). R_BLKSIZE is mandatory when MVS dataset must be created. Complete EZX_START_XFER macro. 3133 EZX_START_XFER R_LRECL is missing (%s.%s %s). R_LRECL is mandatory when MVS dataset must be created. Complete EZX_START_XFER macro. 3134 EZX_START_XFER R_RECFM is missing (%s.%s %s). R_RECFM is mandatory when MVS dataset must be created. Complete EZX_START_XFER macro. 3135 MountId: %s. Current operation '%s' is not valid for loading the EZX volume %s. The current operation is not valid. Verify the correct execution of EZX_START_XFER macro. 3136 No MVS disk model known with track length %ld. MVS volume %s, EZX volume %s. %s The EZX MVS Agent returned a DISK track length not yet supported by EZX Domain Manager Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXIX Msg Num Message Text Explanation Action 3137 Error computing MVS dataset allocation for disk %s, EZX volume %s. %s Internal error. Contact ETI-NET Technical Support. 3138 MVS dataset %s allocated for transfer through EZX volume %s for %s.%s %s. %s Successful lock of MVS dataset when processing a mount request. None. 3139 Estimated data size to send (%s MB) requires the creation of %ld MVS datasets. Maximum number of datasets %s is %ld. EZX volume %s for %s.%s. Unable to create MVS dataset able to contain the specified TRFSIZE. Be sure the FILEID allows creating a group of datasets (ends by ".EZX") Estimated data size to send (%s bytes) exceeds the capacity of the %ld existing MVS dataset(s) %s (%ld tracks, %s bytes). EZX volume %s for %s.%s. (MVS time %s) The transfer is rejected because the TRFSIZE specifies a size exceeding the capacity of MVS datasets to write Recreate the MVS datasets and revise TRFSIZE. The total size (%ld tracks, %s bytes) of %ld existing MVS dataset %s exceeds the estimated data size to receive (%s bytes). EZX volume %s for %s.%s. (MVS time %s) The transfer is rejected because the TRFSIZE specifies a size that can not contain the capacity of MVS datasets to read The MVS dataset tested size is the allocated size, not the used size. 3140 3141 Revise the maximum allocation configured in the Domain configuration, DataStore tab. Remove the TRFSIZE parameter to disable this validation. Use SPACE = (,RLSE) when writing the MVS dataset to release unused space. Revise TRFSIZE. Remove the TRFSIZE parameter to disable this validation. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXX Msg Num 3142 Message Text Explanation MountId: %1.%2. DE-XP error %3 loading %4 on %5 %6. %7. Load to be retried A VT Controller is not able to access a DE XP volume. Other routes configured in the DE XP volume will be tried. The failed load will be retried at the same frequency as the “busy drive” condition. Action 1- Force the discovery of DE XP volumes by the VT Controllers, by inquiring the list of DE XP volumes of the domain through the Web application, Data Exchange tab. Check if the volume is seen by the VT Controller trying to load a virtual media. 2- Have the DE XP volumes reconnected to the proper VTC(s) 3143 FILEID must be specified The FILEID parameter is missing in an EZX macro Specify the FILEID to name the MVS dataset involved by the opertion. 3144 MVS dataset %s must be freed by resetting the current operation of volume %s through the web application. The EZX_FREE_MVS_DATASET cannot be used when the MVS dataset can be freed via the Web application. In the Web application, display the detail of the involved tape volume, edit it and reset the Current operation. 3145 Invalid BBCMD parameters. Keyword '%s' is unknown. Invalid TACL program parameters for BBCMD. Verify EZXSETUP parameters. 3146 Invalid BBCMD parameters. Value missing for keyword %s. Invalid TACL program parameters for BBCMD. Verify EZXSETUP parameters. 3147 Invalid BBCMD parameters. '%s' is not a valid value for %s Invalid TACL program parameters for BBCMD. Verify EZXSETUP parameters. 3148 Invalid BBCMD parameters. %s parameter is missing Invalid TACL program parameters for BBCMD. Verify EZXSETUP parameters. 3149 Manual freeing of MVS dataset %s, tape volume %s. The EZX_FREE_MVS_DATASET was executed Verify EZXSETUP parameters. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXI Msg Num Message Text Explanation Action 3150 BBCMD stops retrying sending a '%s' message to the Domain Manager after %ld retries. The retry limits specified in EZXSETUP are reached. BBCMD and the current TACL macro end with error. Check the cause of errors in previous messages and in EMS log. 3151 VOLUME or STOREID must be specified to free an MVS dataset. The macro EZX_FREE_MVS_DATASET must specify one of these two parameters Complete the call to EZX_FREE_MVS_DATASET 3152 Automatic unload of volume %s, after an unrequested load on %s.%s An unrequested EZX tape volume was loaded, the EMS message #640 'UNREQUESTED ANSI TAPE' is logged. This condition is not acceptable for regular EZX transfers and the volume is automatically unloaded. Verify the automatic unload is appropriate for the case. No automatic unload of volume %s, after an unrequested load on %s.%s. %s The EMS message #640 'UNREQUESTED ANSI TAPE' is logged, but the state of the unrequested volume is not consistent. Verify the conditions of current transfer. 3153 Last Revised: Mar. 10, 16 Version 1.58 This condition occurs when the tape application program stops or abends just during the processing of the load, or the tape volume recognition. To manually get rid of an unrequested load, use the Inload command on the Home page of the Web application. This will unload the volume, reset the current operation of the volume, and deallocate the MVS datasets. Appendixes XXXII Msg Num 3154 Message Text Explanation MountId: %s. Volume %s. MVS DSN %s in the TAPE DEFINE does not the match and overrides the DSN %s recorded by EZX_SETUP_XFER macro for volume %s. Mismatch between the data received by the Domain Manager when the EZX_START_ZFER macro executed, and when the mount request was issued by $ZSVR. Action Check the execution of the EZX_START_XFER macro that should be run to build the TAPE DEFINE. This is a warning. 3155 EZX_START_XFER R_RECFM=%s R_LRECL=%ld R_BLKSIZE=%ld: {DCB-error-text}. Volume %s (%s.%s %s) The consistency check failed on the DCB parameters (RECFM, LRECL,BLKSIZE) of the MVS dataset. Error is specified by the DCB-error-text. Check the DCB parameters of the EZX_START_XFER macro. 3156 MountId: %s. Device '%s' requested to load %s is not on a VTC that is an active route to the DataStore %s. The device requested to load a volume is not emulated by a VTC that is active and that is a route to the DataStore. Check the Domain configuration: - the VTC is a route to the DataStore associated to the tape volume - the VTC is active. 3157 VTC %s rejects the unloading of volume on device %s.%s with error %ld %s. An unload command is rejected by the VTC. Check the error condition reported in the message. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXIII Msg Num 3158 Message Text Explanation Completion of operation (%s) of volume %s can not be communicated to the MVS Agent that has allocated the dataset(s). Current operation changed to POST_TRF. A communication error prevents to send the transfer completion data to MVS. The MVS dataset is still locked and the MVS audit file is not updated. Action When the communications with MVS are reestablished, the next scan of volume status will retry the MVS communication. Ref: 10. Configure and Start the EMS Extractor The retry can be triggered manually: use the Web application to "reset the current operation" of the tape volume. A successful communication will unlock the MVS dataset and register the actual completion (may be a failure or a success) of the transfer in the MVS audit file. 3159 State of volume %s does not match. VTC reports %s. Domain manager reports %s. Device %s.%s Discrepency between states in the domain manager and states in a VTC. The processing of the current event might be aborted. Check possible other messages in EMS. Check the result of the event processing: state of the involved volume and device in NSK MEDIACOM, in the BackBox domain catalog. To clear inconsistent conditions: - restart the device in SCF - use the web application to reset the current operation of the volume 3160 Volume loaded on device %s.%s does not match. Guardian reports volume '%s'. Domain manager reports volume '%s'. Discrepency between states in the domain manager and the Guardian tape system. The processing of the current event might be aborted. Check possible other messages in EMS. Check the result of the event processing: state of the involved volume and device in NSK MEDIACOM, in the BackBox domain catalog. To clear inconsistent conditions: - restart the device in SCF - use the web application to reset the current operation of the volume Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXIV Msg Num Message Text Explanation Action 3177 POST_TRF scan: %ld volumes read, %ld volumes found in operation state POST_TRF, current operation reset for %ld volumes A scan of volumes for POST_TRF state completed, and provides execution statistics. None. 3178 VOLUME scan: another scan is still executing. New scan skipped A scan of volumes starts when another did not complete yet. None. Disk model mismatch for EZX volume %s Dataset %s. MVS volume %s is model %s, DataStore %s is configured for model %s The volume of an MVS dataset has a geometry 3380/3390 that does not match the domain configuration. Contact ETI-NET Technical Support. 3501 CONNECT to BB-DOMAIN SERVER failure, error %1 The EMS Extractor failed to connect to the Domain Manager. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 3502 WRITE to BB_DOMAIN SERVER failure, error %1 The EMS Extractor failed to connect to send data to the Domain Manager. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 3503 READ from BB_DOMAIN SERVER failure, error %1 The EMS Extractor failed to connect to read data from the Domain Manager. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 3505 PENDING-REPLY msg: %1 A GET Pending Mounts was rejected by the Domain Manager to the EMS Extractor. Refer to the reply message of the Domain Manager. 3179 Last Revised: Mar. 10, 16 The new scan is not executed. Version 1.58 3390 is the default value and the regular disk geometry. 3380 geometry is partially supported for testing purpose only. Appendixes XXXV Msg Num 3506 Message Text Explanation Action Max Retries (%1) reached for load request %1 on %2. No more retry The number of retries reached the max-failsafe-retries configured for the EMS Extractor. Check the status of virtual devices. 3507 MAX-PENDING-MOUNTS(%1) reached An internal limit was reached. Contact ETI-NET Technical Support. 3508 BBEXT must be started by a user in SUPER group, current user: %1 The EMS Extractor must run under a User ID in the SUPER group. Restart BBEXT with a User ID in the SUPER group. 3509 Running BBEXT requires infile: run BBEXT/in BBEXTCFG ,name/ BBEXT needs a configuration file in its standard input. Check the TACL RUN command, or the SCF definition that registers BBEXT as a permanent process. 3510 Unable to get required parameter from EMS-event: %1 error, ignoring this mount BBECT is unable to extract a tape-related event from EMS. None, if no other symptoms occur. 3511 %s loaded in EZX-Gateway at %s for mount request %ld, but the request is still pending. Load being retried A volume load was successful, but the mount Id is still in the list of pending mounts. Check the outcome of the retry. Last Revised: Mar. 10, 16 A new attempt is executed. Version 1.58 Check the BBEXTCFG configuration file. Appendixes XXXVI Msg Num 3512 Message Text Explanation Loading of %s initiated in EZXGateway at %s for request %ld, but the request is still pending A volume load was successfully initiated, but the mount Id is still in the list of pending mounts. Action Check the log of the restore script. A restore script was initiated but did not complete successfully yet. 3513 BBEXT config error: %s There is an error in BBEXTCFG file. Refer to the BBEXT section of the Installation chapter. 3514 BBEXT cannot open EMS filter file %s, errno=%d The EMS filter file named by the tag <emsFilter> in BBEXTCFG can not be opened. Check the reported Guardian error code. 4001 MVS Storage size = [EZX_MVS_STORAGE_SIZE] bytes Information display of the number of bytes the remote MVS dataset(s) can contain. None. 4002 '[param]' is not valid for TRFSIZE TRFSIZE parameter of the EZX_REMOTE_SUBMIT TACL macro is invalid. Refer to the description of macro in this manual NonStop Application Interface section. 4003 Error [rc] in #DEFINESETATTR [attrname] [value] Error returned by the TACL function #DEFINESETATTR. Refer to the HP document TACL reference. 4004 Expecting a remote MVS dataset name A parameter of the EZX_START_XFER TACL macro is invalid. Refer to the description of macro in this manual NonStop Application Interface section. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXVII Msg Num Message Text Explanation Action 4005 DEFINE [defname] already exists The EZX_START_XFER macro cannot add the specified DEFINE name. Choose a different DEFINE name or delete the DEFINE before the macro call. 4006 Expecting a BCOM requestname A parameter of the EZX_REMOTE_SUBMIT TACL macro is invalid. Refer to the description of macro in this manual NonStop Application Interface section, and the BCOM on Tandem User guide. 4007 Unable to add the DEFINE [defname], [rc] A #DEFINEADD was rejected during the execution of the EZX_REMOTE_SUBMIT TACL macro. Check the output of SHOW DEFINE that follows the message and that can display a consistency check number. Check numbers are described in the HP manual DSM Tape Catalog User Guide, Consistency check section. Refer the HP manual TACL (Reference : Appendix B Error codes) 4011 BCOM request-name '[reqname]' must begin by '#' A parameter of the EZX_REMOTE_SUBMIT TACL macro is invalid. Refer to the description of macro in this manual NonStop Application Interface section, and the BCOM on Tandem User guide. 5000 Error %1 starting the Tape Emulator Error at service startup in a VT Controller. Contact ETI-NET Technical Support. 5001 Error opening the configuration file (%1): %2 The internal configuration file of a VT Controller is not available. Contact ETI-NET Technical Support. 5002 Configuration file contains invalid parameter (%1) The internal configuration file of a VT Controller is invalid. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXVIII Msg Num Message Text Explanation Action 5003 Error loading SCSI DLL (%1) Internal error at VT Controller startup. Contact ETI-NET Technical Support. 5004 Error creating the Virtual Tape Infrastructure Internal error at VT Controller startup. Contact ETI-NET Technical Support. 5005 Error creating the Storage infrastructure Internal error at VT Controller startup. Contact ETI-NET Technical Support. 5006 Error processing the start sequence of tape Emulator Internal error at VT Controller startup. Contact ETI-NET Technical Support. 5007 Device has no entry in configuration file (%1) Internal error at VT Controller startup. Contact ETI-NET Technical Support. 5008 Device %1.%2 already in use by tape %3 A load request is rejected by the VT Controller because a volume is already mounted on the virtual device. Manual load: Choose an alternate device, or retry later. Automatic load: Wait for automatic retries. 5009 Error malloc for storage (%1) Internal error in VT Controller at load time. Contact ETI-NET Technical Support. 5010 Error opening the WINFILE storage (%1-(%2)) Open rejected by the Windows file system in the VT Controller. Refer to the Microsoft documentation. 5011 Error reading the WINFILE storage (%1-(%2)) Read rejected by the Windows file system in the VT Controller. Refer to the Microsoft documentation. 5012 Error writing the WINFILE storage (%1-(%2)) Write rejected by the Windows file system in the VT Controller. Refer to the Microsoft documentation. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XXXIX Msg Num Message Text Explanation Action 5013 Error in the root structure of the WINFILE storage (%1) The indexed Windows file for the specified virtual volume was corrupted. Contact ETI-NET Technical Support. 5014 Device not in use A SCSI command was received for a device that has no volume loaded. The device is ready to load a volume. 5015 Device not found for tape %1 A VT Controller received a load or an unload command for a device not defined in the VT Controller internal configuration. Contact ETI-NET Technical Support. 5016 Error deleting the WINFILE storage (%1-(%2)) Delete file rejected by the Windows file-system in the VT Controller. Refer to the Microsoft documentation. 5017 Error getting disk free space on %1 (%2) Impossible to get the amount of free space on disk. If the error occurs on a local disk, contact ETI-NET Technical Support. For WINFILE storage, the VT Controller will assume that there is enough free space to write the volume to process. For remote disks, check authorizations and functionality of non MS-Windows servers. 5018 Error getting full path name on %1 (%2) Impossible to get full path name of a disk location for WINFILE. Check the syntax and availability of the Master path and Data paths configured in the DataStore. 5019 Missing Open Arguments for %1 Internal error. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XL Msg Num Message Text Explanation Action 5020 Not enough free disk space for %1 There is not enough disk space for the operation. Refer to the Installation chapter, in the Configure the EZX-Gateway Domain section. 5021 Label type (%1) not supported for %2 Internal error. Contact ETI-NET Technical Support. 5022 Tape %1 already in use by another device The volume is already used by another device. Try a manual load. Error getting the file size of %1 (%2) Error getting attributes of a disk file in a WINFILE DataStore. Contact ETI-NET Technical Support. 5024 Cannot launch thread %1 (%2) for Storage (%3) Internal error. Contact ETI-NET Technical Support. 5025 Error executing the script [%1] (%2) for Storage (%3) Error in script execution. Log on to the operating system in the VT Controller to check: 5023 If the problem re-occurs, reset the VTC whenever possible. For remote disks, check authorizations and functionality of non MS-Windows servers. The Windows Event Viewer The log of the script 5026 Maximum launch of [%1] reached for Storage (%2) Error in script execution. Refer to previous error messages. 5027 Error No TSM scripting for Storage (%1) Scripting is not supported for TSM Data Stores. Remove scripting from the configuration of TSM Data Stores. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLI Msg Num Message Text Explanation Action 5028 Error setting environment variable %1 (%2) for Storage (%3) Error setting a named Windows parameter for the script execution. Check that the name and value of the parameters configured for the DataStore are syntactically valid for MS-Windows. 5029 The script [%1] has been submitted for Storage (%2) A script is stared in the VT Controller. None. 5030 The script [%1] terminated with a return code of %2 for Storage (%3) A script has ended. Check that the return code is zero. 5031 Error %1 starting the Tape Emulator Administration Internal error. Contact ETI-NET Technical Support. 5032 Device (%1) has no SCSI activity A command is received on a device that has no SCSI activity. Verify the SCSI target Ids in configuration. 5033 Multiple copies (%1) found for the file (%2) There are multiple copies of the same virtual volume in the disk pool of a Windows file DataStore. Verify the version of the files, leave only an index file (*.IND) and a data file (*.DAT) for a given volume. 5034 The file was not found (%1) The Emulator does not find a file for a virtual volume of a Windows file DataStore. Restore the two files (*.IND and *.DAT) of the virtual volume. 5035 There is no valid data path in the pool for (%1) All disk paths configured for the pool of a Windows DataStore are invalid. Restore the availability of the paths, or configure a new path that will receive the SCRATCH volumes to be written, and the volumes to be restored by the restore script. If not zero, log on to Windows on the VT Controller to check the script output. No operation is possible. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLII Msg Num Message Text Explanation Action 5036 An invalid path [%1] is still configured for (%2) Windows DataStore: the file of a virtual volume cannot be accessed because the path is invalid. The Emulator does not search in alternate locations because the path is still configured. Restore the disk path, or remove the path from the pool configuration to allow the Emulator search in other paths of the pool or execute the restore script. 5037 Wrong path found [%1], expected path [%2] for (%3) Windows DataStore: a file was found in an unexpected path. Explain the new location. Move the proper file in the expected location. 5038 Invalid path in Configuration [%1] A path configured in a Windows file DataStore is unavailable or invalid. Restore the disk path, or remove it from the configuration to allow the VTC Emulator search in alternate locations the files cataloged to be in this path. 5039 File not found on Load for (%1) Windows DataStore: a file is not found. Restore the file. 5040 Processing stops due to volume load operation error (%1) for (%2) A volume load fails. A possible reason is that a restore script does not complete with returncode zero. Refer to the log of the script. Fix the error condition or manually execute the restore. 5041 WRITE operation is denied for (%1) A WRITE operation is received through the SCSI bus to a volume loaded with “Read Only” attribute. This symptom can show up if a volume is mounted via the Stand Alone Load Web page, and the NonStop application tries to write on the virtual volume. Have the mount request for regular tape activity solved automatically solved by the EMS Extractor, or by the manual load that is available through the Domain Manager. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLIII Msg Num Message Text Explanation Action 5042 A Volume Load Operation has been cancelled for (%1) An Unload command cancels the execution of a load volume. None. 5043 Running [FetchData] operation for (%2) A pre-fetch operation is started for loading a virtual volume kept in a TSM DataStore. None 5044 Cannot write tape device %2 : %3 An export fails when writing to the MS Windows attached tape device. Check the identification of the device in MS Windows. Check the MS Windows Event log and the Guardian EMS log. Reset the tape device. 5045 Exporting virtual volume %1 to physical volume %2 terminate with error An export failed. Check the MS-Windows Event log and the Guardian EMS log for previous errors 5046 Exporting virtual volume %1 to physical volume %2 completed successfully Successful export. Take the media out of the MS-Windows device. 5047 Error getting object from [%1] (%2) for Storage (%3) Error accessing data in a TSM server. See ‘Errors returned by TSM’ at the beginning of this appendix. 5048 Error sending new TSM password in [%1] (%2) for Storage (%3) A TSM password renewal fails. See ‘Errors returned by TSM’ at the beginning of this appendix. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLIV Msg Num Message Text Explanation Action 5049 Error sending end of volume in [%1] (%2) for Storage (%3) The notification of the end of an operation to the Domain Manager fails. Using the Web User Interface, check in the Volume detail if any current operation is still registered. If yes, verify the actual status of the volume. If the current operation is wrong, reset it (Volume details, Edit button, and Reset current operation). 5050 Exporting virtual volume %1 to physical volume %2 started successfully An Export operation is successfully initiated. None. 5051 Importing physical volume %1 to virtual volume %2 started successfully An Import operation is successfully initiated. None. 5052 Importing physical volume %1 to virtual volume %2 terminates with error. An import fails. Check the MS Windows Event log and the Guardian EMS log for previous errors. 5053 Importing physical volume %1 to virtual volume %2 completed successfully An import completes successfully. None. 5054 The physical volumes %1 label match user's entry The label of a physical volume to import matches the user entry. None. 5055 The physical %1 volume %2 label does not match user's entry. The label of a physical volume to import does not match the user entry. Unload and reload the proper volume on the tape drive attached to the VT Controller. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLV Msg Num Message Text Explanation Action 5056 The physical tape device %1 doesn't support %2 features The tape drive attached to a VT Controller for import/export operations misses a required feature. Install proper device. 5057 (%1) VT Controller cannot reach the MVS Volume %2 The DE XP MVS volume is not visible in Windows, or the access to this volume is rejected by FAL. Verify the configuration and status of the DE XP volumes for the VTC. Display the list of DE XP volumes from the Web application to verify the list of DE XP volumes seen by the VTC after an autorediscovery. 5058 (%1) EZX Discovery error: %2. Error while discovering the list of DE XP volumes in the list of physical devices known by the Windows operating system. Verify the configuration and status of the DE XP volumes for the VTC. 5059 Device %1 BUSY while checking usage of tape %2 A volume load is rejected because a virtual tape device is busy. Retry the operation. 5060 Mismatch on MVS disk model received (%1) and model found (%1) The model of DE XP disk volume reported by the EZX MVS Agent does not match the model reported by the volume discovery executed in Win2003. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLVI Msg Num Message Text Explanation Action 5061 Virtual Tape Device %1 STARTED The VTC Emulator reports the successfully start of the named virtual tape device. Occurs at the first SCSI command send by the NSK tape system. Note: the VTC Emulator used the Guardian device name enter in the VTConfig.txt file. None. 5062 Virtual Tape Device %1 STOPPED The VTC Emulator reports the normal stopping of the named virtual device. Occurs when the service shuts down. Note: the VTC Emulator used the Guardian device name enter in the VTConfig.txt file. None. 5063 Virtual Tape Device %1 DOWN For the named virtual device, the VTC Emulator encountered an error condition that can not be recovered without restarting the virtual device. The host will send a bus reset. The tape applications using any device on the same bus will abort. The host will then try to reconnect to all devices of the bus to recover a normal state. Resubmit the tape applications. Note: the VTC Emulator used the Guardian device name enter in the VTConfig.txt file. Last Revised: Mar. 10, 16 Version 1.58 If the message 5061 does not show for the named device and the NSK tape system continues to report error on the device, STOP the device in SCF. Then, reset the VTC as soon as possible depending on the current work schedule and the performance of other devices. Appendixes XLVII Msg Num Message Text Explanation Action 5064 Virtual Tape Device %1 REACTIVATED The VTC emulator received again SCSI activity from the host, for a device internally deactivated because of lack of SCSI activity. None. 5065 Virtual Tape Device %1 DEACTIVATED The VTC emulator did not received any commands from the host since 3 minutes. It will reject load commands from the domain manager. This state is not harmful if the device is not in use and not needed. This EMS message is most often followed by an other EMS message from the NSK tape system reporting a tape io error (timeout). The message 5064 can show up several hours later. Error reported by the Windows software implementing the DataStore (such as TSM API, or DE-XP FAL). Refer software documentation. 6000 (BBSL) %1 (%2) Check the device was re-activated later (message 5064), or check interactively by SCF STATUS $drive. If the device stays disconnected, then the VTC must be reset. IBM Tivoli Messages manual. Hitachi FAL DE-XP manual. 6001 Cannot Initialize the API to TSM storage library (%1)) The Tivoli Storage Manager API returned an error. Refer to the IBM Tivoli Messages manual. 7000 Label VOL1 is missing for storage (%1)) Internal error. Contact ETI-NET Technical Support. 7001 Label HDR1 is missing for storage (%1)) Internal error. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLVIII Msg Num 7002 Message Text Explanation Modifying a volume label is not allowed. Storage (%1)) Action The VT Controller does not allow the Relabelling of a virtual volume with a different label. Relabelling is only supported to get rid of non-expired data files on a virtual volume. The regular procedure is to delete a virtual volume and then recreate it. 10000 Error during XML Parsing: %1 %2 Internal error. Contact ETI-NET Technical Support. 10001 The requested function(%1) is not supported Internal error. Contact ETI-NET Technical Support. 10002 Compatibility Error, (%1) version (%2) is not supported There is a version mismatch between VT Controller components. Verify the installation. 10100 Error parsing the IPFiltering config (%1) (%2) Internal error. Contact ETI-NET Technical Support. 10101 IPFiltering address list has not been refresh due to configuration error, old address list is still active Internal error. Contact ETI-NET Technical Support. 10102 IPFiltering address list has been successfully refreshed from the updated configuration file The update of the Domain TCP/IP address(es) is being propagated. None. Last Revised: Mar. 10, 16 Version 1.58 Appendixes XLIX Msg Num Message Text Explanation Action 10103 Connection from %1 has been rejected due to IPFiltering security The VT Controller receives a control message from an address that is not in the list of the Domain TCP/IP address(es). Find out the source of the message. 10104 Couldn’t retrieve the registry key for the Profile.xml used for IPFiltering Internal error. Contact ETI-NET Technical Support. 28000 EZX JOB using volume <JOB> from <DOMAIN> with DSN <DSN> is rejected, a job with the same DSN is already executing. The EZX MVS Agent does not accept two consecutive locks on the same dataset – except when they come from the same Domain Manager for the same tape volume label. Serialize EZX transfers to/from the same MVS dataset. 28001 EZX JOB with DSN <DSN> from <DOMAIN> using volume <VOLUME> is rejected: unable to allocate a XFER handle to execute the job Internal error. Contact ETI-NET Technical Support. 28002 EZX JOB from <DOMAIN> using volume <VOLUME> is rejected, transfer direction is invalid <DIRECTION> Internal error. Contact ETI-NET Technical Support. Last Revised: Mar. 10, 16 Version 1.58 Appendixes L Msg Num 28003 Message Text Explanation EZX JOB from <DOMAIN> using volume <VOLUME> is rejected, error allocating dsn (<DSN>) : <RC> Error in dynamic allocation of the MVS dataset. To interpret <RC>, refer to the IBM document "MVS Auth Assembler Services Guide ", Section “Interpreting Error Reason Codes from DYNALLOC". Action See possible other system error messages for the DSN being allocated in the BCOM MVS job log. Verify the parameters of EZX_START_XFER macro. Verify the allocation specifications configured for the DataStore associated to the tape volume. The RC is displayed in decimal base. 28004 END-TRANSFER for EZX JOB with DSN <DSN> from <DOMAIN> using volume <VOLUME> is ignored, the job is not currently active An out-of-sequence end-oftransfer message is ignored. 28005 Message from Domain Manager is rejected the operation <OPERATION> is not supported Internal error, software version mismatch. Contact ETI-NET Technical Support. 28006 EZX Domain Manager report completion for <DOMAINID> <VOLUME> : <TEXT> The NonStop side reports the end of transfer. None. 28007 Dataset locked successfully for <DOMAIN>: <VOLUME>, <NUMDS>-<DSN> Successful lock at beginning of transfer. None. Last Revised: Mar. 10, 16 This message can be the result of a systematic cleanup after a previous error. Contact ETI-NET Technical Support if this message is not explained by the operational context. Version 1.58 Appendixes LI Msg Num Message Text Explanation Action 28008 Dataset unlocked successfully for DSN <DSN> from <DOMAIN> using volume <VOLUME> The end-of-transfer unlock is successful. None. 28009 Job <VOLUME> domain <DOMAIN> , lock the dataset <DSN> again A second successive lock comes for the same dataset and is accepted by the EZX MVS Agent. None. 28010 JOB <VOLUME> from <DOMAIN> successfully created/queried <NUMDS><DSN> The Domain Manager prepared the dataset(s) to be involved in an EZX transfer. None. Last Revised: Mar. 10, 16 Version 1.58 Appendixes LII Msg Num 28011 Message Text Explanation JOB <VOLUME> from <DOMAIN> failed to create/query <DSN>: <CODE> Action An MVS dataset cannot be prepared for an EZX transfer. (TBINFOVOL, rc 8, reason 8) means that the dataset is not found. CODE, RC and REASON are displayed in decimal base. Check the parameters of the TACL EZX_START_XFER macro and the Domain configuration of space allocation of the DataStore associated to the tape volume. When MODULE=TBINFOVOL: cannot find the dataset volume through the LOCATE macro. LOCATE return codes: Refer to the IBM document "DFSMSdfp Advanced Services", "Return codes from LOCATE" (<MODULE> [, rc <RC>, reason <REASON>]). RC and REASON are returned by the LOCATE macro. When MODULE=TBDSINFO: cannot find dataset info through the OBTAIN macro. RC is returned by the OBTAIN macro. OBTAIN return codes: Refer to the IBM document "DFSMSdfp Advanced Services", "Return codes from OBTAIN" When CODE=32: Cannot get DSCM format-4 When MODULE=B62FileAllocate: the file cannot be created by the DYNALLOC macro. CODE is returned by DYNALLOC macro. Last Revised: Mar. 10, 16 Version 1.58 DYNALLOC return codes: Refer to the IBM document "MVS Auth Assembler Services Guide" - Section “Interpreting Error Reason Codes from DYNALLOC". Appendixes LIII Msg Num 28012 Message Text Explanation EZX JOB using volume <JOB> from <DOMAIN> with DSN <DSN> is rejected: <REASON>. MVS EZX agent rejects the job for one of the following reasons: Action Retry later. Attemp to access dataset(s) being locked by other job Attemp to create dataset(s) being locked by other job. 28013 The current operation of EZX JOB <JOB> from <DOMAIN> will unlock <DSN> An operation (lock, create or query dataset) is requested on a dataset that is already locked by the same job in the MVS EZX agent. The dataset is unlocked before the new operation is executed. Last Revised: Mar. 10, 16 Version 1.58 None.

EZX Manual - ETI-NET

Related documents

Products

Support

EZX Manual - ETI-NET

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib