29
Fri, Nov
0 New Articles
  1. You are here:  
  2. Home
  3. IT Infrastructure
  4. IT Infrastructure - Other
  5. General
  6. The One AS/400 FTP Command You Must Understand

The One AS/400 FTP Command You Must Understand

Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

If you’re using FTP to exchange files with an AS/400, you must understand the AS/400- specific Select File Naming Format (NAMEFMT) FTP command. Executed with a parameter of 0 or 1, NAMEFMT is a command that controls whether your FTP client session can access file systems on an AS/400 Integrated File System (AS/400 IFS) besides your DB2/400 data. NAMEFMT can be set on either an AS/400 FTP client or server
and—in addition to providing or denying access to AS/400 IFS file systems—it affects how you code AS/400 path names to AS/400 IFS files you want to transfer.

In this article, I’m going to take a quick look at how you use NAMEFMT to facilitate FTP transfers to and from an AS/400. I’ll look at the different parameters you use with NAMEFMT and how they affect your pathname coding in other FTP commands (such as GET, PUT, CD, and LCD).

Using NAMEFMT in an FTP Session

Here are some examples to give you a feel for how NAMEFMT is used and what it provides.

If I start an FTP session to an AS/400, I could run NAMEFMT in the following formats inside my AS/400-centric FTP session:

• NAMEFMT 0 (to change the naming convention on my FTP client and limit FTP access to DB2/400 files only, if that client is an AS/400)

• QUOTE SITE NAMEFMT 0 (to change the naming convention on the AS/400 FTP server I am attached to and to limit FTP access to DB2/400 files on that AS/400)

These commands tell an AS/400 to use a naming format that assumes I am transferring files to and from the DB2/400 file system (the QSYS.LIB file system in the AS/400 IFS). With NAMEFMT 0, I cannot perform file transfers from any other AS/400 IFS file system except QSYS.LIB. So this effectively cuts off my access to the Root (/), QOpenSys, QDLS, and the other AS/400 IFS file systems. It also affects the way I specify my AS/400 working directories or libraries in my other FTP commands. When NAMEFMT 0 is specified, I must use the following pathname naming convention in my FTP command when I am referencing AS/400 QSYS.LIB libraries, files, and members:

[libname/]filename.membername


To execute an FTP GET statement to retrieve member JOE from file SOURCE in library HERTVIK to my current local directory, I would issue the command as follows:

GET HERTVIK/SOURCE.JOE

The pathname syntax would also be the same for the MGET, GET, MPUT, CD, LCD, and any other FTP command that uses a pathname as part of its command line. Because I am only dealing with DB2/400 files when NAMEFMT = 0, I only specify which library, file, and member names I am using. Nothing else is needed or accepted by OS/400.

Now, if I want to work with AS/400 files that reside in another AS/400 IFS file system besides QSYS.LIB, I would first execute NAMEFMT in the following formats in my FTP session:

• NAMEFMT 1 (to change the naming convention and AS/400 IFS file access on my FTP client, if that client is an AS/400)

• QUOTE SITE NAMEFMT 1 (to change the naming convention and AS/400 IFS file access on an AS/400 FTP server I am attached to)

These commands tell OS/400 that my client can access files in any AS/400 IFS file system (such as Root, QOpenSys, and QDLS). It allows me to access any file residing on my AS/400, provided I have the proper security to that file. However, when NAMEFMT = 1, I must change the pathname naming convention for referencing a folder or file on the AS/400 IFS to the following:

• /QSYS.LIB/libraryname.lib/filename.file/membername.mbr—when dealing with objects in the QSYS.LIB file system

• /filesystem/directoryname/filename.extension—when dealing with non- QSYS.LIB file systems. There may be slight variations for this format if you are FTPing a file from an Optical file system (QOPT, where you have to specify the volume name before the directory name) or for file systems where the directory name may also contain an extension. But this is the main format for non-QSYS.LIB transfers.

So, using the NAMEFMT 1 convention, I would change my previous GET command to the following syntax:

GET /QSYS.LIB/HERTVIK.LIB/SOURCE.FILE/JOE.MBR

Again, this syntax would be the same for any other FTP command that uses pathnames. I need to be more literal here because OS/400 is now allowing me to access any AS/400 IFS file system, not just QSYS.LIB. For non-QSYS.LIB file systems, the naming convention is different, based on the convention shown above. For example, if I’m loading some HTML files to an AS/400 IFS folder called HERTVIK under the Root (/) file system, I could change the directory on my host server AS/400 to this directory by issuing the following Change Remote Working Directory (CD) command:

CD /HERTVIK

If HERTVIK were contained under the QDLS file system (where OS/400 stores the old Client Access Shared Folder files), I would change the command to the following:

CD /QDLS/HERTVIK

So now, for any FTP command in which I need to specify a folder or a specific file path to my non-QSYS.LIB AS/400 IFS, I would code those paths using this convention.

Getting Help

If you want more information on what naming convention to use with your particular NAMEFMT settings, you can use the FTP help command when you’re running your FTP


session. If your FTP client is an AS/400, you can access IBM’s local help text for the NAMEFMT command by typing in the following FTP command:

HELP NAMEFMT

If your FTP client is not an AS/400-based machine, you can retrieve your current NAMEFMT settings and pathname configuration off your AS/400 FTP server by typing in the HELP command in the following way:

QUOTE HELP NAMEFMT

You can also find additional information on using NAMEFMT at the online AS/400 Information Center (publib.boulder.ibm. com/pubs/html/as400/infocenter.htm). Once you enter the Information Center, click on the following path to retrieve information about the NAMEFMT command: Main/TCP/IP/ Transferring files (FTP)/File systems and naming conventions supported by FTP/Specifying the format of file names.

A Few “Gotchas”

When working with NAMEFMT, I find it’s very important not to assume anything about what your NAMEFMT values are set at. For example, if I’m conducting an FTP session between two AS/400s, I can verify the NAMEFMT settings on both AS/400s by issuing the NAMEFMT command without any parameters, as follows:

NAMEFMT

This command displays the NAMEFMT setting for each machine if both machines are AS/400s. If my FTP host machine is an AS/400 and my FTP client machine is running on another operating system (such as Windows 95 or UNIX), I can check the status of the AS/400 NAMEFMT value by issuing the NAMEFMT command as follows:

QUOTE SITE NAMEFMT

For AS/400-AS/400 communications, if I want to change NAMEFMT to 1, I can type in the NAMEFMT 1 command and OS/400 may change the settings on both machines. However, it’s usually best to explicitly change those setting on each machine by issuing the command to both your local FTP client and your remote FTP server. (Remember, this can be done by executing both the NAMEFMT 1 and QUOTE SITE NAMEFMT 1 commands in your FTP session or in your FTP script.) Even if you want to use NAMEFMT 0 on both your AS/400s, you may still want to issue the NAMEFMT command for both machines just to ensure your transfer works properly.

Now You Know

By understanding how the NAMEFMT command affects your FTP sessions to your AS/400, you are now armed with the knowledge you need to efficiently use FTP to transfer files between AS/400s or between an AS/400 and the outside world. Knowing what NAMEFMT does is the key to understanding how to manipulate an FTP session involving an AS/400.

References

“Specifying the format of file names,” IBM AS/400 Information Center, publib.boulder.ibm.com/pubs/html/as400/ infocenter.htm


Related Materials

“Setting Up Windows NT to FTP to the AS/400,” John P. Lyons, AS/400 Network Expert, September/October 1999
“Advice: Client Access Data Transfer vs. FTP: When to Use Each Technique,” Joe Hertvik, AS/400 Network Expert, July/August 1999
“How to Create Blazing FTP File Transfers,” Daniel Wood, AS/400 Network Expert, March/April 1999


BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More 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.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY 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.

  • SB HelpSystems ROBOT GenericForms 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.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA 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:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA 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.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra 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: