These Release Notes are structured as follows:
This section provides a brief summary of the changes and enhancements that have been introduced in Com-plete Version 6.8.2.
Com-plete Version 6.8.2. is just a consolidation of fixes that were made during the lifetime of Com-plete Version 6.8.1. The functionality is identical with that of Version 6.8.1. with the latest fixpacks installed. The changes listed below were already described in the Readme.txt accompanying the Version 6.8.1. fixpacks.
In order for the Natural and the Natural Com-plete interface to work correctly in Com-plete Version 6.8.2, you must have the following zaps installed:
Version | Zaps |
---|---|
NCF 8.3 | NP06006, NP06007 |
NCF 9.2 | NP21001 |
Natural 8.2 | NA98083 |
Natural 9.1 | NA18083 |
Natural 9.2 | NA21005 (Might already be installed in the delivery kit) |
It is now possible to specify just the location of the ROLL buffer pool, while letting Com-plete do the calculation of the internal structure (subpools). This may be useful when you do not desire for Com-plete to build the ROLL buffer pool in 64-bit memory.
ROLL-BUFFERPOOL= [64BIT|31BIT|DS]
Com-plete used to write SYSOUT reports into the Com-plete spool first, and then these reports were transferred to JES in the background. This made Com-plete the owner of all reports, rather than the individual originating userIDs. Now SYSOUT reports are written to the JES spool directly bypassing the Com-plete spool.
Note:
When Com-plete detects an installation-specific non-RENT user
exit routine ULMSBTCH, then SYSOUT reports are handled like before.
This means, you can use ULMSBTCH to control how Com-plete handles SYSOUT reports. If you do have your own ULMSBTCH, and want all SYSOUT reports to be written to the JES spool directly, then make your ULMSBTCH RENT.
If you don't want SYSOUT reports to be written to the JES spool directly, then provide a non-RENT ULMSBTCH, different from the one delivered by Software AG in the Com-plete 6.8 load library.
For example, take the provided sample source module, change
something, and assemble it. With APPLYMOD=85
all reports are
routed to JES, forwarding the printer name.
A new system parameter has been introduced in order to be able
to avoid using large pages (1M): LARGEPAGES=NO
. The new parameter
applies to ROLL buffer pool as well.
The utilities UEDIT and UPDS accept syntax MEMBER-N for access to relative generation N.
When browsing a generations-enabled PDSE-2 directory via web UI, the member tool box now contains the link "Show member generations". In order to display the member tool box, click any empty space in the table row.
PDSE-2 libraries can be allocated from within the web UI "Find data sets" function:
Click an empty part of line.
Select Tools.
Click on Allocate similar data set.
Com-plete (both UQ-M and the HTTP console) now use either OPERLOG when present or SYSLOG as the source for system messages. If you are still running a CONSOLE server in your Com-plete, you must remove it.
The new system parameter OPERLOG=NO
avoids attempts
to open OPERLOG and forces UQ-M and the HTTP console to always use SYSLOG.
A C/C++ main() program can now receive arguments when invoked from the ComPass command line.
myprog arg1 arg2
Results in .
arg[0] *MYPROG arg[1] arg1 arg[2] arg2
Note:
All strings are upper-cased unless APPLYMOD=37
is set, and the individual ComPass case setting is set to LOWER
.
Specify the new option SMFRECORDS=1W
to write a
record at the time of every terminal-WRITE operation. In contrast,
SMFRECORDS=1T
writes a record not per transaction, but per
roll-out. This results in way too many records.
The input string from the ComPass command line or FETCH / ATTACH
can now be passed to the LINKAGE SECTION of a COBOL MAIN program like
*PROGRAM
parms. For compatibility reasons,
APPLYMOD=49
must be set to enable this option.
In the web UI under Monitoring, a new function
Running transactions has been added. This function
shows all transactions running for more than one second at the time being,
indicating many details and providing a CANCEL
link for every
transaction running for more than 5 seconds.
The new parameter
MAXPARALLEL=n
limits the maximum number
of connections per client. The default value is 9.
While major browsers normally use no more than 4 parallel connections per server, there are configurable and home-grown HTTP clients out there. These can easily open hundreds and more connections in a very short time, leading to resource shortages in Com-plete.
For requests like /natcgi/lib/pgm
the server now
starts Natural with the parameter STACK(LOGON lib;HNANSHEL)
.
Specify NATLOGON=no
if you wish to avoid LOGON lib
.
You can view all available Software AG product versions and check the dates when their maintenance ends by using the System Requirements App at:
https://documentation.softwareag.com/systemrequirements/#/
Here, you can enter the product name or code in the search field and see the latest information on system requirements and product availability.