| |
Results |
|
XML Yellow COBOL copybooks for ZMF 8.2 Patch 2
|
Caution: Yellow services are intended for use by Professional Services and customers with detailed knowledge of the ZMF meta data. Yellow services are intermediate services which provide access to CREATE, UPDATE, and some DELETE functions. Careful design and testing should be conducted to ensure your implementation of a yellow service functions as intended, and does not harm the integrity of the ZMF meta data.
|
|
|
|
XML Yellow COBOL copybooks for ZMF 8.2 Patch 3
|
Caution: Yellow services are intended for use by Professional Services and customers with detailed knowledge of the ZMF meta data. Yellow services are intermediate services which provide access to CREATE, UPDATE, and some DELETE functions. Careful design and testing should be conducted to ensure your implementation of a yellow service functions as intended, and does not harm the integrity of the ZMF meta data.
|
|
|
|
Unexplained SYNCH10! errors auditing some copybook components in participating packages
|
ChangeMan ZMF 8.2 Patch 2
|
|
|
|
Package audit mis-reporting created date century for old copybook components
|
ChangeMan ZMF 8.2 Patch 2
|
|
|
|
New Features in ChangeMan ZMF 8.2 Patch 1
|
The CMNBAQ00 utility program extracts these copybooks from the SYSLIB concatenation. In addition, for impact analysis purposes, CMNBAQ00 now establishes a source-to-copy relationship between these two copybooks and the like-SRC parm
|
|
|
|
SERLCSEC exit should not require SYSPARM(??????) in order to assemble it.
|
In ZMF 8.2 Patch 2 a change was made to SERLCSEC to remove copybook SER$SETC. This change means you no longer need use the parameter ‘SYSPARM(xxxxxx)’ when assembling SERLCSEC. The ZMF
|
|
|
|
Impact analysis table relationship refers to incorrect subcomponent (copybook) library type
|
... a number of copybooks from existing libtype CP 2 (each has ... months ago they baselined a package where one of the existing CP1 copybooks was staged (S1'd) into the package as a CP 2 and a calling SRC also changed in the same package. ... CMNWRITE output metadata in the package is all accurate and correctly shows the relationship generated to the CP 2 component. ... at the IA table, the relationship for the two components there is still pointing to the CP1 copybook . ... Problem reported running 8.2 Patch 3.
|
|
|
|
‘SER8500E FILE service not found for product CMN’ when using XMLCFIL* COBOL copybooks
|
|
|
CMNAS000 and CMNDB2TM processing nested copybooks inconsistently
|
Fixed in ZMF 5.6.3. Fixed in ZMF 6.1.0.
|
|
|
Serena® ChangeMan® ZMF Patch Release 6.1.1.01 Readme File Last Updated on 2 December 2009
|
9.2 Installing ChangeMan ZMF 6.1.1 Maintenance Release Several copybooks for exit programs are changed in the CMNZMF.ASMCPY library. If you have customized the exit programs in the CMNZMF.ASMSRC library that use these copybooks, you must assemble the exits, even if you do not change your customization in the program source.
|
|
|
