IND$FILE Plus Modernization Guide

IND$FILE Plus facilitated file transfers between z/OS systems and personal computers using a 3270 emulator. It extended the capabilities of IBM's IND$FILE with features like compression and batch processing.

IND$FILE Plus offered features beyond IBM's IND$FILE, including data compression to speed up transfers, a batch interface for automated transfers, auditing capabilities for tracking file activity, and filtering to transfer only specific portions of a file.

The product was acquired by Proginet from Novell in 1994. Novell obtained an equity stake in Proginet at the time of the acquisition.

While specific command details are unavailable, IND$FILE Plus likely used commands similar to IBM's IND$FILE for initiating file transfer send and receive operations. Configuration likely involved setting up communication parameters within the 3270 emulator environment.

Details on specific APIs are unavailable. Given its age and function, IND$FILE Plus likely did not expose modern APIs like REST or SOAP. Communication would have relied on protocols inherent to the 3270 environment, such as SNA.

Specific architectural details are unavailable. The system likely involved a z/OS component for server-side processing and a PC-based component integrated with a 3270 emulator. Communication would occur through the 3270 data stream.

IND$FILE Plus provided value by enabling file transfer between mainframe systems and personal computers, facilitating data exchange for applications running on both platforms. The compression feature improved transfer speeds, and the batch interface automated repetitive tasks.

The audit functionality allowed organizations to track file transfer activity for compliance and security purposes. The filtering capability enabled users to transfer only relevant data subsets, reducing transfer times and storage requirements.

Security in IND$FILE Plus likely relied on the security features of the 3270 environment and the underlying z/OS system. Specific authentication methods are unavailable, but likely included user IDs and passwords validated against z/OS security systems.

Given the product's age, advanced encryption methods were likely not implemented. Security focused on access control within the z/OS environment and potentially basic data obfuscation during transfer.

The audit/logging capabilities provided a record of file transfer activities, aiding in security monitoring and compliance efforts. These logs could be analyzed to detect unauthorized transfers or data breaches.

Administrative interfaces are unavailable, but administration likely involved configuring parameters within the 3270 emulator and managing user access through z/OS security tools. Monitoring relied on analyzing the audit logs generated by the system.

User management was handled through the z/OS security system (e.g., RACF, ACF2, Top Secret). Configuration parameters likely included settings for communication protocols, data compression, and audit logging.