i talk to other servers. No, it's not a typo. This TechTip series will get your System i talking to other servers.
Back in the old days, when our server was called AS/400, there were few or even no "satellite systems" like PC servers that needed to pass and/or receive data from it. Nowadays, it's a totally different landscape: the i sits together with a broad scope of servers and devices with which it has to communicate, passing and receiving data. These interfaces are, at times, manual data imports or exports performed by operators via boring and repetitive procedures.
This TechTip series suggests a few ways to automate these procedures using FTP, ODBC, and WebSphere MQ. It doesn't intend to set a standard, just to get you thinking about your own IT landscape and interfacing needs. Hopefully, you'll find here the answers to some of your problems regarding i data import/export.
Automate Data Transfers Using FTP
Let's start with the basics: one of the most commonly used procedures to transfer data to and from the System i is FTP. I won't go into detail in this article, but there are some points worth mentioning. First of all, I'll always be referring to FTP started on a Windows PC. This may sound strange, but since Windows is (still) one of the most-used file servers and desktop OSes out there, I think it makes sense.
You can start an FTP session via a command line and use it interactively to transfer data. That's part of the boring procedure mentioned earlier. This first TechTip is on how to automate the data transfer. By using a batch file to invoke the FTP command and a script file to perform the data transfer actions, you avoid typing the same thing over and over.
FTP has some options to perform batch transfers. Let's start with option –n. This option tells the FTP command not to ask for the user name and password when the FTP session is initiated. Then, in order to run the transfer, you need to use a script file (which will contain the commands to perform) and tell the FTP where it's located. This is done using the option –s:<script file name>. Finally, you have to indicate the target system name. So your batch file should look a bit like this:
@echo Transferring file
@echo Off
ftp -n -s:U:ScriptsMyScript.scp MYSystemi
U:ScriptsMyScript.scp indicates the name and location of the script, and MySystemi indicates the target system name.
Of course, this is usually not that simple. You will probably need to change to the proper folder or rename the file to be transferred (or perform some other actions using DOS commands). You can use entry parameters to your batch file to achieve that. Here's another example:
@echo Transferring file %1
@echo Off
H:
CD
rename %1 myfile.txt
ftp -n -s:U:ScriptsMyScript.scp MYSystemi
This batch file will change to path H:, rename the entry parameter (%1) file name to myfile.txt, and execute the myscript.scp that resides on U:Scripts on system MySystemi.
The use of entry parameters on the batch file is especially useful because you cannot pass parameters into the script file; it's a kind of black box of commands to execute, without any flexibility.
Finally, let's see how the script file is composed.
Since we're using the –n option, which removes the prompt for user name and password, the first command of any script should always be the login:
User username password logs you into your system.
Keep in mind that doing this is a security risk: you're storing a user name and password on a text file, somewhere on a file system! You might want to create a user profile for a user who isn't allowed to sign on interactively to your System i and who has limited authorities (for instance, only has access to the IFS folder/library where the user gets or puts the files to be transferred).
After the login, you'll have to indicate the commands to be executed. These are standard FTP commands, like cd, lcd, put, get, and so on. Again, keep in mind that the script doesn't have any flexibility, so you have to use fixed directories and IFS folders/libraries on the data transfers. Here's an example of a complete script file:
user myuser mypassword
cd /textfiledir
put myfile.txt
quit
Note that FTP is case-sensitive, so be sure to type all commands in lowercase. This script, together with the batch file mentioned before, transfers the file indicated when you invoke the batch file to the IFS folder /textfiledir under the name myfile.txt. For example, imagine that your batch file is named mybatch.bat. If you type the following on a command line, you'll be transferring file h:inventory.txt to the IFS folder extfiledir under the name myfile.txt.
Mybatch.bat inventory.txt
In the second part of this series, we will explore how to automate the transfer of a file received via email on a Lotus Domino mail server.
Rafael Victória-Pereira has more than 20 years of IBM i experience as a programmer, analyst, and manager. Over that period, he has been an active voice in the IBM i community, encouraging and helping programmers transition to ILE and free-format RPG. Rafael has written more than 100 technical articles about topics ranging from interfaces (the topic for his first book, Flexible Input, Dazzling Output with IBM i) to modern RPG and SQL in his popular RPG Academy and SQL 101 series on mcpressonline.com and in his books Evolve Your RPG Coding and SQL for IBM i: A Database Modernization Guide. Rafael writes in an easy-to-read, practical style that is highly popular with his audience of IBM technology professionals.
Rafael is the Deputy IT Director - Infrastructures and Services at the Luis Simões Group in Portugal. His areas of expertise include programming in the IBM i native languages (RPG, CL, and DB2 SQL) and in "modern" programming languages, such as Java, C#, and Python, as well as project management and consultancy.
MC Press books written by Rafael Victória-Pereira available now on the MC Press Bookstore.
 |
||
 |
|
Evolve Your RPG Coding: Move from OPM to ILE...and Beyond Transition to modern RPG programming with this step-by-step guide through ILE and free-format RPG, SQL, and modernization techniques. List Price $79.95 Now On Sale
|
|
||
 |
|
Flexible Input, Dazzling Output with IBM i Uncover easier, more flexible ways to get data into your system, plus some methods for exporting and presenting the vital business data it contains. List Price $79.95
Now On Sale
|
|
||
 |
|
SQL for IBM i: A Database Modernization Guide Learn how to use SQL’s capabilities to modernize and enhance your IBM i database. List Price $79.95
Now On Sale
|
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online