ETU400 User Guide AS/400 File Transfer Utility i
SOFTWARE LICENSE AGREEMENT NOTICE ======= YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE OPENING THIS PACKAGE. OPENING THIS PACKAGE INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE WITH THEM, YOU SHOULD PROMPTLY RETURN THE PACKAGE UNOPENED, AND YOUR MONEY WILL BE RETURNED. NLynx provides the computer software program contained on the medium in the package (The "Software") and licenses its use.
PROHIBITED USES ================ You may not: * Make the Software available to any person or entity other than Your employees, who must use the Software as specified above. You may, however, after written notification to NLynx, transfer all (but not a lesser portion) of the Software and related manuals to another person or entity, who in turn will be subject to this Agreement. * Modify the Software or merge it with another program. Any modified or merged portion of the Software is subject to this Agreement.
LIMITED WARRANTY ================= NLynx warrants that, upon delivery by NLynx, the diskettes or other media on which the Software is distributed will be free from defects in materials for a period of 90 days. The Software itself IS LICENSED TO YOU ON AN "AS IS" BASIS. If the diskette or other media fails to comply with the warranty set forth above, NLynx will replace the diskette or other media.
Legal Notices This document is for use with the NLynx Technologies ETU/400 product. No part of this document may be copied in any form or by any means without prior written consent of NLynx Technologies. All software, firmware and downloadable operating code described herein or used by the products described herein are copyrighted by and shall remain the property of NLynx Technologies. All drawings, schematics and artwork used in the manufacture of products described herein are copyrighted.
PREFACE This manual is intended for users of the ETU 400 Emulator Transfer Utility. It assumes the reader has a basic working knowledge of the IBM AS/400, the IBM Personal Computer or Personal System/2, and the operation of software for emulation of the IBM 5251 Model 11 or Model 12 workstations on the IBM Personal Computer.
About This Guide Use this guide to install and run ETU 400 on the IBM AS/400 host computer. Who Should Use This Guide? All users of ETU, from the beginning user of the AS/400 to the most advanced user, should refer to this guide. ETU interfaces directly with the 5251 emulation software running on your microcomputer, whether it's an IBM PC, an Apple Mac or a UNIX workstation. This guide assumes that you have a working knowledge of your microcomputer and the emulation software that resides on it.
Legal Notices © 2000 NLynx Technologies, Inc. All rights reserved. v v PREFACE v Trademark Recognition. vi About This Guide Who Should Use This Guide? How This Guide is Organized vii vii vii INTRODUCTION 1-1 Welcome to ETU What ETU Can Do for You Inventory Checklist Security Considerations 1-2 1-2 1-3 1-3 Hardware and Software Requirements Hardware Requirements Software Requirements 1-4 1-4 1-4 Features of Version 5.02 1-5 Features of Version 5.041 1-6 Features of Version 5.
USING ETU 3-1 About This Chapter 3-2 Starting ETU A Note About User Authorization 3-3 3-3 The ETU Main Menu The ETU Utilities Menu 3-4 3-5 The ETU Commands Main Menu: File Transfer Commands Main Menu: ETU Power Commands Utilities Menu: Microcomputer Commands Utilities Menu: File Translation Commands Utilities Menu: Translation Table Commands 3-6 3-6 6 6 6 6 Running ETU Commands Using the Menu Entering Commands on the Command Line Using the Command Prompts Using Mac Directory Dialog Boxes Request D
5-1 6-1 7-1 8-1 9-1 Transferring Files Translating Files Working with PC Functions Modifying Translation Tables Advanced ETU Features TRANSFERRING FILES 3 3 3 3 3 5-1 About This Chapter 5-2 Transferring Data Files Transferring Data Files From Host to a Microcomputer: FROM3XB Example Transferring Data Files From a Microcomputer to the Host: The TO3XB Command TO3XB Example 5-3 5-3 5-3 5-5 5-5 5-6 Transferring Print Files Transferring a Host Spool File to a PC Print File: About Host Spool Files Transf
RENAMEB Example Figure 7-1 The RENAMEB prompt screen Allocate a Micro File: The ALOCATB Command ALOCATB Example Delete an Existing File: The DELETEB Command DELETEB Example Test for the Existence of a Micro File: The TESTB Command TESTB Example MODIFYING TRANSLATION TABLES 7-3 7-3 7-4 7-4 7-4 7-5 7-5 7-6 7-7 7-7 7-7 8-1 About This Chapter 8-2 About Translation Tables 8-3 Modifying a Translation Table Make a Copy of the Original Table Editing the Translation Table Translation Table Record Format Samp
Saving Request Definitions Re-using Request Definitions 9-20 9-20 Performing Batch Transfers Batch Transfer – Example 9-22 9-23 Time and Date Scheduling Time and Date Scheduling – Example 9-24 9-25 ETU COMMAND REFERENCE 10-1 ALOCATB Command 10-2 DELETEB Command 10-3 EDITTABLE Command 10-4 EDTUDF Command EDTUDF Notes 10-6 10-7 FROM3XB Command FROM3XB Notes 10-8 10-11 PCFROMPC Command 10-12 PCTOPC Command 10-14 PGMFROM3XB Command 10-16 PGMTO3XB Command 10-17 PRTFROM3X Command 10-18
TESTB Command 10-47 TO3XB Command 10-48 VWSAVRQS Command VWSAVRQS Notes 10-52 10-52 XLATEFROM Command 10-54 XLATETO Command A-1 Inside ETU B-1 ETU Compatibility C-1 Creating DDS Specifications D-1 Creating F & I Specifications E-1 ETU Error Messages F-1 EBCDIC/ASCII Printable Characters G-1 System/36-mode Commands H-1 International Translational Tables GLOSSARY INDEX Appendix A 10-57 10-61 10-61 10-61 10-61 10-61 10-61 10-61 10-61 10-61 10-61 A-1 INSIDE ETU A-1 About This Chapter A-2 Editing U
Creating DDS Specifications C-3 APPENDIX D D-1 CREATING F&I SPECIFICATIONS D-1 About This Appendix D-2 Creating F & I Specifications Appendix E D-3 E-1 ERROR MESSAGES: NATIVE MODE E-1 About This Appendix E-2 USR MESSAGES: E-3 TRANSFER PROBLEMS: E-4 USER MESSAGES: E-5 CPF MESSAGES: E-15 SYS MESSAGES: E-19 OCL PROBLEMS Appendix F E-21 F-1 ASCII-EBCDIC PRINTABLE CHARACTERS F-1 About This Appendix F-2 This appendix lists the ASCII and EBCDIC characters and their hexadecimal equivalen
FILEFRPC Procedure G-10 FILETOPC Procedure G-13 LIBRFRPC Procedure G-15 LIBRTOPC Procedure G-18 PRNTFRPC Procedure G-21 PRNTTOPC Procedure G-23 RENAME Function G-25 TESTFILE Procedure G-26 XLT36FIL Procedure G-27 XLT36PRT Procedure G-29 XLTPCFIL Procedure G-31 XLTPCPRT Procedure Appendix H G-33 H-1 INTERNATIONAL TRANSLATION TABLES H-1 Installing International Translation Table Appendix I H-2 I-1 ETU AUTOMATION I-1 ETU400 Automation AUTOMATION MECHANISMS SBMBATXFER SBMSCHJOB I-
Part One Getting Started “Getting Started” is intended for all users of ETU. It describes how to install and how to use ETU. If you are new to ETU, you will be introduced to concepts and terms that will help you master it.
Chapter 1 INTRODUCTION Welcome to ETU What ETU Can Do For You Inventory Checklist Security Considerations Hardware and Software Requirements Hardware Requirements Software Requirements Features of Versions Notes to Mac Users Compatibility with Non-NLynx ES32 products Native Mode and System/36 Mode 1-1
Welcome to ETU ETU is a host software package that allows you to transfer files between an IBM AS/400 host computer and one or more microcomputers that are emulating an IBM 5250 display station. What ETU Can Do for You The purpose of ETU is twofold: to transfer data and to translate data. Data transfer entails the movement of data between two systems. Data translation changes the way the data is represented or stored so that the same data can be used by two different systems.
Inventory Checklist In addition to this manual, the following items are included in your ETU package: 9 One of the following sets of storage media containing the ETU software: six 5.25-inch diskettes' one reel-to-reel tape, one tape cartridge, or one CDROM. If this item is missing, contact NLynx Customer Service at 888-NLynx67 from 8:30 to 5:30 Central Standard Time.
Hardware and Software Requirements The host and microcomputer hardware and software required by ETU are described below. Hardware Requirements In order to run ETU, you must have the following hardware components: • IBM AS/400 and one of the following: • • IBM PC, IBM PS/2, or compatible; Apple Mac System 8.0 to OSX. Software Requirements The AS/400 requires: • • Operating System/400, Version 1 Release 3, or higher; Source Entry Utility (SEU).
Features of Version 5.02 This version of ETU has several new features that didn't exist in Version 5.01 (or earlier), including: • • • • • The maximum column width is supported. ETU 400 supports print translations to the maximum column width allowable in OS/400. In the current version of ETU 400, the prompt for column width is 999 characters. However, the latest version of OS/400 allows a column width of only 378. A new translation table is included.
Features of Version 5.041 ETU 400 RISC Version 5.041 represents an incremental maintenance release. We have modified the installation procedure for this version so that an IBM PTF does not need to be installed on the host prior to the installation of ETU 400 RISC. Details With V3R7 of OS/400, the previous release of ETU 400 RISC (5.04) required IBM PTF SP36296 to be installed on the AS/400 prior to the installation of the ETU RISC CD-ROM.
Features of Version 5.5 Version 5.5 and the changes to it are as follows: This version has been created to remove the need for registration with ETU (the Y2K changes are now redundant). 1. Changed save command to use V3R6 rather than *PRV, so that once built ETU can be used on any version of RISC OS400. 2. Changed all RPG programs to ignore decimal data errors, to solve problems that were occurring with spreadsheet data. 3.
Features of Version 5.6 Version 5.6 is the latest release. This release supports changes in Operating System V5R1. The issue was a problem transferring AS/400 spool files to the PC. When you select the Output queue, you could not see any of the files that were in that queue. It is downward compatible with older versions of OS/400. Notes to Mac Users Most of the information in this manual is relevant to all microcomputer workstation users. However, some information is specific only to Mac users.
Part One, Getting Started “Getting Started” is intended for all users of ETU.
Chapter 2 INSTALLING ETU About This Chapter Installing ETU Installing the ETU Software Registering Your Host System Obtaining Your Host Registration Number Completing the Host Registration Procedure Re-installing ETU Removing ETU From Your Host System Installing ETU For International Users The ETU Compatibility Diskette: For DOS-only Non-ES32 Emulation Products Who Should and Can Use IBMTRAN Copying IBMTRAN To Your Hard Drive Starting ETU When Using IBMTRAN Exiting IBMTRAN Alternative Method to Start and E
About This Chapter This chapter is intended for the system administrator, or other experienced host user responsible for installing the ETU software on the AS/400. This chapter explains: • how to install the ETU software; • how to register ETU with NLynx Technologies; • how to determine if you need the IBM Compatibility Diskette in order to run ETU.
Installing ETU To • • • install ETU on the AS/400, you will follow these basic steps: load the ETU software; register your copy of ETU with NLynx Technologies complete the registration procedure on the AS/400. NOTE: Before installing ETU, you must sign on to the AS/400 as the security officer (QSECOFR). NOTE: If you install ETU to an existing library that contains the files QS36SRC or QS36PRC, the installation procedure will overwrite these files and any existing data will be lost.
1. Sign on to the AS/400 as QSECOFR. 2. Ensure that library QTEMP is in your library list. 3. Insert ETU software in the AS/400: If you are installing from diskettes, insert the first diskette into the drive on the AS/400. If you are installing from tape, load the tape into the tape drive. • • • 4. If you are installing from CDROM, insert the CDROM into the CDROM drive.
old versions, since most users do not modify these tables ETU400 User Guide 011603 2-5
If you have translation information required to Guide. a version of ETU prior to 5.01 and have modified or created tables, you must modify the tables further for ETU 5.01. The below assumes you are familiar with the terminology and steps modify the translation tables, as defined in the ETU 400 User The host-to-micro source members for the PC (ETOA1) or the Mac (ETOA1M), or any user-defined table that was created using these members, must be modified as described below.
Obtaining Your Host Registration Number 1. Have the following information ready before you request your host registration number. 9 9 9 9 9 9 The ETU serial number located on your ETU software media. (For most software media, the serial number is six digits beginning with 2. For 8mm tape, the serial number is eight digits beginning with 5.) Your host serial number.
If you are updating an existing version of ETU, sign on as the system security officer (QSECOFR), back up your ETU library using the SAVLIB command, and then re-install ETU following the instructions in Installing the ETU Software on page 2-3. Removing ETU From Your Host System ETU includes a utility that allows for easy removal of the ETU programs from your host system. See Appendix A for details on removing ETU.
The ETU Compatibility Diskette: For Non-ES32 Emulation Products When ETU was originally sold, there was a compatibility disk that shipped with the product to allow DOS products to run with it. Very few PC run in DOS mode anymore, so that is no longer included with this product, however it is available on our website at http://www.nlynx.com/html/tbetu36.htm. To use this program, called IBMTRAN, you would install it on the IBM PC from which you run ETU.
"5250 Emulation not loaded, verify that your API is loaded." If your API is loaded and this message persists, contact your emulation manufacturer to be sure you have the latest version. The documentation included with your emulation software should provide you with details about API. NOTE: If you configure your emulator and API the way you would to run PC Support/36, then IBMTRAN should work.
Chapter 3 USING ETU About This Chapter Starting ETU A Note About Authorization The ETU Main Menu The ETU Utilities Menu The ETU Commands Main Menu: File Transfer Commands Main Menu: ETU Power Commands Utilities Menu: Microcomputer Commands Utilities Menu: File Translation Commands Utilities Menu: Translation Table Commands Running ETU Commands Using the Menu Entering Commands on the Command Line Using the Command Prompts Using the Mac Directory Dialogue Boxes Recalling ETU Commands Request Definitions Type
About This Chapter This chapter is intended for beginning users of ETU. It covers the basics of running ETU in native mode on the AS/400. In this chapter, you will learn: • • • • how to start ETU; how to use the ETU menu; how to enter ETU commands; about using ETU with PC or Apple Mac files. Once you have read this chapter, continue with Chapter 4, Learning About ETU.
Starting ETU You can begin using ETU once it is installed on your host system. To start ETU: 1. Load your 5250 emulation software on your microcomputer. If necessary, load the ETU compatibility program, IBMTRAN, on your PC. See Chapter 2, Installing ETU, for information about IBMTRAN. 2. Enter your AS/400 user I.D. and password at the sign-on screen. 3.
The ETU Main Menu The ETU commands are split between two menus, the Main menu and the Utilities menu. The Main menu, shown in Figure 3-1, displays when you issue the command WSMENUS. It contains an option for each file transfer command. In addition, it also contains an option that displays the ETU Utilities menu, and an option that signs you off the AS/400.
The ETU Utilities Menu The ETU utilities menu provides access to the ETU commands that aren't used for transferring files. There are three groups of commands on the Utilities menu. They are the PC functions commands, the translation commands, and the translation table commands. These commands are described later in this chapter. To display the ETU Utilities menu, select option 20 from the ETU Main menu. Figure 3-2 The ETU Utilities Menu Menu - WSMENUS NLRISCLIFF 1. 2. 3. 4. 8. 9. 10. 11.
The ETU Commands There are 20 ETU commands that work with files. These commands can be divided into five groups, each providing a different function. The ETU commands are grouped below according to the menu on which they appear, and their functions. Main Menu: File Transfer Commands These commands transfer files between a microcomputer and the host. They are discussed in Chapter 5, Transferring Files. Option 1. Option 2. Option 3. FROM3XB PGMFROM3XB PRTFROM3X Option 4. Option 5. Option 6.
Running ETU Commands With ETU, there are two ways to run commands: using the ETU menu, or entering ETU commands on the command line. Both methods produce the same result; that is, a prompt screen displays on which you provide information like the name of the file you want to transfer, and where you want to transfer the file. ETU menus have an option field or a command line, but not both, depending on your authority.
Using the Command Prompts After you select the ETU command that you want to run, either by choosing an option from the menu or by entering the name of the command on the command line and pressing F4, a prompt screen displays. This screen lists the parameters associated with the command. A parameter is a placeholder for a single piece of information, or value, that you must provide to ETU to tell ETU what to do and how to do it.
Recalling ETU Commands If you run the same ETU command more than once, you can avoid re-keying repeated values by using the recall function. The recall function displays the most recently run command on the ETU command line. To recall a command, press F9. You can then change whatever information you want by typing over it. You can cycle through and recall any command you entered since you accessed the ETU menu (WSMENUS) by repeatedly pressing F9.
Types of Processing Any work that is processed by the AS/400 is called a job. Two important types of jobs are interactive jobs and batch jobs. All ETU commands can be run interactively. Some can be run in batch mode, as well. Interactive ETU Commands Interactive jobs begin processing the moment you execute them, usually when you press the ENTER key. The microcomputer from which you execute the job is input inhibited or tied up until the interactive job is completed.
About Microcomputer Files ETU works with several types of microcomputers, including IBM PCs (and compatibles) and Apple Maces. Throughout this guide, these computers are referred to as micros. When you perform an ETU command that works with a PC or Mac file, you will be asked to provide the micro file name. The micro file names can contain up to 80 characters, including the file path.
Chapter 4 LEARNING ABOUT ETU About This Chapter What is ETU? Data Transfer Data Translation Other ETU Functions About Transferring Files Micro and Host File Names Transferring Data to Host Files Record Length Host File Type Data Description Specifications About Translating Files How Data is Stored Using Translation Tables ETU Translation Table Members Using Translation Tables With the Mac Using Microcomputer Data Formats ETU400 User Guide 011603 4-1
About This Chapter This chapter is a general overview of ETU and is intended for beginning users. It explains how data is stored on the host and the microcomputer, and how ETU makes it possible to transfer data between the two systems. The information you provide when you transfer and translate files using ETU is also explained in this chapter.
What is ETU? ETU has two main purposes: data transfer and data translation. Data transfer entails the actual movement of data between the host and a microcomputer. Data translation changes the way the data is represented or stored so that the same data can be used by the two different systems. ETU provides you with file transfer commands and file translation commands. Data Transfer With the file transfer commands, you can transfer and translate the file, or you can specify that translations not occur.
About Transferring Files ETU allows you to transfer files and programs between a host system and any microcomputer connected by emulation software to the host. To transfer a file from one system to another, you must provide certain information such as the name of the file you are transferring, the type of file it is, and the name of file to which you are transferring it. For example, if you are transferring a file from a PC to the host, you must provide the name of the PC file and the name of the host file.
Transferring Data to Host Files When you transfer data to the host, you can transfer it to an existing file, or to a new file, which ETU creates. To transfer data to an existing file, supply the name of the existing file, the library it resides in, and the member name. The data within the file is defined using the existing file's definition. To transfer data to a new file, supply the new file's name, the library in which it will reside, the member name, and the file type.
Data Description Specifications When you create a physical file (*DATA) on the AS/400, you can define the file using Data Description Specifications (DDS). The DDS file definition tells the computer many things about the file, including where one field begins and ends, and whether a field is numeric or alphabetic. It's not necessary for each physical file to have a unique set of DDS specifications.
About Translating Files You must usually translate data when you transfer it between a microcomputer and the host. That's because the host and the microcomputer have very different data storage methods. The remainder of this chapter explains the differences between host and micro data, and the two types of translations ETU performs to overcome those differences. How Data is Stored The way data is stored on the AS/400 is considerably different from the way it is stored on the micro.
Using Translation Tables ASCII and EBCDIC are standard character sets. When you transfer a file between a microcomputer and the host, the file must be translated from one character set to the other. (Unless, that is, you are only storing the file and not planning to manipulate or use the file in any way on the other system. In that case, you can transfer files without any translation taking place by specifying *NONE as the value for the TRANSLATE parameter.
ETU Translation Table Members The ETU translation tables member names and their specific functions in the TRANSLATE file are listed below. ETOA1 The EBCDIC-to-ASCII PC-DOS character translation member that produces a variable-length record, with carriage return and line feed added after the last byte of data in each record. Trailing blanks are stripped. ETOA2 The EBCDIC-to-ASCII PC-DOS character translation member that produces a basic random file on the PC, with no carriage return line feed.
Using Translation Tables with the Mac All ETU commands in which data translation occurs include the TRANSILE parameter. The default value for this parameter is TRANSLATE, which exists for translating PC data – not Mac data. If you use a Mac you must change the default value to MACTAB. (If you create a different translation table, then you can specify the new table.) As an example, the screen in Figure 4-1 displays when you select WSMENUS option #1, FROM3XB.
Table 4-2 ETU Commands in which the translation table file name is optional ETU Command ETU Main Menu Option FROM3XB 1 PRTTOPC 3 TO3XB 4 PRTFRMPC 6 PWRFROM3XB 7 PWRTO3XB 8 ETU400 User Guide 011603 4-11
Using Microcomputer Data Formats In addition to translating files from ASCII to EBCDIC, ETU formats the data so that it can be used in the various types of microcomputer applications such as spreadsheets, word processors, and database programs. Each type of application stores data in its own format. ETU provides four translation types that enable the host data to be formatted for the type of application in which you will use it.
Tab format (*TAB) TAB format is the same as BASIC Sequential, except that tab characters, rather than commas, separate the fields. Data in a *TAB format looks similar to that shown below: Table 4-4 Example of a *TAB data file 9.00 “LOlll” ”10119” “BLACK” ”DOG”9.00 ”890101” 9.00 “LO118” “10119” “RED” ”DOG” 8.00 “890301” 9.00 “LO118” “10221” “BLACK” “BIRD” 6.00 “890401” 9.00 “LO118” “lO222” ”BLUE” ”CAT” 6.00 “890201” 8.00 “LO118” “10222” ”BLACK” ”HORSE” 7.0 “890202” 8.00 “LO118” “10224” “GREEN” “FISH” 7.
Part Two Running ETU “Running ETU” is intended for all users of ETU. It introduces each ETU command and describes how to use the commands. An example of how to use each command is also provided.
Chapter 5 TRANSFERRING FILES About This Chapter Transferring Data Files Transferring Data Files From Host to a Microcomputer: The FROM3XB Command FROM3XB Example Transferring Data Files Microcomputer to a Host: The TO3XB Command TO3XB Example Transferring Print Files Transferring a Host Spool File to a PC Print File: The PRTFROM3X Command PRTFROM3X Example Transferring a PC Print File to a Host: The PRTTO3X Command PRTTO3X Example Transferring Host Programs Transferring a Host Programs to a Microcomputer:
About This Chapter This chapter is intended for beginning users of ETU. It explains the file basic transfer commands included with ETU. You will learn the purpose of each command, as well as how to use them. There are three primary host objects you can transfer with ETU. They are host files (physical files, logical files, and *SAVF files), spool files, and executable programs. There are three primary micro-based objects you can transfer with ETU. They are data files, print files, and executable programs.
Transferring Data Files The ETU commands FROM3XB and TO3XB transfer data files between the host and a microcomputer. Transferring Data Files From Host to a Microcomputer: The FROM3XB Command With the FROM3XB command, you can transfer and translate data from an AS/400 physical, logical, or *SAVF file to a file on the micro.
3. Enter the member name at the Member name prompt: user1 4. Specify *NONE as the parameter at the Translation table file prompt because you have already translated the file with the XLATETO command. 5. Enter the Mac folder and file name at the Qualified file name prompt: store1:sales 6. Because you did not specify a data translation, you can disregard the remaining parameters. Once you have entered the appropriate information, press ENTER to start the command.
Transferring Data Files From a Microcomputer to the Host: The TO3XB Command With the TO3XB command, you can transfer and translate data from a microcomputer to a file on the host. The TO3XB command also allows you to store data on the host in ASCII. This serves as an alternative means of off-site storage for your microcomputer data. To store the microcomputer data on the host in ASCII, specify *SAVE as the value for the FILETYPE parameter.
TO3XB Example In this example, you will transfer a file on your PC to a new host physical file. The file on the PC is called c:\sales\january\week1.sal. The host physical file is called JANSAL1 in a member called REG1. To define the host file, use the existing host file definition (DDS) contained in member SALE in the source physical file QDDSSRC. Use the translation type *BASICS. 1. Choose option 4 from the ETU Main menu. The TO3XB screen displays. 2.
Transferring Print Files The ETU commands PRTFROM3X and PRTTO3X allow you to transfer print files between the host and the microcomputer. Once the file is transferred to the target system, you can print it on the target system's printer. Mac users: The commands PRTFROM3X and PRTTO3X work only with PC-DOS and should not be used with the Mac. Transferring a Host Spool File to a PC Print File: The PRTFROM3X command allows you to transfer a host spool file to a PC so it can be printed on the PC's printer.
PRTFROM3X Example In this example, there is a host spool file on the host output queue USER1. You will transfer the file to the PC so you can print it on the PC printer. Translate the file to a PC using translation table member ETOA1 in the TRANSLATE file. 1. Choose option 3 from the ETU Main menu. The PRTFROM3X screen displays (Figure 5-3). 2. Enter the output queue name at the Output queue prompt: user1 Use *LIBL for the Output queue library name. 3.
4. Choose the spool file you want to transfer. Press the TAB key until the cursor is next to the spool file you want to transfer. In the left-most column, type a 2(Copyprt and transfer) next to the print item. Figure 5-4 The PRTFROM3X Print Queue Screen 1/03/03 14:15:31 Select "COPYPRT" File Output queue: PRT01 Library: *LIBL Type options, press Enter.
Transferring a PC Print File to the Host: The PRTTO3X command allows you to transfer PC-DOS print files to the host and add them to a host output queue. For this command, supply the PC file name, the host output queue name, and optionally, host printer information such as lines per inch, characters per inch, and number of copies. Once you have supplied the information, ETU will transfer the file to the host and add the file to the AS/400 output queue that you specify.
PRTTO3X Example In this example, you will transfer a PC print file to the host and print it on the host printer. The PC file is called a:\report.prt. The host output queue to which you will send the file is called USER1. Use the defaults for all other parameters. 1. Choose option 6 from the ETU Main menu. The PRTTO3X screen displays. 2. Enter the name of the PC file at the Qualified file name prompt: a:\report.prt 3. Enter the output queue name at the Output queue prompt: user1 4.
Transferring Host Programs The ETU commands PGMFROM3XB and PGMTO3XB allow you to transfer compiled executable host programs between a microcomputer and the host. You can use these commands to transfer host programs to a micro so you can either run the host program on the micro, if you have appropriate PC software, or transfer the program to another host system. In the latter case, the PC serves as a link between two host systems.
If you are using this command to transfer a program between two different AS/400s having differing versions of OS/400, youi must provide the Target Release Level (TGRLS) from the SAVOBJ command. To access the target release, press F10 when prompting the PGMFROM3XB command. PGMFROM3XB Example Suppose you have a program on the AS/400 that you want to transfer to the micro. The host program is called BETA1 and is in the USER library. You will transfer it to a PC file called a:\ beta1.pgm. 1.
Transfer Host Programs to the Host: The PGMTO3XB command transfers executable host programs from a file on the micro to the host. This command transfers only those executable host programs from the micro that were originally transferred to the micro with the PGMFROM3XB command. To transfer a host program from a microcomputer, supply the name of the microcomputer file that contains the program, and the name of the host program and library to receive the file.
PGMTO3XB Example In this example, you will transfer a program from one host system to another host system. To do this, you would normally first transfer the host program to a PC using the ETU command PGMFROM3XB. Assume, for this example, that this step has already been done. You will now transfer the program to a second host system using the PGMTO3XB command. To do this, copy the PC file containing the host program to a floppy diskette.
Chapter 6 TRANSLATING FILES About This Chapter Why Use the Translation Commands Translation Commands Can Run in Batch Mode Translation Commands Can Be Run From a Host Terminal Translation Commands Reduce Connection Time Translating Data Files Translating a Microcomputer File to a Host Format: The XLATEFROM Command XLATEFROM Example Translating a Host File to Microcomputer Format: The XLATETO Command XLATETO Example Translating Print Files Translating PC Print Files: The PRTXFRMPC Command PRTXFRMPC Example
About This Chapter This chapter explains the ETU translation commands. These commands are used in conjunction with the ETU transfer commands. If, when you transfer a file, you specify no translation, you will translate it using one of the commands described in this chapter. There are four ETU translation command: • XLATEFROM--Translates a microcomputer ASCII file to a host physical file format.
Why Use the Translation Commands In Chapter 5, you learned about the ETU transfer commands. Those commands have two purposes. First, they transfer files between the micro and the host. Second, they translate the data so that both systems, the host and the micro, can use it. This chapter discusses ETU translation commands. These commands have only one purpose--and that is also one of the purposes of the transfer commands--to translate the data so that both systems can use it.
Translating Data Files The translation commands XLATEFROM and XLATETO translate files separately from the transfer commands TO3XB and FROM3XB. These commands can be initiated from the microcomputer that contains or will contain the file, or from any host terminal. They can be run interactively or in batch mode. To run them interactively, leave the JOBD parameter blank.
XLATEFROM Example Suppose you transferred a PC file to the host using the TO3XB command. You didn't translate the file during the transfer operation, but you do want to translate it now using the XLATEFROM command. The name of the host file containing the untranslated data is RS132 in the NEWLIB library. After the file is translated, it will be written to an existing host file called HOME1, in the member of the same name.
4. At the Host output data file prompt, enter the name of the file to which data will be written once it is translated: home1 5. Use the defaults for the parameters PC member and Host output file. 6. At the Type of translate prompt, enter the translation type: *tab 7. Enter the name of the translation table for ASCII-to-EBCDIC translations: atoe1 Use the defaults for all the other parameters. 8. Once you have entered the appropriate information, press ENTER to start the command.
Translating a Host File to Microcomputer Format: The XLATETO command translates a AS/400 physical file to a format usable on the microcomputer. You will use this command prior to transferring the file to the PC with the FROM3XB command. After you translate the data, you must enter the following FROM3XB parameters as shown: strip(*no) translate(*no) When the file is translated, it is written to a different host file, which you specify in the PCDATA parameter.
XLATETO Example Suppose there is a file on the AS/400 that you want to transfer to your Mac. Before you transfer the file, you will translate it using the XLATETO command. For this example, the file on the host is called LOT14. It contains one member, also called LOT14. After the data is translated, it will be written to a newly created host file called DATA3. The data will ultimately be transferred to a variable-length record on the Mac. Use the file definition of the FRMFILE parameter for the PCDATA file.
Translating Print Files The translation commands PRTXFRMPC and PRTXTOPC translate print files. The command PRTXFROMPC translates a micro print file that was previously transferred to the host with no translation using the TO3XB command. The PRTXTOPC translates a host spool file prior to transferring the file to the micro with the FROM3XB command. Both translation commands can be run in batch mode on the host.
Suppose you previously transferred a PC print file to a host file using the TO3XB command. Now you want to print the file on the host printer. Before you can print the file, you must translate it using the PRTXFRMPC command. For this example, the PC file residing on the host is called PRINT1. When the translation is complete, you want the file sent to the USERX output queue. Use the defaults for all other parameters associated with this command. 1. Choose option 20 from the ETU Main menu.
Translating Host Spool Files: The PRTXTOPC Command The PRTXTOPC command translates host spool files that reside on an AS/400 print queue, prior to transferring them to a PC. After the file is translated, use the FROM3XB command (with no translation) to transfer the print file to the PC. Before you transfer the file to the PC, you must change the file from a spool file to a physical file. To do this, use the AS/400 command CPYSPLF.
PRTXTOPC Example Suppose you have a host spool file on the host that you want to print on the PC. Before you transfer the file to the PC, you will translate it on the host to keep the transfer time to a minimum. After the spool file has been translated on the host, you will transfer it to the PC using the FROM3XB command. The host spool file is called LETTER2. You will run the CPYSPLF command within the context of the PRTXTOPC command. 1. Choose option 20 from the ETU Main menu.
Chapter 7 WORKING WITH PC FUNCTIONS About This Chapter Rename a Micro File: The RENAMEB Command RENAMEB Example Allocate a Micro File: The ALOCATB Command ALOCATB Example Delete an Existing File The DELETEB Command DELETEB Example Test For the Existence of Micro File: The TESTB Command TESTB Example ETU400 User Guide 011603 7-1
About This Chapter This chapter explains the ETU commands that allow you to perform PC functions, such as creating and deleting PC files, from emulation. These commands let you work with microcomputer files while you are running emulation. They eliminate the need for you to return to the PC or Mac environment to create or delete a file. Four commands are discussed in this chapter.
Rename a Micro File: The RENAMEB Command With the RENAMEB command, you can rename an existing micro file while you are in emulation mode. You supply the current name of the micro file and the new name. The new file uses the same path as the file it replaces. RENAMEB Example In this example, you are working in emulation on the AS/400 and you want to rename a PC file called c:\data.pgm to c:\data1.pgm. 1. Choose option 20 from the ETU Main menu. The ETU Utilities menu displays. 2.
Allocate a Micro File: The ALOCATB Command The ALOCATB command creates a new file on the microcomputer. ALOCATB Example In this example, you are in emulation and want to create a file on the PC's c: drive called sales.feb in the reports directory (c:\reports\sales.feb). 1. Choose option 20 from the ETU Main menu. The ETU Utilities menu displays. 2. Choose option 1 from the ETU Utilities menu. The ALOCATB prompt screen displays. 3.
Delete an Existing File: The DELETEB Command Just as you may need to allocate (create) files on a microcomputer while in emulation, you may also need to delete files. The DELETEB command deletes any micro file. ETU will send you a completion message if it doesn't find the file you want to delete. Enter *NO at the NOTIFY prompt if you don't want ETU to notify you. NOTE: When you use the DELETEB command, all data in the designated micro file will be permanently deleted.
DELETEB Example In this example, you are running emulation and you want to delete a file on the PC's a: drive called fiscal.doc in the ‘reports’ subdirectory (a:\reports\fiscal.doc). 1. Choose option 20 from the ETU Main menu. The ETU Utilities menu displays. 2. Choose option 3 from the ETU Utilities menu. The DELETEB prompt screen displays. 3. At the Qualified file name prompt, enter the name of the micro file you want to delete: a:\report\fiscal.doc 4.
Test for the Existence of a Micro File: The TESTB Command With the TESTB command, you can check to see if a file exists on the micro while you are in emulation. The host you sends a completion message about the existence of the file. TESTB Example In this example, you are running emulation on your micro and you want to check to see if a certain file exists on the micro. The micro file is called c:\datafile.doc. 1. Choose option 20 from the ETU Main menu. The ETU Utilities menu displays. 2.
Chapter 8 MODIFYING TRANSLATION TABLES About This Chapter About Translation Tables Modifying a Translation Table Make a Copy of the Original Table Editing the Translation Table Translation Table Record Format Sample Translation Table.
About This Chapter ETU provides you with eight translation tables which it uses to translate data. Each table performs a separate function. Some translate data from the micro to the host and others from the host to the micro.(See Chapter 4, Learning About ETU, for more information about the translation tables.) The tables provided with ETU will serve the needs of most users. If the translation tables supplied with ETU do not fit your needs, you can modify an existing table.
About Translation Tables The translation tables provided with ETU have three purposes. They: • translate data from ASCII to EBCDIC or from EBCDIC to ASCII; • specify whether the file being translated has a fixed or variable format; • tell the host whether the micro involved in the translation is a DOSbased PC or a Mac. Each translation table is stored as a member in a physical file. The DOSbased tables are in a physical file called TRANSLATE in the host library containing the ETU programs.
Modifying a Translation Table If you decide that the standard translation tables included with ETU won't work for you, you can create a new one. To create a new table, modify the source member closest in function to one of the existing members. For example, if you want to create a table that translates data from a PC to the host, modify the source member ATOE1. The source members for the translation tables are in the source physical file TRANSSRC. Changing a translation table is a three-part process.
Make a Copy of the Original Table Before you modify a translation table member, it is recommended that you copy the original member, which resides in the supplied TRANSSRC file, into another member. This leaves the original members inviolate in case you still need to use them. To copy a member, use the AS/400 command STRSEU (option 20 on the ETU Utilities menu). Using SEU, copy the member you will modify into another member.
Table 8-2 Translate Table Source Record Format Position in the Record Functions (Record Fields) 1-18 19-36 37 38-39 FROM HEX (or special function) TO HEX Translate before or after performing control Pad character (B=blank, N=Null, or 2-byte hex character) End-of-record (EOR) action for ASCII-to-EBCDIC translation End-of-file (EOF) action for ASCII-to-EBCDIC translation Comment Not used 40-41 42-43 44-80 81-96 The fields in the record are described in detail below: From one to nine characters expressed
For example, the table above indicates that a translation table can contain a maximum of 20 “From” entries with a string length of 6 bytes. The xxx markers indicate that the length is not supported for that type of translation. Normally, all translation types will use only the single character translation. TO HEX From zero to nine characters (depending again on the type of file translation) expressed in hexadecimal.
End-of-File Action This is identical to end-of-record action with one exception. This function also completes translation and terminates the program. Comments Are printed in the translation table compiler listing. There are five special records for the translation table compiler. These records define what action is to be taken for end-of-record and end-offile for FROM3XB translation. On TO3XB translation, the special records determine if trailing blanks or nulls should be omitted.
Sample Translation Table The following is an example of an ASCII-to-EBCDIC translation table. For a complete listing, see member ATOE1 in the file TRANSSRC in the library containing ETU. It can be printed with the Source Entry Utility. Figure 8-4 FROM HEX 01 02 . . 30 31 32 33 34 . . 41 42 43 . .
Compiling the New Translation Member After you create or modify a new translation source file member using SEU, you must compile it into a physical file member before you can use it in the ETU translation program. The compiler • edits the translate table source; • prints a listing of the table (including any error messages); • writes the compiled table to a physical file member. To compile the new member, use the AS/400 command EDITTABLE (option 20 on the ETU Utilities menu).
Chapter 9 ADVANCED ETU FEATURES About This Chapter Multiple-device Transfer Transferring From Multiple Micros Using PWRTO3XB Transferring a Host File to Multiple Micros Micro-to-Micro Transfers The PCFROMPC Command The PCTOPC Command Transferring Files Between Multiple Macs Mac File Transfer Examples If InterAxcess is located at the root level of the hard drive If InterAxcess is one or more folders deep Record and File Selection About Creating Auxiliary Storage Pools Transferring Selected Fields Field Sele
About This Chapter Most ETU commands allow you to transfer a file interactively between the host and a micro. This chapter describes features that allow advanced users to go beyond the basic ETU operations. The features included in this chapter are part of the ETU power commands: PWRFROM3XB, PWRTO3XB, PCFROMPC, and PCTOPC. The commands PWRFROM3XB and PWRTO3XB provide the same functionality as their more basic ETU counterparts, FROM3XB and TO3XB.
Multiple-device Transfer Multiple-device file transfer is a feature supported by all ETU power commands. Using multiple-device transfer, you can: • Transfer a single host file to multiple micros (PWRFROM3XB); • Transfer a file from multiple micros to the host (PWRTO3XB); • Transfer a single • Transfer a file from multiple micros to a single micro (PCFROMPC). micro file to multiple micros (PCTOPC); (The command you use to perform the described operation is shown in parentheses.
signed on. Each device you transfer from must be powered on, have emulation loaded, and be at the AS/400 signon screen. NOTE: This parameter must be changed from *REQUESTER when you run the PWRTO3XB command in batch mode. When you transfer the files to the host, you can specify how you want the file stored: • In one physical file with multiple members; • In one physical file with one member (data is stored together); • In multiple physical files with one member each.
Using PWRTO3XB In order to send files from multiple micros to the same host library using PWRTO3XB with the TOFILE(*MULTI) option, you must rename any files sent in a first transfer before performing a second transfer. This procedure is necessary because when files are transferred from multiple micros to a single micro, the resulting file names on the destination micro are the device names from which the data was transferred.
Transferring a Host File to Multiple Micros The PWRFROM3XB command allows you to transfer a single host file to up to ten micros with one command. To transfer a file to multiple micros, specify the name of the host file to be transferred, the name of the micro file to which the data will be transferred, and the device names of the micros to which to transfer the data. The parameters used with PWRFROM3XB multiple-device transfers are described below.
Micro-to-micro Transfers In addition to allowing file transfers between a micro and a host, ETU allows you to transfer files directly from one micro to another micro. Use the ETU commands PCFROMPC and PCTOPC to transfer files between multiple micros. The PCFROMPC command allows you to transfer a file from multiple micros to a single micro. The PCTOPC command allows you to transfer a file from one micro to multiple micros.
The parameters used with PCFROMPC multiple-device transfer are described below: Qualified file name The name of the file to be transferred. If you are transferring a file from multiple micros, the file name, including the path name, must be identical on each micro. MICLST1 The device name of the source micro(s). To transfer a file from more than one micro, enter the device name of each. (You must be authorized to use each device you specify in the MICLIST1 parameter.
The PCTOPC Command To transfer a single file from one micro to multiple micros, specify the name of the file, the device name of the micro from which the file is being transferred, and the name of the device or devices to which the file is being transferred. QFNAME1 The name of the micro file to be transferred. If you are transferring a file to multiple micros, the file name, including the path name, must be identical on each micro. For additional information, see About Microcomputer Files in Chapter 3.
Transferring Files Between Multiple Maces If you are transferring files between your Mac and the host, or you are transferring files between Maces that share the same hard drive name, you may use the file transfer example on page 3-11. However, if you are transferring files between Maces that have unique hard drive names, you must use either of the examples below.
Figure 9-1 Transferring Files With InterAxcess on the Root Level of the Hard Drive If InterAxcess is one or more folders deep In this example, on each Mac, InterAxcess is located in a folder named AS/400, which is in turn located in a folder named Apps. The Apps folder resides at the root level of the hard drive (Figure 9-2). 1. From the ETU menu, issue the PCTOPC command. 2. Enter the parameters as you normally would, taking special care with the qualified pathname, as described in step 3. 3.
Figure 9-2 Transferring Files With InterAxcess Several Levels Deep Record and Field Selection Record selection and field selection are features that allow you to transfer only the records and fields you specify. This feature is part of the PWRFROM3XB command. Record selection and field selection are not mutually exclusive functions of ETU, although it's not necessary to use them together. NOTE: Record and field selection can be used only with externally-defined host physical files.
Field name The name of the field you want to transfer. may transfer up to 25 fields. You Key field Specifies whether the field is to be a key field. The default, *NONE, does not re-sort the records, but rather, leaves them in sequential order. The field does not have to be an existing key field in the file. The total of the key fields cannot exceed 120 characters in length. Ascending or descending Specifies whether the records are sorted in ascending or descending order (*ASC or *DES).
Field Selection -- Example 1 Suppose there is a file on your host computer that contains information about the employees in your company. Each record in the file contains a variety of information about one employee, such as the employee's name, address, phone number, rate of pay, and length of service. In this example, you will transfer only the names and phone numbers of each employee to a file on the PC. You also want the PC file to list the employees in alphabetical order, from A to Z.
Field Selection -- Example 2 In this example, you will see how you can use more than one key field when transferring selected fields. You will transfer the same file as in the first example. This time, you will transfer the employee names and their rates of pay. You will sort the information first in order of highest salary to lowest salary, and second, in alphabetical order when two or more employees earn the same salary. Table 9-2 below illustrates how the file will appear on the PC.
Transferring Selected Records ETU allows you to transfer selected records from a host file to a file on a micro. You select the records to be transferred by creating test cases. A test case is a set of criteria you specify within the PWRFROM3XB command. You can specify up to 15 test cases. If a record meets the criteria of a test case, it is transferred.
Record Selection -- Example1 Suppose you want to transfer the employee file (described in the previous section) from the host to the PC. You will transfer only the records of those employees earning more than $20,000 per year. To do this you will create a test case that transfers the records that meet the following criterion: the value in the PAYRAT field is greater than 20,000. 1. Enter the file transfer and translation information as you would for any file transfer. 2.
Entry and Exit Programs With the PWRFROM3XB and PWRTO3XB commands, you can run any user-defined programs before and/or after the file is transferred. Programs that run before the file transfer occurs are called entry programs. Programs that run after the file is transferred are called exit programs. To use the entry and exit programs, enter the name of the program and the library in which it resides in the ENTRYPGM and EXITPGM parameters.
Deleting Files After Transfer The commands PWRFROM3XB and PWRTO3XB allow users to delete files after the files have been transferred. Both commands contain a parameter called DLTFILE. If you enter *YES in the DLTFILE parameter in the PWRFROM3XB command, the host file you are transferring to the micro is deleted after the transfer occurs.
Saving Request Definitions Some ETU commands allow you to save the definition of the current request. The request definition is the completed, or filled-out, list of parameters for the command you are running. You can re-use the saved definition later to run the same command. The ETU commands that allow you to save request definitions are PCFROMPC, PCTOPC, PWRFROM3XB, PWRTO3XB, FROM3XB, and TO3XB. These commands all contain a parameter called SAVRQS.
1 Execute Interactively runs the command using the saved definition. 2 Submit to batch Prompts for the job description parameters and submits the request to batch. Batch commands cannot be longer than 256 characters. In order to run a job in batch mode, the device you specify must be powered on, running emulation, and displaying the AS/400 sign-on screen. NOTE: Only the ETU power commands can be submitted to batch; not the commands FROM3XB or TO3XB. 3 Change Allows you to change the saved request.
Performing Batch Transfers The ETU transfer commands featured in this chapter (PWRFROM3XB, PWRTO3XB, PCFROMPC, PCTOPC, ) can all be run in batch mode from either a microcomputer emulating a 5250 workstation or a dumb terminal. To submit one of these commands to batch, use the ETU command SBMBATXFER. Enter SBMBATXFER on the AS/400 command line, press F4, and provide the information described below.
After you supply the above information and press ENTER, you are prompted with the command name you specified in the SBMCMDNAM parameter. Fill out the parameters for the command as you would if you were running the job interactively. If you are submitting one of the ETU power commands to batch, you must change the default value, *REQUESTER, to the actual device address you will use.
Time and Date Scheduling The ETU Time and Date Scheduling utility allows you to submit a job to batch and specify a time in the future that the job will be released to the job queue. The utility can be used to schedule jobs when you know the host system is less busy than normal, such as on weekends or at night. All ETU power commands and any other AS/400 or user-defined command or program that can be run in batch mode can be scheduled using the Time and Date Scheduling feature.
Time and Date Scheduling – Example Suppose you want to transfer a file to a PC from the host using the PWRFROM3XB command. You want this command to run later the same night in batch mode. The job name is NIGHT and the job description is QBATCH. 1. On the command line, enter the ETU command that schedules the job. sbmschjob 2. Press F4. The Submit Scheduled Job prompt screen displays. 3. Prompt for the command you want to schedule: pwrfrom3xb 4.
Part Three Command Reference “Command Reference” is an alphabetical presentation of al AS/400 native mode ETU commands and the parameters and values associated with each command.
Chapter 10 ETU COMMAND REFERENCE ALOCATB Command DELETEB Command EDITTABLE Command EDTUDF Command - EDTUDF Notes FROM3XB Command - FROM3XB Notes PCFROMPC Command PCTOPC Command PGMFROM3XB Command PGMTO3XB Command PRTFRO3XB Command PRTTO3XB Command PRTXFROMPC Command PRTXTOPC Command PWRDELETEB Command PWRFROM3XB Command PWRRENAMEB Command PWRTO3XB Command RENAMEB Command SBMBATXFER Command SBMSCHJOB Command - To Schedule a Job STRSEU Command TESTB Command TO3XB Command VWSAVRQS Command - VWSAVRQS Notes XLA
ALOCATB Command Parameter description Qualified file name Display status message? Parameter name QFNAME DSPSTSMSG Parameter values micro file name *YES or *NO The ALOCATB command allocates (creates) an empty file on the micro. QFNAME The name of the micro file to be allocated. For additional information, see About Microcomputer Files in Chapter 3. DSPSTSMSG Displays program status messages during the execution of the command. The default is *YES. To turn the messages off, enter *NO.
DELETEB Command Parameter description Qualified file name Notify Operator? Display status message? Parameter name QFNAME NOTIFY DSPSTSMSG Parameter values micro file name *YES or *NO *YES or *NO The DELETEB command deletes a file on the micro. QFNAME The name of the micro file to be deleted. For additional information, See About Microcomputer Files in Chapter 3. NOTIFY Specifies whether you will be notified if the file to be deleted is not found.
EDITTABLE Command Parameter description Source member Source file Parameter name SRCMBR SRCFILE Library name Translation table file name TRANSFILE Library name Translation table member name TRANSMBR Parameter values ETOA2 ETOA3 ATOE1 ATOE3 ETOA1M ETOA2M ATOE1M translation table member name TRANSSRC source file name *LIBL library name TRANSLATE MACTAB file name *LIBL library name *SRCMBR member name The EDITTABLE command compiles an ETU translation table after you have edited it with the STRSEU comm
Mac Users: If you use the TRANSFILE default (TRANSLATE), the member names will have an M on the end of the name (for example, ATOE1M). The Mac tables are also shipped in a translate file called MACTAB. The members in this file do not have the M at the end of the name (for example, ATOE1). Library The name of the library containing the TRANSFILE. *LIBL is a valid library. TRANSMBR The member name for the compiled table.
EDTUDF Command The EDTUDF command allows you to add user-defined options to the ETU Main menu (WSMENUS). Any valid AS/400 command can be added to the menu using this function. Additionally, ETU utilities, such as EDTUDF, can be added to the ETU menu. To add a user-defined option, enter the command EDTUDF on the AS/400 command line and press F4. You will first be prompted to enter a user profile. You can add user-defined functions for a single user or a group of users.
EDTUDF Notes Up to ten user-defined functions can be added to the ETU menu. The first time you start the EDTUDF utility (where no user-defined functions have previously been created), the utility will be in “add” mode. While in add mode, you may create as many user-defined functions as you like, up to ten. Each time you start the EDTUDF utility, (after you add one or more userdefined functions) it will be in “change mode”. To place EDTUDF in add mode, use the F9 function key.
FROM3XB Command Parameter description File name Parameter name FRMFILE Library name Member name FRMMBR *SAVE file type? Strip seq/date file Type of translation SAVTYP STRIP TRANSLATE Translation file name TRNSFILE Library name Member name Record length DDS or F&I file name TRANSMBR RECL FLDDEFFILE Library name Member name Qualified file name Save request definition? Request name Display status message? FLDDEFMBR QFNAME1 SAVRQS DSPSTSMSG Parameter values host file name translation table member na
SAVTYP *LAST Transfers the last member arrival sequence in the file. *ALL Transfers all members from the FRMFILE file into one micro file. *ALL is not valid with *DIF translation. Used to transfer files that were previously transferred to the host with the *SAVE file type using the TO3XB command. *NO The file being transferred was not previously transferred to the host with the *SAVE file type (the default).
Library The library containing the source for the translation tables. *LIBL is the default. TRANSMBR The TRANSFILE member name. The default name is ETOA1, an EBCDIC-to-ASCII table supplied with ETU. ETOA2 should be used for fixed-length record translations. RECL The record length of the translation work file. Valid record length entries are: *FILE The record length of the FRMFILE file is used. 1-9989 The record length for the translation work file.
DSPSTSMSG Displays program status messages during the execution of the command. The default is *YES. To turn the messages off, enter *NO. FROM3XB Notes When you specify file translation with this command, the AS/400 file (FRMFILE) is read by the translate program. After the program translates the data, it writes the translated data into a workfile that is created for this purpose (PCTTOWORK in QTEMP). It is this workfile that will then be transferred to the micro.
PCFROMPC Command Parameter description Qualified file name Transfer from which micro? Parameter name QFNAME MICLIST1 Transfer to which micro? MICLIST2 Save request definition? Request name Display status message? SAVRQS DSPSTSMSG Parameter values micro file name Device name(s) of one or more micros. *REQUESTER device name of target micro *YES or *NO Name *YES or *NO The PCFROMPC command transfers a file from one or more microcomputers to a single microcomputer.
MICLST2 The device name of the target micro. The default, *REQUESTER, transfers multiple files to the micro from which you initiate the command. (You must be authorized to any device you specify in this parameter, or the transfer will fail.) If multiple files are transferred, the files transferred to the target micro have the same name as the device from which they came. If the host device name is longer than eight positions, the file name on the micro will be in the format: XXXXXXXX.XX.
PCTOPC Command Parameter description Qualified file name Transfer from which micro? Parameter name QFNAME MICLIST1 Transfer to which micro? MICLIST2 Save request definition? Request name Display status message? SAVRQS DSPSTSMSG Parameter values micro file name Device name(s) of one or more micros. *REQUESTER device name of target micro *YES or *NO Name *YES or *NO The PCTOPC command transfers a file from one micro to one or more other micros.
DSPSTSMSG Displays program status messages during the execution of the command. The default is *YES. To turn the messages off, enter *NO.
PGMFROM3XB Command Parameter description Qualified file name Program Library name Parameter name QFNAME PGM Display status message? Target release level DSPSTSMSG TGTRLS Parameter values micro file name host program name *LIBL library name *YES or *NO *CURRENT see SAVOBJ command for other parameters The PGMFROM3XB command transfers a host executable program from the AS/400 to a specified file on the micro. Do not use this command for transferring program source code.
PGMTO3XB Command Parameter description Qualified file name Program Library name Parameter name QFNAME PGM Display status message? DSPSTSMSG Parameter values micro file name host program name *LIBL library name *YES or *NO The PGMTO3XB command transfers a host executable program from a file residing on the micro. Do not use this command for transferring program source code. Transfer source code with the FROM3XB, PWRFROM3XB, TO3XB, or PWRTO3XB command.
PRTFROM3X Command Parameter description Output Queue Library name Parameter name OUTQ Translation table name TRANSFILE Library name Translation table member name TRANSMBR Parameter values output queue name *LIBL library name TRANSLATE table file name *LIBL library name ET0A1 member name The PRTFROM3X command allows you to transfer a print file from the host to a micro. This command is interactive only.
Figure 10-1 The PRTFROM3X Translate prompt screen Translate spool file to PC: (TRANSLATE) Type choices, press Enter. Name of PCPRINT file on host: . > PCPRINT Library name: . . . . . . . . > QTEMP F3=Exit F4=Prompt F24=More keys F5=Refresh F12=Cancel Name Name, *LIBL Bottom F13=How to use this display The screen you get with 1=Copyprt Figure 10-2 The PRTFROM3X Transfer prompt screen Transfer from 3X: (FROM3XB) Type choices, press Enter. File name: . . . . . Library name: . .
PRTTO3X Command Parameter description Qualified file name Output queue Parameter name QFNAME OUTQ Library name Lines per page LINES Lines per inch LPI Characters per inch CPI Form width WIDTH Overflow line number OVERFLOW Type of form label FORMTYPE Number of copies COPIES Place job on hold? Translation table name HOLD TRANSFILE Library name Translation table member name TRANSMBR Parameter values micro file name host output queue name *LIBL library name 66 lines per page 6 lines per inch
OVERFLOW The overflow line on the new print job being added to the AS/400 print queue. The default is 63. FORMTYPE The forms type label to associate with the new print job being added to the AS/400 print queue. The default is *STD. COPIES The number of copies of the new print job to print. The default is 1. HOLD Specifies whether the print file should automatically start and print the job at the completion of the translation/transfer.
PRTXFRMPC Command Parameter description PC data file Library name Parameter name FILE PC data member name PCMBR Output queue OUTQ Library name Lines per page LINES Lines per inch LPI Characters per inch CPI Form width WIDTH Overflow line number OVERFLOW Type of form label FORMTYPE Number of copies COPIES Place job on hold? Translation table name HOLD TRANSFILE Library name Translation table member name TRANSMBR Parameter values Host file name *LIBL library name FILE member name host
LPI The number of lines per inch to allocate to the new print job being added to the AS/400 print queue. The default is 6. CPI The number of characters per inch to allocate to the new print job being added to the AS/400 print queue. The default is 10. WIDTH The width of the forms being printed. Valid entries are 1 through 198. The default value is 132. OVERFLOW The overflow line on the new print job being added to the print queue (OUTQ). The default is 63.
PRTXTOPC Command Parameter description PC data file Library name Parameter name PCDATA PC data member name PCMBR Action to perform ACTION Spooled output file SPLFILE Spooled output file number SPLNBR Job name or * for current job User name Job number Copy file name Library name JOB Copy file member name Type of Copy file COPYMBR CTLCHAR Lines per page LINES Begin translation in which column? End translation in which column? Translation table file name Library name FROM Translation table me
ACTION Specifies the action the program is to perform. *COPYPRT Use *COPYPRT it the data is resident on the print queue. The command will first perform the AS/400 function CPYSPLF and then translate that file into a PC print file format. The micro print file should then be transferred to the selected micro file. *TRANSLATE use *TRANSLATE if you have already executed the AS/400 function CPYSPLF; only the translation from the CPYSPLF format to the micro print format needs to be done at this time.
current task. The specified value must be in the range of 1 to 198. The default value is 1 (one). TO The column of the printed report on which to end translation. This can be used to restrict the copying of either sensitive data, or data that has no meaning for the current task. The specified value must be in the range of 1 to 198. The default “TO” column is 132. TRANSFILE The qualified file name of the translation table file to be used. The default is TRANSLATE.
PWRDELETEB Command Parameter description Qualified file name Process done on which micro? Notify Operator? Display status message? Parameter name QFNAME MICLIST NOTIFY DSPSTSMSG Parameter values micro file name *REQUESTER device name *YES or *NO *YES or *NO Use PWRDELETEB to delete a PC file on a specified micro from either a PC in emulation mode or from a dumb terminal. Issue the PWRDELETEB command from the command line and press F4 to prompt. You can also run this command in batch mode.
PWRFROM3XB Command Parameter description File name Parameter name FRMFILE Library name Parameter values host file name translation table member name *LIBL library name *FILE *ALL micro file name *REQUESTER device name Member name FRMMBR Qualified file name Transfer to which micro? QFNAME1 MICLIST Delete host file after transfer? *SAVE file type? Strip seq/date file Type of translation DLTFILE *NO or *YES SAVTYP STRIP TRANSLATE Save request definition? Request name Translation file name SAVRQS
Comparison value Entry program Library name ENTRYPGM Exit program Library name EXITPGM Display status message? DSPSTSMSG numeric value or ‘alphabetic value’ program name *LIBL library name program name *LIBL library name *NO or *YES The PWRFROM3XB command performs all functions of the FROM3XB command: it transfers files from the AS/400 to a micro and, optionally, translates the data.
QFNAME1 The name of the micro file to contain the data from the AS/400. For additional information, see About Microcomputer Files in Chapter 3. MICLST The device name of the microcomputers to which the file will be transferred. *REQUESTER Transfers the file to the micro from which the command is initiated. Use only with interactive transfers. device name Transfers the file to the micro with this device name.
SAVRQS Saves the current request definition so it can be reused at a later time. The request definition is this completed PWRFROM3XB command with the parameter values as you have specified them. The default is *NO. To save the request definition, specify *YES and enter the request name you desire. Request name The name of the SAVRQS request definition. The request name can be up to ten characters long. (To recall the saved request, use the ETU command VWSAVRQS.
Length May be from 1 to 9989 bytes long. If an ASCII fixed-record-length translation is to be performed, specify *FILE to produce the desired file. If not translating to ASCII fixed-length records, any record length may be specified that could allow for better performance by buffering the data. FLDSEL Allows the transfer of up to 25 user-specified fields from the host to the micro.
all records in the file. The other relationships are *AND, *OR, *ANDIF, *ORIF and are used in situations where more than one test case is performed. Field to be Tested Specifies the field to be tested. Use the FRMFILE parameter for the field name. Relational Operator The relationship between the field to be tested and the comparison value.
PWRRENAMEB Command Parameter description Qualified file name New file name Process done on which micro? Display status message? Parameter name QFNAME1 NEWFIL MICLIST DSPSTSMSG Parameter values micro file name new file name *REQUESTER device name *NO or *YES Issue PWRRENAMEB on the command line and press F4 to prompt in order to rename an existing micro file on a specified micro or micros. You can issue PWRRENAMEB from a micro in emulation mode or from a dumb terminal.
PWRTO3XB Command Parameter description Qualified file name Transfer from which micro? Parameter name QFNAME1 MICLIST Parameter values micro file name *REQUESTER device name File name TOFILE host file name *MULTI *LIBL library name *FILE *MULTI member name *FILE 0-9989 *TEXT or *YES *NO or *NONE *DIF *BASICS *TAB *RELACE *ADD *DATA *SAVE *SRC *SAVF *NO or *YES *NO or *YES *NO or *YES Library name Member name FRMMBR Record length Type of translation RECL TRANSLATE Add or replace records? ADDRPL Fi
The PWRTO3XB command performs all the functions of the TO3XB command: it transfers files to the AS/400 from a micro and, optionally, translates the data. In addition to these functions, PWRTO3XB offers the following additional features: Multiple-device transfer -- a single file from one or more micros • can be sent to the host. The micros involved in a file transfer must be of the same platform, either DOS-based PC or Mac, but not both.
from which it was transferred. *MULTI Transfers the files into multiple host files. Data Description Specifications (DDS) must be specified when using *MULTI as the value in the TOFILE parameter. Library name The name of the library containing the host file. The default, *LIBL, searches all libraries in your library list for the file. You must specify an existing library if the host file is to be created with this command. Member name The TOFILE member name. You may use one of the following values.
currently exists on the micro. ADDRPL For transfers to existing files: indicates whether the transferred file will replace the data in the file or be added to it. The default is *REPLACE. To add to the existing data, specify *ADD. FILETYPE The type of TOFILE file, if the host file is to be created with this command. *DATA A physical file is created. RECL or FLDDEFFILE is used to create the data file. (This is the default.) *SAVE Permits offline storage, and moves executable programs between micros.
*YES The data is truncated, if necessary. To truncate indicates that once the current host record is filled, any additional data for that record as it resided on the micro will be lost. Additionally, the record is written to the host only after ETU reads an end-of-record character sequence in the qualified file. The end-of-record character is defined in the translation table (see Table 8-1, position 40-41, in Chapter 8).
same name as the source file. ENTRYPGM The name of any user-specified entry program to be run prior to transferring the file. Library name EXITPGM The name of any user-specified exit program to be run after transferring the file. Library name DSPSTSMSG The name of the library containing the specified program. The name of the library containing the specified program. Displays program status messages during the execution of this command. The default is *YES. To turn the messages off, enter *NO.
RENAMEB Command Parameter description Qualified file name New file name Display status message? Parameter name QFNAME1 NEWFIL DSPSTSMSG Parameter values micro file name new file name *NO or *YES The RENAMEB command renames a file on the micro. Mac Users: option. The directory dialog box is unavailable for the RENAME QFNAME The name of the micro file (including the path) to be renamed. For additional information, see About Microcomputer Files in Chapter 3.
SBMBATXFER Command Parameter description Command name to submit Job name Parameter name SBMCMDNAME JOBNAME Job description JOBD Library name Job queue JOBQ Library name Display status message? DSPSTSMSG Parameter values ETU command name *JOBD submitted job name *USERPRF job description name *LIBL library name QBATCH Job queue name *LIBL library name *NO or *YES The SBMBATXFER command submits the ETU power commands (PCFROMPC, PCTOPC, PWRFROM3XB, and PWRTO3XB) to batch.
SBMSCHJOB Command Parameter description Command Parameter name SBMCMD Hour in 24 hour clock format Minutes Date in system format SCHHR Job name JOBNAME Job description JOBD Library name SCHMIN SCHDT Parameter values command name ? 00-24 00-59 *TODAY date 1-14 *JOBD submitted job name *USERPRF job description name *LIBL library name The SBMSCHJOB command allows you to schedule batch jobs for execution in the future.
To Schedule a Job To schedule a job, first start a job called SCHPGM. This job controls the SBMSCHJOB command. Then enter SBMSCHJOB on the AS/400 command line, press F4, and fill out the following parameters. SCHCMD The name of the command you want to schedule. You can enter the command followed by the entire command string, or enter a question mark (?) followed by the command name, which displays the command prompt after you complete the remaining parameters.
STRSEU Command Parameter description Source file Parameter name SRCFIlE Library name Source member SRCMBR Source type to create TYPE Text description TEXT Parameter values TRANSSRC *PRV file name *LIBL library name *SELECT *PRV source member file name *SAME type *BLANK descriptive text The STRSEU (Start Source Entry Utility) command is the AS/400 command used to change or create a translation table.
TYPE The type of source to be edited or created. Specify any combination up to 10 characters, or one of the AS/400 types supported by SEU. *SAME Specifies that the same source type is used as when the member was edited. type TEXT *BAS, *BASP, *CBL, *CL, *CMD, *DSPF, *LF, *PF, *PLI, *PRTF, *PRG, *RPT, *TXT, *CLP, *CMNF, *DFU, *QRY, *MXDF You can enter a description that identifies the source member. The description can be up to 50 characters. The default is *BLANK.
TESTB Command Parameter description Qualified file name Notify operator? Parameter name QFNAME NOTIFY Starting position in LDA POS Display status messages? DSPSTSMSG Parameter values micro file name *YES *NO no default 1-1012 *YES *NO The TESTB command tests for the existence of a file on the micro. The result of the test is returned in a data area (PCTDTAARA) in QTEMP for later use. If you specify NOTIFY (*YES), you will be notified if the file exists via a completion message.
TO3XB Command Parameter description File name Parameter name TOFILE Library name Member name FRMMBR Record length File Type RECL FILETYPE Add seq/date field Type of translation SRCSEQ TRANSLATE Translation file name TRNSFILE Library name Member name TRANSMBR Truncate text TRUNCATE DDS or F&I file name FLDDEFFILE Library name Member name Qualified file name Save request definition? Request name Display status message? FLDDEFMBR QFNAME1 SAVRQS DSPSTSMSG Parameter values host file name *MULTI
name if the file is to be created with the TO3XB command. MBR The TOFILE member name. If the member already exists, it will be cleared. If the member does not exist, it will be added to the file. *FILE indicates that the member name is the same as the value in the TOFILE parameter. RECL The record length of the TOFILE file to be used in either allocating (creating) the file or verifying the record length of an existing file. A record length of zero can be specified if the file already exists.
TRANSLATE Determines whether the data is to be translated, and if so, what type of translation is to be performed. *TEXT or *YES The qualified file resides in ASCII Text format and is to be translated for the AS/400. This is the default. *DIF The qualified file resides in DIF format and is to be translated for the AS/400. *BASICS The qualified file resides in BASIC Sequential format and is to be translated for the AS/400.
Use the default, *NONE, or its equivalent, *DDS, for existing host files. FLDDEFMBR The member contained in the FLDDEFFILE. The default,*FILE, uses the member with the same name as the file specified in FLDDEFFILE. QFNAME1 The name of the micro file to be transferred. For additional information, see About Microcomputer Files, in Chapter 3. SAVRQS Saves the current request definition so it can be used at a later time.
VWSAVRQS Command The VWSAVRQS command displays the request definitions saved with the FROM3XB, PWRFROM3XB, PWRTO3XB, PCTOPC, PCFROMPC, and TO3XB commands. Once you display the request definitions, you can run them interactively or submit the power commands to batch. You can also change or delete any of the saved requests. You may take action on more than one saved request at a time. To use the command, enter VWSAVRQS on the AS/400 command line.
ETU400 User Guide 011603 10-53
XLATEFROM Command Parameter description PC data file name Library name Parameter name PCDATA PC member name PCMBR Host output data file Library name TOFILE Host output file member name Record length File Type MBR Add seq/date field Type of translation SRCSEQ TRANSLATE Translation file name TRNSFILE RECL FILETYPE Library name Member name TRANSMBR Truncate text TRUNCATE Job description Library name JOBD Field translation definition DDS or F&I file name Library name FLDDEFFILE Member name
Library The library containing the PCDATA file. *LIBL is the default. PCMBR The PCDATA file member name. The default is *FILE. TOFILE The qualified file name of the AS/400 file into which the micro data is to be written. Library The library containing the TOFILE file. *LIBL is the default. TOMBR The TOFILE member name. If the member does not exist, it will be added to the file. If it does exist, the member will first be cleared before the current data is written. The default is *FILE.
TRANSFILE The qualified file name of the translate table file to be used. The default is TRANSLATE. Library The library name containing the TRANSFILE file. *LIB is the default. Mac Users: There are two files you can use. If you use the default file (TRANSLATE), the member names have an M on the end of the name (for example, ATOE1M). The Mac translation members are also shipped in a file called MACTAB. The members in this file do not have the M at the end of the name (for example, ATOE1).
*FIRST Transfers the first member (arrival sequence)in the file. *LAST Transfers the last member (arrival sequence)in the file.
The XLATETO command translates an AS/400 physical file member prior to transferring it to a micro. It is intended for use in instances where translation is to occur sometime before the actual transfer with the FROM3XB command (for instance, on a long-distance telephone line in order to keep line costs down). This command can be put on the JOBQ with the SBMJOB command (in that case, do not specify the JOBD parameter).
*BASICS Converts the file to BASIC Sequential format. *TAB Converts the file to BASIC Sequential format with tab characters as the delimiters. TRANSFILE The file name of the translation table file to be used. The default is TRANSLATE. Mac Users: There are two files you can use. If you use the default file (TRANSLATE), the member names have an M on the end of the name (for example, ETOA1M). The Mac translation members are also shipped in a file called MACTAB.
FLDDEFMBR The FLDDEFFILE member name. You can enter the member name or one of the following values: *FILE Transfers the member with the same name as the FLDEFFILE file (the default value). *FIRST Transfers the first member (arrival sequence) in the file. *LAST Transfers the last member (arrival sequence)in the file.
Part Four Appendices The “Appendices” provide reference and supplemental information.
Appendix A INSIDE ETU About This Chapter Editing User-defined Menu Options EDTUDF Parameters EDTUDF Example Configuring the Audit Trail The CFGAUDIT Parameters Checking the Audit Trail Working With ETU Security Granting Authority to a Command Revoking Authority From a Command Regranting Authority to a Previously Revoked Command Securing Devices on the AS/400 Removing ETU From the AS/400 ETU400 User Guide 011603 A-1
About This Chapter ETU includes utilities that allow you to customize the way ETU works on your AS/400. This chapter describes the utilities and explains how to use them. This chapter is intended for experienced host users and the security officer. Some tasks you can perform with the ETU utilities include: • adding user-defined menu options to the ETU menu; • changing how the ETU audit trail is configured; • granting and revoking authority to the ETU commands; • removing ETU from your AS/400.
Editing User-defined Menu Options With ETU it's possible to add menu options, called user-defined functions, to the ETU Main menu. A user-defined function is any command or program that can be run on the AS/400. Even ETU utilities, like EDTUDF, can be added to the ETU menu. Once a user-defined function has been added to the menu, you can execute the option as you do any ETU option -- by entering the option number on the ETU command line and pressing ENTER.
EDTUDF Parameters Description The description of the user-defined function as it will appear on the ETU Main menu. It may be up to 32 character long. Function The AS/400 command that will run when the menu option is issued. Only the first 20 characters will be displayed. Mode Specifies how the command will execute when selected from the ETU Main menu. Valid entries are: *PMT Displays the prompt screen for the command specified in the Function parameter.
EDTUDF Example In this example, you will add the ETU utility EDTUDF to the ETU Main menu. Define the menu option so that you are prompted for parameters each time you call the option from the menu so it displays only on your own menu, and appears on your menu as Edit User-defined Functions. 1. Enter the EDTUDF command on the AS/400 command line. edtudf 2. Press F4 to prompt for the parameters. The Enter User Profile screen displays. 3.
Configuring the Audit Trail An audit trail is produced for the ETU commands FROM3XB, PCFROMPC, PCTOPC, PWRFROM3XB, PWRTO3XB, and TO3XB. The purpose of an audit trail is to inform you whether a file transfer operation was successful, and, if not, why it was not. When you first install ETU, the audit trail is configured as active with entries sent on hold to the QPRINT output queue.
The CFGAUDIT Parameters CRTAUDIT Turns the audit trail on or off. The default, *YES, creates an audit trail for all users on the system. To turn off the audit trail for all users, enter *NO. OUTQ The name of the output queue to which the audit trail entries are sent. The default is QPRINT. You may enter any valid AS/400 output queue. Library HOLD The library in which the output queue resides. *LIBL is a valid library name.
Checking the Audit Trail All ETU transfer operations performed with the above-named ETU commands create entries in the audit trail in the QPRINT output queue. To view the audit trail, display the QPRINT output queue by entering the command WRKOUTQ QPRINT on the AS/400 command line. Each ETU audit trail entry is listed in the output queue as ETUADTPP. To view an entry, enter 5 next to the entry and press ENTER. The audit trail for the entry you selected displays.
Working with ETU Security For the Security Officer: The ETU menuing system takes advantage of the security provided with the AS/400. This allows you to decide which users on your system will have access to which ETU commands. When ETU is first installed on your host system, the only profiles that are authorized to the ETU power commands are QSECOFR, and any other user profile with all object (*ALLOBJ) authority. The menu options for the power commands do not display on the ETU menus of other users.
Revoking Authority From a Command When you revoke authority to a command, the users from whom the command is revoked will no longer be able to use the command, nor will the command's menu option display on ETU menus. How you revoke authority depends on the command you are revoking. To revoke authority from an ETU power command: 1. Sign on to the AS/400 as QSECOFR. 2. Enter the RVKOBJAUT command (revoke object authority) on the command line and prompt (press F4): rvkobjaut 3.
Securing Devices on the AS/400 For the Security Officer: The ETU power commands allow a properly authorized user to transfer files to and from multiple devices. The devices to which a user is authorized can be limited using the security built into the AS/400. Then, if a user tries to transfer data to or from the device to which he is not authorized, the program ends and sends the following error message to the screen: Unable to open display file with device specified.
Removing ETU From the AS/400 ETU includes a utility that makes it easy to remove the ETU software from your host system. (You may need to remove ETU from your system if, in the future, you upgrade to a new version of ETU.) This utility, called RMVETU, removes all the ETU objects from the library in which you loaded ETU, and leaves intact all non-ETU objects in that library.
Appendix B ETU COMPATIBILITY About this Appendix Using ETU with Autokey Batch Files Modifying an Autokey Batch File – Example ETU400 User Guide 011603 B-1
About This Appendix ETU 5.01 supports all the command functions of earlier versions of ETU. However, the menus for ETU 5.01 have been enhanced. This may cause some Autokey batch files that were used with earlier versions of ETU not to execute properly. This appendix explains which types of Autokey batch files may need to be modified, as well as how to modify them.
Using ETU 5.01 and above with Autokey Batch Files The menu for ETU 5.01 and above changed from earlier versions. Some menu options have been moved from the Main menu to a Utility menu, and most all ETU commands have received new menu option numbers. (For example, the FROM3XB command in version 5.0 is option 13. In earlier versions of ETU, the FROM3XB command is option number 1.) These changes may cause some existing Autokey batch files not to work properly.
Appendix C CREATING DDS SPECIFICATIONS About This Appendix Creating DDS Specifications ETU400 User Guide 011603 C-1
About This Appendix This appendix explains how to define AS/400 files using Data Description Specifications (DDS specs). DDS specs define field-oriented files on the AS/400, which are files in either *TAB, *BASICS, or *DIF format. Before you can transfer a field-oriented file, the file must be defined with DDS specs. DDS specs are not needed when transferring straight text files (*TEXT format). DDS specs are created using the Programming Development Manager (PDM) utility on the AS/400.
Creating DDS Specifications In order to transfer field-oriented data, like that found in spreadsheets or databases, you must create a template that tells the AS/400 where each field begins and ends, and what type of data will be in each field. This is done with DDS specs or F&I specs. See Appendix D for a detailed explanation of creating F&I specs. The PDM utility on the AS/400 is used to create the DDS.
To create a DDS specs for a file, use the PDM (Programming Development Manager) utility on the AS/400. The steps below and on the following pages describe how to create DDS specs for the file shown on the previous page. 1. Log on to the AS/400. 2. Type STRPDM on the command line of the AS/400, and then press ENTER. The AS/400 PDM screen, shown in Figure C-2, appears. Select option 3 and press ENTER to work with members.
3. The Select Members screen, shown in Figure C-3, appears. Type the required data in each prompt as explained in the following instructions, and then press ENTER. Figure C-3 The Select Members screen Specify Members to Work With Type choices, press Enter. File . . . . . . . . . . QDDSSRC Library . . . . . . . . *LIBL Member: Name . . . . . . . . . Type . . . . . . . . .
4. The Work With Members screen, shown in Figure C-4, appears. Press F6 to create the member. Figure C-4 The Work With Members screen Work with Members Using PDM File . . . . . . Library . . . . NLRISC QDDSSRC QGPL Position to Type options, press Enter. 2=Edit 3=Copy 4=Delete 5=Display 8=Display description 9=Save 13=Change text Opt Member BASICTST QDSIGNON SAMPLDDS Type PF Text PF sample DDS spec . . . . . 6=Print 14=Compile 7=Rename 15=Create module...
5. The Start Source Entry Utility (SEU) screen, shown in Figure C-5, appears. Type SAMPLE in the Source member prompt, and then press ENTER. Figure C-5 The Start Source Entry Utility screen Start Source Entry Utility (STRSEU) Type choices, press Enter. Source file . . . Library . . . . Source member . . Source type . . . Text 'description' F3=Exit F4=Prompt F24=More keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > QDDSSRC . > QGPL . SAMPLE . *SAME .
6. The Edit screen, shown in Figure C-6, appears. Press F4 for prompts to begin entering data. Figure C-6 The SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......
7. To create the DDS, enter the letter R in the Name Type field and RECORD in the Name prompt as shown in Figure C-7, and then press ENTER. This identifies this record as the record format name for the physical file defined by these DDS specs. For each prompt, you can press HELP to receive more information. Figure C-7 The SEU Edit Screen after F4 prompt Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......
8. The DDS Edit screen, shown in Figure C-8, appears. Position the cursor in column 1 of line 0001.00, then type the letters IP. Press ENTER. The letter I places SEU in insert mode and the letter P allows you to be prompted to enter the next record. Figure C-8 The SEU Edit Screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......Functions+++++++++++++++++++++++++++ IP01.
9. The 0001.00 edit screen, shown in Figure C-9, appears. Type the required data in each prompt as explained in the following instructions, and then press ENTER. Figure C-9 SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......Functions+++++++++++++++++++++++++++ 0001.
10. The 0002.00 edit screen, shown in Figure C-10, appears. Type the required data in each prompt as explained in the following instructions, and then press ENTER. Figure C-10 The SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......Functions+++++++++++++++++++++++++++ 0001.00 0002.
11. The 0003.00 edit screen, shown in Figure C-11, appears. Type the required data in each prompt as explained in the following instructions, and then press ENTER. Figure C-11 The SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......Functions+++++++++++++++++++++++++++ 0001.00 0002.00 0003.
12. The 0004.00 edit screen, shown in Figure C-12, appears. Type the required data in each prompt as explained in the following instructions, and then press ENTER. Figure C-12 The SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........T.Name++++++RLen++TDpB......Functions+++++++++++++++++++++++++++ 0001.00 0002.00 0003.00 0004.
13. The Edit screen, shown in Figure C-13, appears. When you have defined each field, press F3 to exit the SEU. The DDS for the example is now complete. Press F3 to exit. If you made a mistake, place the cursor on the line requiring the change, and then press F4. To insert a line, place the cursor on the line that you want the new line to appear after, and then press F4. Otherwise, press F3 to exit. Figure C-13 The SEU Edit screen Columns . . . : 1 80 Edit QGPL/QDDSSRC SEU==> SAMPLE FMT PF .....A..........
14. The Exit screen, shown in Figure C-14, appears. Enter a text comment, if desired, and then press ENTER. A text comment can help you remember the purpose of the DDS spec you create. Figure C-14 The SEU Exit screen Exit Type choices, press Enter. Change/create Member . . File . . . Library . Text . . . member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15. The PDM screen, shown in Figure C-15, appears. Press F3 to exit to the AS/400 main menu. The demonstration file is now ready to be transferred to the AS/400. Be sure to verify that the file has been created by reading the member added to file message at the bottom of the screen. Figure C-15 The PDM screen Work with Members Using PDM File . . . . . . Library . . . . NLRISC QDDSSRC QGPL Position to Type options, press Enter.
Appendix D CREATING F&I SPECIFICATIONS About This Appendix Creating DDS Specifications ETU400 User Guide 011603 D-1
About This Appendix On the AS/400, files can be defined with Data Definition Specifications (DDS) or Format and Input specifications (F&I). This appendix explains how to define files using F&I specs. F&I specs define field-oriented files on the AS/400, which are files in either *TAB, *BASICS, or *DIF format. Before you can transfer a field-oriented file, the file must be defined with F&I specs. F&I specs are not needed when transferring straight text files (*TEXT format).
Creating F & I Specifications In order to transfer tabular data, like that found in spreadsheets or data bases, you must create a template that tells the AS/400 where each field begins and ends, and what type of data will be in each field. This is done through the use of Format and Input (F&I) specifications or DDS specifications. See Appendix C for a detailed explanation of DDS specifications.
To create an F&I specification for a file, use the Source Entry Utility (SEU) on the AS/400. The steps below and on the following pages describe how to create F & I specs for the file shown on the previous page. 1. Sign on to the AS/400. 2. Enter STRSEU on the command line of the AS/400, and then press F4. The Start Source Entry Utility (STRSEU) screen, shown in Figure D-2, appears. If you receive an error after this command, you may not have the authority to perform this task.
4. When the SEU Edit screen appears (see Figure D-3), press F4 to display a data area prompt in which to enter the file specification record. The file specification record includes the form type, the name of the file being defined, the file type, the record length, and the type of media on which the file will reside. To create the file specification record, enter the file description specification in the data area prompt at the bottom of the screen exactly as shown in Figure D-3, and then press ENTER.
Column 15 is the File Type and must contain the letter I, which defines the file as an input file. Column 16 is the File Designation and must contain the letter P. Column 19 is the File Format and must contain the letter F. Columns 24 through 27 allow you to specify the record length of the data file. This example uses 128, which is the ETU default. Columns 40 through 46 are used to indicate where the F&I source member will be found. DISK means the file will reside on the hard disk of your host system.
F3=Exit F12=Cancel F4=Prompt F5=Refresh F11=Previous record F23=Select prompt F24=More keys 6. The field statement number 0002.00 appears. Enter the input specification in the data area prompt at the bottom of the screen exactly as shown in Figure D-4, and then press ENTER. Column 6 is the Form Type and must contain the letter I. Columns 7 through 14 may contain a valid file name for documentation purposes. This example uses filename SAMPLE. Type the letters NS for No Sequence in columns 15 and 16.
7. Display the next statement number by typing I1 over the first two positions of the line containing statement 0002.00 and pressing Enter. When the new statement line is displayed, press F4 to display a prompt in which to enter the input specification. 8. The field statement number 0003.00 appears. Here you will define the first field in the SAMPLE file. Enter the data exactly as shown in the data area prompt at the bottom of the screen, as shown in Figure D-5, and then press ENTER.
Use columns 48 through 51 to enter the ending position of the Name field. This field ends in position 17. Use columns 53 through 58 to title the field for reference. This example calls the field NAME. After you press Enter, the input specification you've just created moves to the top of the screen.
9. Display the next statement number by typing I1 over the first two positions of the line containing statement 0003.00 and pressing Enter. When the new statement line is displayed, press F4 to display a prompt in which to enter the input specification. 10. The field statement number 0004.00 appears. Here you will define the second field in the SAMPLE file.
Use columns 48 through 51 to enter the ending position of the Job Title field. This field ends in position 52. Use columns 53 through 58 to title the field for reference. This example calls the field TITLE. After you press Enter, the input specification you've just created moves to the top of the screen.
11. Display the next statement number by typing I1 over the first two positions of the line containing statement 0004.00 and pressing Enter. When the new statement line is displayed, press F4 to display a prompt in which to enter the input specification. 12. The field statement number 0005.00 screen appears. Here you will define the third field in the SAMPLE file. Enter the data exactly as shown in the data area prompt at the bottom of screen, as shown in Figure D-7, and then press ENTER.
Use columns 48 through 51 to enter the ending position of the Salary field. This field ends in position 60. Column 52 specifies the decimal places of the numeric field. Use column 52 if the field contains numeric data and you would like to specify the number of decimal positions. For our example, SALARY, you will use 2 decimal positions. Use columns 53 through 58 to title the field for reference. This example calls the field SALARY.
F12=Cancel F23=Select prompt F24=More keys The Type entry is not H, F, E, L, I, C, O, or U (position 6). Column 6 is the Form Type and must contain the letter I, which designates this record as an input specification. Use columns 44 through 47 to enter the beginning position of the City field. This field starts at position 61. Use columns 48 through 51 to enter the ending position of the City field. This field ends in position 76. Use columns 53 through 58 to title the field for reference.
If you need to insert a line, enter I1 in the first two positions of the line number that will precede the new line. For example, enter I1 over line number 0003.00 to insert a new line following line 0003.00. 15. Press F3 to complete the F & I specification. The SEU Exit screen appears as shown in Figure D-9. Verify that the Change/create member parameter is Y for yes. Also verify that the member name and the library name on this screen are correct, and then press ENTER.
Appendix E ERROR MESSAGES: NATIVE MODE ETU400 User Guide 011603 E-1
About This Appendix This appendix lists the ETU error messages that are most likely to occur when you use ETU. The messages appear in order of their ETU message number, which precedes each message. For each message, you will find the error message number, message text, and possible causes and Solutions.
USR MESSAGES: If a USR message that you are experiencing is not in this document, please try this procedure, on the AS/400, to get more information: 1. Go to a command line and type: WRKMSGF ETUMSGF and press the key. 2. Take a 5 on the ETU message file. 3. Type the error message (USR####) in the 'Position to . . .' field and press . NOTE: If the error message does not show up here, it is not an ETU error message.
TRANSFER PROBLEMS: PROBLEM: When we go into the option to transfer a spool file to a pc file and enter the outq, no spool files show up so we can select the spool files from a list. CAUSE: You must be the owner of the spool file and it must be held in the queue. SOLUTION: You must be the user to submit the print job to become the owner of the spool file.
USER MESSAGES: PROBLEM: “USR0020 Translation failed. Specified record length differs from existing file.” CAUSE: The translation failed because the record length (RECL) you specified in the translation command does not match the record length of the file being translated. SOLUTION: Verify that the record length you specified matches the actual record length of the file. PROBLEM: Getting "USR0022 xxxx bytes moved to/from PC disk/diskette." ... after moving to a new system. He used to monitor for a CPF.
PROBLEM: “USR0032 Error detected while materializing program into AS/400 object file does not contain valid AS/400 object data”. CAUSE: The program you tried to transfer to the host from the PC was not previously transferred to the PC from the host.
PROBLEM: "USR4001 The PC disk/diskette is full - Transfer ended." CAUSE: The disk or diskette to which you are transferring became full during the transfer causing the transfer to end. When transferring a file to the micro with ETU, the size of the file being transferred may not be greater than the capacity of the disk or diskette receiving the file. SOLUTION: Specify a different drive with a greater capacity. PROBLEM: "USR5255 Invalid PC file name or no space for a new directory entry.
PROBLEM "USR5255 Invalid PC file name or no space for a new directory entry" occurs when doing back to back file transfers. CAUSE: Timing problem. SOLUTION: Put a 5-second delay between transfers. PROBLEM "USR6255 Old PC file not found or new PC file name already exists for RENAME command." When he does TESTB, it indicates that the file exists, when he does a rename, it complains that it does not exist. CAUSE: The name you specified for the old PC file in the RENAMEB command was not found.
PROBLEM: "USR7900 System Error - INCORRECT SYSTEM SERIAL NUMBER, CALL SYSTEM SUPPORT STAFF” or on ETU36 "USER 7900 Option (3) - error in host registration system, contact Emerald Technology" CAUSE: Have had ETU/36 for over a year. They are upgrading to an AS/400. SOLUTION: Call sales to transfer the license for $100 and get a new registration for the new machine. CAUSE: ETU/36 will force a registration if you go into the OWNERID screen. SOLUTION: Uninstall and reinstall.
The values specified for the FILETYPE and RECL parameters are not compatible with each other. SOLUTION: If the value for the FILETYPE parameter is ~SAVF, the value for the RECL parameter must be O or 528.
PROBLEM “USR8258 File &1 not found, RECL must be non-zero to create the file”. CAUSE: The host file you specified could not be found. SOLUTION: Specify a new file name or specify a record length (RECL) greater than zero preferably = or greater than the file on the PC. PROBLEM “USR8261 When parameter FRMMBR is *ALL, parameter TRANSLATE cannot be *DIF”. CAUSE: The values specified for the FILETYPE and RECL parameters are incompatible with each other.
PROBLEM “USR9971 A DIF record found in PC file has record Length greater than allowed maximum of 258”. CAUSE: The library containing the ETU programs is not in your library list. SOLUTION: Add the library containing the ETU programs to your library list. CAUSE: While translating a DIF, BASICS, or TAB formatted file into the host format, field over 258 bytes was encountered.
PROBLEM “USR9986 File transfer was interrupted: ("r" to retry or "c" to cancel)”. CAUSE: Only known cause was a remote controller. SOLUTION: Examine the configuration options for the remote controller. Contact that vendor. Possibly reroute or replace controller. PROBLEM When I try to do a transfer, I get a message after the EMULATOR CHECK that says "USR9987 Device is not P.C. or emulator loaded incorrectly." CAUSE: An ETU function has failed because of incorrect data received from the display screen.
PROBLEM "USR9988 ETU encountered information not identified as part of an ETU process." This is sort of a catchall for ETU problems not previously identified and clarified. CAUSE: Trying to type during a transfer. SOLUTION: Do not key inside the emulation screen during a transfer. Do not press on the message regarding the number of day’s left. CAUSE: This could happen if the disk just got full. SOLUTION: Check the disk space on the PC.
CPF MESSAGES: These are the same as User Failures, except it was call by a program. Call Program Fault. PROBLEM Getting “CPF4101 File &2 in library &3 not found or inline data file missing” when doing a file transfer. CAUSE: The file was not opened. The reason code is below. The reason codes and their meanings are as follows: 01 - The library does not exist. 02 - The file does not exist. The library does exist. 03 - The file does not exist. The library specified as *LIBL.
DDM File (CHGDDMF) command or use the necessary procedures to make the library exist on the remote system. PROBLEM: Doing TO3XB on a field-oriented file. There is an error message “CPF5029 Data mapping error on member &4”. CAUSE: A data mapping error occurred on member &4 file &2 in library &3, because the data fields in record number &6, record format &7, member number &8 are in error.
PROBLEM CPF5149: I/O error detected in XLATIN. Using 36 commands. Customer has to end the procedure that creates the file to be transferred before it will transfer successfully. CAUSE: Need detailed printing of joblog using dspjoblog command. Prompt with F4 and change output to *print to get details. Look for sharing errors or errors with subfile. Problem typically occurs in S36 mode. This is not an ETU problem but a system problem.
17 -- The format of the data in a date, time, or timestamp field is not valid. 18 -- There is data in a date, time, or timestamp field that is not valid. 19 -- An unexpected null field was found. 20 -- A field that is not 'null capable' could not be set to null. 21 -- The data has been converted from one CCSID to another. However, substitution characters were used for characters that could not be converted.
SYS MESSAGES: These are not ETU messages. These are System Messages. The exact meaning could probably be traced using F1 on the error message. PROBLEM He is doing FROM3X on a file. Getting an error message: “SYS1185 Error: User One Member INVOICE file INVOICE in library QS36 not found”. CAUSE: The Member name is still set to *FILE. This makes ETU look for a member with the name INVOICE in this case. . SOLUTION: Change the Member name to *ALL. PROBLEM Running ETU 4.
PROBLEM Trying to install software gets this message: “SYS-2594 ETUXFER Trying to Copy Privileged Module PCRCB1 not found”. CAUSE: Customer installed the ETU 36 software but not as a security officer. SOLUTION: The installation requires some privileges that require the use of the security officer privileges. There is no work around as these capabilities are external to ETU and is intrinsic to the SSP. If a person lost the Security Officer password, the whole drive would have to be reformatted.
OCL PROBLEMS PROBLEM: When I submit my OCL, I get this message: “PCT0002 Invalid or missing parameter.” CAUSE: There are two steps to a transfer: the translation and the transfer itself. In OCL the parameters must be entered for each step. SOLUTION: Use two steps: 1) translate, and 2) then transfer using *NONE. PROBLEM: The company has 8 output queues that will have new data every day for the same output queue names. They want to automate as much as possible the daily transfer process.
PROBLEM: I am using ES32 macro commands to do transfers and I get this error message: “USR9988 "ETU encountered information not identified as part of the ETU process". CAUSE: If a transfer has started, and more data comes in, this message will occur. SOLUTION: Put a delay between file calls, to make sure ETU finishes it's processes before another file is called.
PROBLEM: “CPF0818 Value cannot be converted to type implied by receiver”. CAUSE: The value to be converted and the receiving field are different data types. SOLUTION: Change the contents of the field to be converted or the type of the receiver field, and then try the Change Variable (CHGVAR) command again. More information on data conversion in control language (CL) programs and proper formats of different constant types can be found in the CL Reference manual.
PROBLEM “SYS1301 Invalid Procedure Name” when running a System 36 OCL. Commands sent in the script work when sent from a command line. OCL is started from a batch file. CAUSE: When you execute the OCL procedure, ETU looks for a PC with ETU support, but instead it sees the System36 as the one that started the procedure and denies further action, causing your OCL to error out. SOLUTION: You can not start the OCL script from a batch file; it must be started interactively.
PROBLEM: ETU requires that a session be at the signon screen and not logged on in order to accept batch transfers to or from a *REQUESTOR. Users have a tendency log on any session that they see. SOLUTION: This solution, for Windows 2000 only, allows you to configure a session that will run in the background. As the Windows 2000 PC Administrator, use the Task Scheduler create a task using the browser to point to the first TVD.
Appendix F ASCII-EBCDIC PRINTABLE CHARACTERS ETU400 User Guide 011603 F-1
About This Appendix This appendix lists the ASCII and EBCDIC characters and their hexadecimal equivalents. Use this table when you create or modify an ETU translation table.
Dec 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 ETU400 User Guide 011603 Hex 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E OF 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 32 34 35 EBCDIC ASCII (space) ! " # $ % & ' ( ) * + , .
54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 ETU400 User Guide 011603 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6 7 8 9 : ; = (space) â ä à á å ç ñ ¢ .
109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 ETU400 User Guide 011603 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 _ > ? ø É ê ë è í î ï > ` : # @ ' = " ø a b c d e f g h i j k l m n o p q r s t u v w x y z
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 ETU400 User Guide 011603 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC v w x y z A B C D E F G H I J K L M N O P Q R F-6
221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 ETU400 User Guide 011603 DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF S T U V W X Y Z F-7
Appendix G System/36-mode Commands This appendix contains the commands used to emulate ETU36.
About This Appendix Some users of ETU/400 may be more familiar with the operating system of System/36 than with that of the AS/400. For this reason, ETU/400 supports a set of commands in System/36 mode, in addition to the native AS/400 commands. The commands that are supported in both the native mode and System/36 mode are listed in this chapter. Any native command can be used by a System/36-mode OCL procedure.
Starting ETU in System/36 Mode To use the Emulator Transfer Utility (ETU) in System/36-mode, follow these steps. 1. Start your emulation software on your micro. 2. Sign on to the AS/400 by entering your user I.D. and password 3. Start the System/36 mode on the AS/400. On the AS/400 commmand line, type: strs36 or designate *S36 on the user's profile in the special environment (SPCENV) parameter. 4. Access the ETU36 menu. On the AS/400 command line, type: menu etu36 The ETU System/36-mode menu displays.
Each menu option executes a ETU36 procedure: 1. executes the ALLOCATE procedure. 2. executes the RENAME procedure. 3. executes the DELETE procedure. 4. executes the TESTFILE procedure. 8. executes the XLT36FIL procedure. 9. executes the XLT36PRT procedure. 10. executes the XLTPCFIL procedure. 11. executes the XLTPCPRT procedure. 13. executes the FILETOPC procedure. 14. executes the LIBRTOPC procedure. 15. executes the PRNTTOPC procedure. 16. executes the FILEFRPC procedure. 17.
Running ETU in System/36 Mode Once you have signed on to the AS/400, you may execute an ETU procedure in the following ways: • Prompt an ETU procedure by selecting a menu item from the ETU36 menu. To display the ETU 36 menu, type: MENU ETU36, your ETU library name • Prompt an ETU procedure by entering “ETU36 procedure”, where procedure is the ETU procedure (such as ALLOCATE, FILETOPC, LIBRFRPC) to be executed. For example: etu36 allocate • Include in an OCL procedure.
ALLOCATE Procedure ETU36 ALLOCATE workstation file name The ALLOCATE procedure allocates a new file on the workstation. workstation file name ETU400 User Guide 011603 is the name of the workstation file to be allocated. For additional information, see “Workstation File Name” on page ____.
COMPILE Procedures The translation table functions are not provided in the S/36 mode. The native-mode translate tables provide the required support. If you execute the COMPILE procedure, it calls the native-mode ETU command EDITTABLE (used to compile the translate source member). See the EDITTABLE command in Chapter 10 for more information.
DELETE Procedure ETU DELETE workstation file name … notify NO YES The DELETE procedure deletes a file on the workstation. workstation file name The name of the workstation file to be deleted. For additional information, see “Workstation File Name” on page ____. notify Specifies whether you should be notified with a halt message if the workstation file is not found in the directory (optional). If NO is specified, the procedure continues without halting.
EDITABLE Procedure The translation table functions are not provided in the S/36 mode. The native-mode translate tables provide the required support. If you execute the EDITABLE function, it calls the native-mode ETU command STRSEU (used to edit the source member). See the STRSEU command in Chapter 10 for more information.
FILEFRPC Procedure ETU36 FILEFRPC, workstation file name , AS400 label, record len1 , T, 128 reformat *TEXT xlate file ATOE1 xlate size 1000 record len2 record len1 truncate YES NO ETU36 FILEFRPC, workstation file name , AS400 label, record len1 , T, 128 reformat *DIF *BASICS *TAB xlate file xlate size 1000 input specs , spec lib clilb ETU36 FILEFRPC, workstation file name , AS400 label, record len1 , T, 128 *SAVE *NONE The FILEFRPC procedure transfers a file from the workstation to the AS/400,
record len1 (optional) is the record length of the target AS/400 file (“AS/400 label”). This value defaults to 128. retain (optional) is the file retention (how long the file is to exist) for the translated “AS/400 label2”. Allowed values are T or J. Specifying T results in the file existing indefinitely (until specifically deleted), and specifying J will result in the file being automatically deleted at the end of the current AS/400 job. The default value is T.
record len2 (optional) is the record length of the translation work file. The default value is the record length of the target file (“record len1”). input specs is the name of the field definition member in user library “spec lib”. These are standard F and I (file/input) RPG specifications, defining the file and its fields. This member is required only for the field-oriented translation methods (*DIF, *BASICS, *TAB). See Chapter 5 for more information on creating the F and I RPG specifications.
FILETOPC Procedure ETU36 FILETOPC, AS/400 label, date , reformat , *TEXT xlate file , ETOA1 xlate size , record len 1000 128 , workstation file name ETU36 FILETOPC, AS/400 label, date , *DIF , xlate table , xlate size , input specs *BASICS 1000 *TAB spec lib , workstation file name clib ETU36 FILETOPC, AS/400 label, date , *SAVE *NONE , workstation file name The FILETOPC procedure transfers an AS/400 file from the AS/400 to the workstation specified, and optionally translates the file into a workstati
When using *SAVE to move executable programs between workstations, all necessary data (including Mac data and resource forks) is transferred. Data must have been previously transferred with the FILEFRPC procedure with reformat type *SAVE. xlat file (optional) is the translation table file. Translation file member ETOA1 is provided on the AS/400 distribution diskette and can be used to translate from the EBCDIC to the ASCII character set in variable length records.
LIBRFRPC Procedure ETU36 LIBRFROMPC, workstation file name , record len , 128 reformat , *TEXT xlate file , ETOA1 xlate size , record len2 1000 record len1 , truncate *YES *NO ------------------------------------------------------------------------*DIF , xlate table , xlate size , input specs *BASICS 1000 *TAB spec lib , workstation file name clib ------------------------------------------------------------------------*NONE lib name clib replace YES NO add ctl YES, member name NO member type P S fil
reformat (optional) specifies the type of data translation to take place on the AS/400 file. *TEXT (or *YES) the file is to be translated into an ASCII text format. *DIF the file is to be translated into a DIF format *BASICS the file is to be translated into a B BASIC Sequential format. *TAB the file is to be translated into a BASIC Sequential format with tab characters as the field delimiters. *NONE no translation of the file is to be performed (the default).
add ctl (optional) specifies whether or not (YES or NO respectively) to add $MAINT utility control statements into the work file before sending the member to the library. The default value is NO. member name if “add ctl” is YES, is the library member name of the workstation data when replaced in the library (lib name). member type (optional) if “add ctl” is YES, is the library member type to be created. Specify S for source and P for procedure. The default value is S.
LIBRTOPC Procedure ETU36 LIBRTOPC, member name, partall member name partial name, ALL ALL, record len 1 , file size 1000 reformat , *TEXT xlate file , ETOA1 *DIF *BASICS *TAB xlate table , , member type PROC LIBRARY SOURCE member lib clib remove ctl YES NO xlate size , record len2 1000 record len1 xlate size , input specs 1000 *none , , , , workstation file name The LIBRTOPC procedure transfers a AS/400 library member from the AS/400 to the workstation specified, optionally translating the file
record len1 (optional) is the record length of the library member(s) to be sent to the workstation. This parameter defaults to 96 if SOURCE is specified for “member type”, 120 if PROC or LIBRARY is specified, or 8 if LOAD or SUBR is specified. A record length of 8 creates a sector mode file, and 40 to 120 create record mode files. file size (optional) is the number of records in the temporary work file used in the translation process. The default value is 1000.
spec lib (optional) is the library containing the field definition member (“input specs”), and the translate table member (“xlat table”). If left blank, this parameter defaults to the current library. workstation file name is the name of the workstation file to receive the library members from the AS/400. For additional information, see “Workstation File Name” on page 4-2.
PRNTFRPC Procedure ETU36 PRNTFRPC, workstation file name forms id hold YES NO , ,,, #copies cpi , 10 15 , printer id lpi align 10 , YES 15 NO width 198 , 132 translate table ATOE3 The PRNTFRPC procedure transfers and translates a PC-DOS file and places it on the AS/400 print spool. Mac Users: Do not run this procedure. It is intended for use only with PC-DOS. workstation file name is the name of the workstation file to be transferred to the AS/400.
on the print spool until the operator releases it for printing. The default is NO. width (optional) specifies the width in columns of the file to be printed. Width may be 132 (the default) or 198. translate table (optional) specifies the name of the printer translation table you wish to use. The default is ATOE3.
PRNTTOPC Procedure ETU36 PRNTTOPC, function COPYPRT , spool name , xlat file ALL ETOA1 Fxxx Spoolid TRANSLATE, AS/400 label from window , 1 to window 132 , qualifier RELEASE CANCEL xlat file ETOA1 date file size 1000 file size 1000 , workstation file name The PRNTTOPC procedure translates and transfers print spool reports from the AS/400 to the workstation. Mac Users: Do not run this procedure. It is intended for use only with PC-DOS. procedure has possible values of COPYPRT or TRANSLATE.
file size (optional) is the number of records in the temporary work file used in the translation process. The default value is 1000. from window (optional) is the print column position of the report(s) on which to start translation. Any number from 1 to 198 is valid. The default value is 1. to window (optional) is the print column position of the report(s) on which to end translation. Any number from 1 to 198 (must be equal to or larger than the number specified in “from window”) is valid.
RENAME Function ETU36 RENAME, workstation file name ,,, new file name. The RENAME procedure changes the filename of a workstation file. workstation file name is the current name of the workstation file to be renamed. For additional information, see “Workstation File Name” on page 4-2.You may include the DOS pathname in the file specification (e.g., C:\TEST\MYFILE.TXT). If not specified, it defaults to the current default directory on your workstation.
TESTFILE Procedure ETU36 TESTFILE, workstation file name ,,, ida offset NOTIFY The TESTFILE procedure tests for the presence of the specified file and returns the number of bytes (characters) in the file. Depending on the “lda offset” parameter, the results of the test will be either given to the operator as a message, or placed in the Local Data Area (LDA) for later use by the programmer in determining the next step to process in the application program.
XLT36FIL Procedure ETU36 XLT36FIL, AS/400 label1, reformat *TEXT date , xlate file ETOA1 , AS/400 label2, retain J T , xlate size 1000 , record len 128 , xlate size , , , truncate YES NO *DIF , *BASICS *TAB xlat table input specs , 1000 spec lib clib The XLT36FIL procedure performs translation of a file residing on the AS/400 disk into a workstation data format. This procedure may be run from the job queue (with JOBQ), or released from the workstation (with EVOKE).
reformat (optional) specifies the type of data translation to take place on the AS/400 file. *TEXT (or *YES) *DIF *BASICS *TAB *NONE xlat file the file is to be translated into an ASCII text format. the file is to be translated into a DIF format. the file is to be translated into a BASIC Sequential format. the file is to be translated into a BASIC Sequential format with tab characters as the field delimiters. no translation of the file is to be performed(the default).
XLT36PRT Procedure ETU36 XLT36PRT, function COPYPRT spool name ALL Fxxx TRANSLATE, AS/400 label1, date1 , , AS/4oo label2, file size mode , qualifier RELEASE CANCEL CREATE 1000 ADD, date2 , , AS/4oo label2, from window 1 , , , retain, J T to window 132 The XLT36PRT procedure translates AS/400 print spool items into an AS/400 file in the workstation print format. function has possible values of COPYPRT or TRANSLATE.
mode (optional) specifies whether the target translation file is to be created by this procedure, or if an existing file is to be changed. Specify CREATE to create a new file with the name specified in the parameter “AS/400 label2”. Specify ADD to add the print reports to the existing file “AS/400 label2”. The default value is CREATE. AS/400 label2 is the label (name) of the file to receive the translated data.
XLTPCFIL Procedure ETU36 XLTPCFIL, AS/400 label1, reformat , *TEXT date , date , AS/400 label2, retain, J T , record len, 128 xlate file ATOE1 , xlate size 1000 , xlate size , input specs, 1000 truncate YES NO *DIF *BASICS *TAB , xlat file spec lib clib The XLTPCFIL procedure translates a previously transferred workstation data file into an AS/400 formatted data file. AS/400 label1 is the name of workstation data file residing on the AS/400 that is to be reformatted for the AS/400.
reformat (optional) specifies the type of data translation to take place on the AS/400 file. *TEXT (or *YES) *DIF *BASICS *TAB *NONE xlat file the file is to be translated into an ASCII text format. the file is to be translated into a DIF format. the file is to be translated into a BASIC Sequential format. the file is to be translated into a BASIC Sequential format with tab characters as the field delimiters. no translation of the file is to be performed (the default).
XLTPCPRT Procedure ETU36 XLTPCPRT, AS/400 label, forms id date , , cpi , 10 12 # copies lpi , 6 8 align YES NO , printer id , hold YES NO The XLTPCPRT procedure translates a PC-DOS file and places it on the AS/400 print spool. Mac Users: will occur. Do not run this procedure, as unpredictable results AS/400 label is the label (name) of the previously transferred workstation print file on the AS/400 disk to be translated into AS/400 print report and placed on the AS/400 print spool.
Appendix H INTERNATIONAL TRANSLATION TABLES ETU400 User Guide 011603 H-1
Installing International Translation Table NLynx Technologies now supports sixteen languages for the ETU/400 file transfer programs on the AS/400 host computer: Country Belgian French Canadian French Danish French German Italian Dutch Norwegian Portuguese Swiss French Swiss German Spanish Finnish Swedish U.K. English U.S. English ID BF CF DK FR GR IT NL NO PO SF SG SP SU SV UK US (default) If you are using a non-U.S. language on your AS/400, then you need to install the appropriate non-U.S.
Appendix I ETU Automation ETU400 Automation This section is intended as an explanation of the considerations that one must make when one is trying to automate file transfers using ETU400. It is usually easier to handle the function of automating the process on the AS/400 itself, vs. using PC macros. Interactive vs. Batch: Interactive means that the command strings are or appear to be typed in by a user. Batch means that the commands are sent by a utility that does not identify itself as a terminal.
job). The ETU power commands are PWRDELETEB, PCFROMPC, PCTOPC, PWRFROM3XB, PWRRENAMEB, and PWRTO3XB. AUTOMATION MECHANISMS When you are setting up an automated application on the AS/400 there are two mechanisms with which to do this. There are CL scripts (called OCL scripts on the System 36) and batch files. Batch commands are submitted to a job queue. The only batch commands that will work are the translation commands, and the power commands, as identified above. See SBMBATXFER, and SBMSCHJOB.
ETU commands: PWRFROM3XB, PWRTO3XB, PCFROMPC, and PCTOPC, as well as non-ETU commands that can be submitted to a batch. See page 9-21 and 10-47 of the ETU400 User Guide for specifics.
Appendix J ETU THROUGHPUT CONSIDERATIONS ETU400 User Guide 011603 J-1
ETU THROUGHPUT CONSIDERATIONS This is a guide to answer questions regarding throughput with ETU 400. The latest revision of ETU 400 is 5.02 for ETU 400 CISC and 5.04.1 for ETU 400 RISC. Use the ETUVER command to find what version you have. QUESTION: What kind of throughput can I expect? ANSWER: This would depend on several factors: The connection to the host, twinax or TCP/IP is the first factor. If the file requires translation from EBCDIC to ASCII it will add processing time.
QUESTION: What other options are there to ETU? ANSWER: FTP (such as File Transfer Protocol, using TCP/IP) or Client Access/400. QUESTION: What are the pros and cons of using FTP? ANSWER: FTP is fairly easy to use. FTP does not support EBCDIC to ASCII, or Comma Separated Values, Basic Sequential, or Differential translations. CSV is a comma delimited file where fields in a record is delimited by a comma (commas in the "data" must be quoted). FTP is supplied as part of the system on OS/400 and Windows 2000.
QUESTION: How would I use ETU400 and FTP? ANSWER: If you use ETU reasonably often and wish the file transfers quicker, for say files that are over 100,000 records, this is a way to do it. 1. Use ETU to only translate the file. Put the translated file in your private library. Don't use QTEMP. QTEMP exist only for the session that you are in. Does not work across sessions. If the file on the AS/400 is not a spool file, take option 20 at the main ETU menu.
GLOSSARY Allocate To create a file on the microcomputer. API Application Program Interface. The interface (calling conventions) by which an application program accesses operating system and other services. ASCII character set American Standard Code for Information Interchange. A standard set of characters used by microcomputers to represent data. See also EBCDIC character set. BASIC sequential format *BASICS. One of four micro file formats supported by ETU.
F&I Format and Input specifications. A means of creating internal file definitions on the AS/400. ETU supports F&I specs. host system The AS/400 computer and its peripherals. IBMTRAN An interface program for PCs that is included with ETU. It allows non-ES32 emulation packages to be used with ETU. interactive processing One of two ways of running jobs on the AS/400 (along with batch processing). A job that is run interactively begins being processed the instant it is executed from the workstation.
