An IBM i Access Client Solutions (ACS) HOD file is a configuration file used within the IBM i Access Client Solutions software, which is a Java-based, platform-independent client for connecting to and managing IBM i (formerly AS/400) systems. ACS provides tools like 5250 terminal emulation (for green-screen interfaces), data transfer, SQL scripting, and more, replacing older products like IBM i Access for Windows and Client Access for Windows.
Key Details About HOD Files
- File Extension and Format: HOD files use the .hod extension. They are essentially text-based profile files that store settings for a 5250 emulator session, such as connection details (e.g., host IP address, port, and SSL options), display preferences, keyboard mappings, macros, and session-specific behaviors. This makes them portable and reusable across different machines and/or users.
- Session Profiles: When you create or save a 5250 emulator session in ACS (via the 5250 Session Manager or directly in the emulator), the settings are saved as a HOD file. Double-clicking an HOD file launches the ACS emulator and automatically loads the configured session, allowing quick reconnection to an IBM i system without re-entering details.
- Batch Sessions: Related to HOD files, batch emulation profiles (saved as .bchx files) can reference multiple HOD sessions for running several emulators simultaneously.
- Command-Line Launching: HOD files can be invoked directly from the command line. For example, on Windows, you might run acslaunch_win-64.exe system_example.hod to start the emulator with the specified profile. This is useful for automation or scripting.
- File Associations: ACS supports associating HOD files with the application, so double-clicking them in Windows Explorer (or equivalent on Linux/Mac) automatically opens them in the emulator. This association can be set up during installation or manually via system settings. Common issues, like after Windows updates, may require re-associating the file type.
- Migration from Older Formats: If you're upgrading from legacy IBM i Access for Windows (which used Personal Communications emulator), old .ws (single session) or .bch (batch) files can be imported and converted to HOD (or .bchx) files using the ACS 5250 Session Manager's "File > Import" feature. This ensures compatibility while leveraging ACS's modern features.
- Storage Location: HOD files are typically saved in a user-specific directory, such as %USERPROFILE%\Documents\IBM\iAccessClient\Emulator\ on Windows, or equivalent paths on Linux/Mac. They can be shared or deployed (e.g., via enterprise tools like SCCM or PDQ Deploy) for standardized connections across an organization.
HOD Files aren't the only config files used by ACS. They are part of a broader set of supported extensions for quick launching:
- .dtfx Data transfer download requests.
- .dttx Data transfer upload requests.
- .sql SQL script files.
- .bchx Batch emulation profiles.
HOD files enhance productivity by encapsulating complex session setups into simple, shareable files, reducing the need to recreate configurations repeatedly.
HOD files enhance productivity by encapsulating complex session setups into simple, shareable files, reducing the need to recreate configurations repeatedly.
What does a HOD File looks like?
The main elements most users will want to setup are the screen name (WorkstationID) and the Screen resolution (27x132 or the older 24x80)
Where is this configuration stored?
You can save your HOD file anywhere - but the default location is %USERPROFILE%\Documents\IBM\iAccessClient\Emulator\
For example, I like to store all my configs in ONEDRIVE so I keep all my HOD files for ACS in a common shared location. This means that if I make changes they are automagically reflected to my various desktops & laptops seamlessly. I keep mine in C:\Users\nicklitten\OneDrive\Documents\IBM\iAccessClient\Emulator
I have several HOD files - one for each machine that I connect to:
For the example above - naming the device PROJEX*= means that IBM i will automatically create a new PROJEXsomething device for each new signon session I start. The initial device will be PROJEXA0 (note device names can be a maximum of 10 characters just like all other objects within the IBM i OS)
Look at my HOD file for this machine - in the [Terminal] section you can see the setting for workstationID=PROJEX*= which instructs ACS to connect with PROJEXA0 first. If that is in use it will try with PROJEXB0, then PROJEXC0 all the way to PROJEXZ0.. if still unable to connect because they are in use, it tries again with PROJEXA1, B1, and so... This allows communication and signon without clashing terminal/workstation names:
When I first connect, I can see one device has been created:
If I signon to more sessions (using FILE > NEW TAB) then multiple signon sessions aka WORKSTATIONS will be created following the same PROJEXsomething rule.
Let's fire up 4 new signon sessions:
Recommendations for HOD config
- Use Workstation name that are 1-8 characters and always add *= to end to allow more to be automatically created
- Always select 27x132 screen size -- why on earth isn't this a default?
- On the ADVANCED tab -- use BYPASS SIGNON to allow the user to automatically signon once the user has been validated upon connection (why enter user/password twice?)
- Use TAB COLOURS to highlight different systems
- Use the BACKGROUND COLOUR or WATERMARK to clearly show which system you are connected to
