…looking to discover an IBM z/OS-powered mainframe? Click here for the z/OS docs page, instead.
IBM i/AS400 Discovery Updates
Device42 has enhanced i/AS400 discovery with additional capabilities and device results.
- FTP support – this allows Device42 to pull in additional discovery details and no longer rely on the Telnet method of discovery.
- Software discovery – this supports all licensed software that IBM registers as installed, and if you use FTP-based discovery, it includes software versions as well. This encompasses different programming languages installed, datastore information, and additional dependencies or tools installed.
- Disk Space discovery – gets the ASPs (Auxiliary Storage Pools) of the machine (capacity and space used) and stores the disk information as mount points attached to the device.
- Tape Drives discovery – these now come in as mount points with tape drive name and model number.
- Lines of code on the machine discovery – the total lines of code, including system files and user files. This information is stored in the extra fields DOQL view in Device42. (Note that this can increase discovery time depending on the number of lines of code.)
- Improved Service Port collection – to match services to specific jobs on the machine.
Creating an IBM i/AS400 [mid-range] Discovery Job
To add a new IBM i/AS400 discovery job, head to the main menu and select Discovery > HyperVisors / *nix / Windows. Create a new discovery job, selecting IBM i/AS400 as your ‘Platform’:
*Note: Please do not set up an auto-discovery / scan using critical [production] account credentials! Please create a separate, dedicated account to use only for discovery.* Doing so, depending on permissions granted & configured password policies could result in account lock-out, therefore causing an otherwise completely avoidable outage.
IBM System i/AS400 Discovery Options
Job name A name of your choosing to identify your IBM i/AS400 auto-discovery job
Remote Collector: Optionally specify a remote collector from which to run discovery [instead of from the main appliance]
Platform: Select “IBM i/AS400”
Discovery Target(s): Specify the FQDN or IP address of the IBM i/AS400 to discover. If using FQDN, ensure Device42 is setup to resolve DNS (VM console, option 1)
Port: IBM i/AS400 discovery uses port 23 by default. Only change if you have configured a custom listening port configuration.
Username & password: Specify a username with permissions on your IBM i / AS 400
Debug Level: Turn debug on for extra troubleshooting output – useful for support tickets.
ADM Sampling Interval: Off or interval in minutes or hours.
Discover Using FTP: Run the discovery through FTP instead of Telnet.
Timeout: The maximum time in seconds per command when performing a Telnet discovery. If there are connection issues or slow loading time, increasing the Timeout may yield better results.
Last Job Status: Displays the status of the last discovery or task run.
Job Run Report: This will record what has changed in the last task.
Schedule for auto-discovery: You can schedule the discovery job to run automatically.
Discover Lines of Code: If selected under the Software and Applications section, this will run a script to collect the total lines of code on the machine. If used, we recommend increasing the max timeout of the discovery to 5 minutes or more.
i/AS400 FTP Discovery
How it works:
- Using FTP, D42 creates a directory on the targeted server named D42TEST.
- D42 then uploads our CL/RPG Programs to the server, transfer them to the QTEMP folder, and run them.
- After that has completed, D42 transfers the output files back to D42TEST and parses them on the remote collector.
- Finally, D42 removes all files placed or created on the server and disconnects.
Advantages over Telnet Discovery:
- FTP does not rely on anything other than the permissions to place/delete files. With Telnet, customization could disrupt the flow and end the discovery.
- Less total communication with the server. This can result in much faster run times if there is any slowness on the targeted server or the network.
FTP Discovery Notes:
Due to limitations, D42 discovery needs to be able to create the directory D42TEST. Only the items that were placed or created during discovery will be removed – this means that if an unexpected file is in that directory, the discovery will most likely fail. If this is the case, please work with your AS400 Server administrator to remove the directory.
Setting IBM i / AS400 Permissions
IBMi/AS400 permissions requirements are configured via the following command. Have your AS400 admin run the following:
CRTUSRPRF USRPRF($USERNAME$) PASSWORD($YOURPASSWORD$) USRCLS(*SECOFR) SPCAUT(*ALLOBJ *JOBCTL)
In the above IBM i / AS400 command:
$USERNAME$ = The chosen profile name being set. Substitute ‘$USERNAME$’ in the above command with the profile name of your choice.
$YOURPASSWORD$ = The password you are setting. Substitute ‘$YOURPASSWORD$’ with a strong password of your choosing.
Note: In USRCLS(*SECOFR) = [*SECOFR] may be substituted with [*USER] or [*PGMR] if desired – however, if you choose [*USER], this option will prevent software from being discovered. For complete discovery access, choose an option higher than [*USER].
- For Telnet discovery, please ensure that the created user has the default initial menu (MAIN). Customized menus may cause issues when running the discovery.
AS400 Auto-discovery Details
What information does discovery gather on the AS/400 midrange compute platform?
- Hardware Inventory – including hostname(s), IP & MAC addresses, hardware specifications, OS information
- Service connections
Sample IBMi/AS400 discovery output:
AS400 support does not currently include:
- Individual application discovery
- Parts support
Note on AS/400 Discovery: AS400 discovery has been verified and functionality tested with IBM i / AS400 operating system deployments configured with the Spanish language setting as of Device42 v15.10.00. AS/400 discovery should also work with other non-English locale configurations. Please let us know about your experiences with other foreign language configurations or any issues you encounter; we love hearing from our users – email firstname.lastname@example.org