|
|
pcMAINFRAME - Release Notes
What's new in pcMAINFRAME 5.01
pcMAINFRAME Version
5.01
New Features - Mainframe
Host Initiated Transfer (CFXINIT) enhancements:
- Bulk Data UPLOAD is now supported.
- Upload/Download of multiple files in a single step is supported.
- For VSE, user defined DLBL names, standard SYSLST and SYSRDR assignments and BLKSIZE=MAX are supported.
Improved default processing during profile maintenance, output format screen definition, as follows:
- When processing WKS, XCEL and DBF formats, the PC field length and data types will be defaulted to the characteristics of the mainframe field.
- Operation will always default to MOVE.
To improve performance, library member delete during file transfer (PCMX) and ONLINE maintenance (PCMM) has been changed to use the generic delete request.
To improve transfer performance, the default read/rewrite logic for uploading to a KSDS file has been changed to WRITE command. If DUPREC condition occurs, pcMAINFRAME will READ for update and REWRITE.
During Multiple Record Header definition, a record hierarchy (parent-child) can be specified. During download, the hierarchy is used to limit record selection as follows:
- No CHILD will be downloaded if his PARENT has not been selected.
- Optionally, a PARENT will not be downloaded if NO child is selected.
A new User Exit, CFXBIMX, allows access to BIMEDIT datasets and VSE sublibraries.
During Multiple File access definitions, a new "not found" rule has been added to allow
the user to define the action to take if a record on the secondary file is not found.
- If action = "TERMINATE", pcMAINFRAME will interrupt the transfer as soon as a not-
found condition is encountered. This is the default action.
- If action = "SKIP", pcMAINFRAME will skip (not select) the record being processed. The transfer will continue with the NEXT record.
- If action = "CONTINUE", pcMAINFRAME will continue the download as if the record were found. All fields referencing the 'not found' record will be downloaded as spaces or zeros.
Uploads to empty VSAM KSDS files during TSO transfers are now permitted.
Library Utility (CFXLIBU) enhancements - The following enhancements have been made to CFXLIBU processing:
- A member can be added to an empty library.
- For VSE users, standard SYSLST and SYSRDR assignments are now supported. The "ASSIGN SYSLST, SYSRDR" statements are not needed.
New Features - PC
The maximum length of variables in the setup file has been increased to 64 bytes.
&MAINRC is now cleared after each request in MANUAL mode.
The following new parameters for Protocol Converters are supported:
- Hardware flow control.
- 14.4 and 28.8 baud rates.
The following WINDOWS only enhancements have been made.
- Run minimized is now fully supported.
- A Return-Code is set at the end of processing. This will allow DIALOGG to test ERRORLEVEL after completion of MAINW.
- A new control file, CFXATB.INI can now be used to control some communication options and driver/configuration file access.
New Device Support for pcMAINFRAME for Windows
- Extra! For NT
- TELNET VT220 WIN32 (win32Sockets)
- VT200 WOW async
- 5250 - IRMA 5250 for Windows
- 5250 - Rumba 5250 HLLAPI for Windows
- 5250 - Windows WOSA HLLAPI 5250
- Rumba LU6.2 for Windows
- WinAPPC LU6.2
- WinCPIC LU6.2
New Device Support for OS/2
- TELNET VT220 IBM TCP/IP/OS/2
- TELNET VT220 FTP/PC/TCP/OS/2
- TELNET VT220 Novell LWP/OS/2
- OS/2 Communications Manager LU6.2
- OS/2 Communications Manager 5250
Corrections:
- Variables defined in the source field of a multiple file key definition screen were being improperly resolved.
- The numeric range check for insert of packed data did not accept 0. (Output Format Screen)
- If the PAD exit parm for CFXPOWEX was defined as Character, CFXPOWEX
ABENDed with an ASRA.
- If "STOP WHEN" record selection or processing was interrupted during a USER EXIT with record buffering, the exit was not called with a CLOSE. For CFXPOWEX, this caused the SAS task to remain open.
- PCMM profile and library directory functions did not work if security class is zero.
- In Windows manual mode, the specification of a library member was ignored. The PC file name was always used to develop the member name.
|