Oracle Documerge
P r o d u c t U pd a t e B u l l e t i n
version 3.2.3
IBM z/OS
Revised 09/23/2011
Notice
Oracle Documerge
Version 3.2.3
September 2011
Copyright © 2011, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under
a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other
intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the
extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be
expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or
transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the
United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are
"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable
Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous
applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to
ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages
caused by such use of the Programs.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not
responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use
of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you
and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the
terms of the agreement with the third party, including delivery of products or services and warranty obligations related to
purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing
with any third party.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
THIRD PARTY SOFTWARE NOTICES
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
THIS SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Oracle Documerge version 3.2.3
CONTENTS OF THIS PRODUCT UPDATE BULLETIN
•
Major New Features & Enhancements on page 1
•
Product Documentation on page 4
•
Fixed Trouble Tickets on page 5
•
Suppported and Discounted Version/Release/Level Notification on page 10
•
Product Ordering Instructions on page 10
MAJOR NEW FEATURES & ENHANCEMENTS
Oracle is pleased to announce the general availability of Documerge Version 3.2
Level 3 for IBM Advanced Function Presentation (AFP), Xerox Metacode, and line
printer.
COMPATIBILITY WITH IBM ZSERIES
Oracle is presently not aware of any issues when running Documerge 3.2 on the IBM
zSeries platform. Please note that certain features including, but not limited to, the
following are not supported by Documerge:
•
64-bit addressing
•
•
VDRs and exit programs can use 24-bit or 31-bit addressing, but not 64-bit
addressing mode
Extended Address Volume (EVA)
OVERVIEW
VLAM® z/OS 3.2.1 is included with Documerge z/OS 3.2.3. If you are a user of
Template Technology™, Documerge 3.2.3 is fully compatible with Template
Technology 3.0.6. If you are a Docucorp Dynacomp® user, Dynacomp z/OS 1.0.4 is
a prerequisite for use with Documerge z/OS 3.2.3.
1
Product Update Bulletin
Documerge 3.2 Level 3 Features and Enhancements
•
There are no new features or enhancements in Documerge 3.2.3. This level contains
only fixed trouble tickets (patches).
Documerge 3.2 Level 2 Features and Enhancements
•
New VDR EXEC PARM: RBOPEN=
The format of the parameter is:
RBOPEN=value
Valid values are:
Value
OPENLIB
Explanation
This is the default.
OPENLIBA
If your VDR calls VLMSRVR with the OPENLIBA command, then specify
RBLIB=OPENLIBA in your VDR EXEC PARM.
Example:
//VDRSTEP
EXEC
PGM=MYVDR,PARM='RBOPEN=OPENLIBA'
You may specify this with other VDR EXEC PARMS.
Example:
//VDRSTEP
•
EXEC PGM=MYVDR,PARM='VLMACCESS=RO,VLMCONTROL=KEEP,RBOPEN=OPENLIBA'
New DMGMERGE EXEC PARM: EDTBDT=
This parameter affects AFP output. The format for this parameter is:
EDTBDT=value
Valid values are:
2
Value
Y or YES
Explanation
Normally DMGMERGE will issue an IMM to force a new sheet of paper. A
value of Y or YES causes DMGMERGE to issue an EDT/BDT sequence
instead. Use this for post processors that do not recognize an IMM as
forcing a new sheet of paper.
N or No
This is the default. It causes DMGMERGE to issue an IMM to force a new
sheet of paper.
Product Update Bulletin
Documerge 3.2 Level 1 Features and Enhancements
•
Keep any INVERT DJDE parameters that exists in EDL forms with the new
STRIPINVERT parameter for the GLOBAL command.
This parameter is for Metacode users only. The format of this parameter is
STRIPINVERT=value
where value is the placeholder for one of the following values:
Value
Explanation
Y
or YES
Strip (remove / ignore) any INVERT parameters in DJDE records in EDL
forms.
This is the default.
N
or NO
Keep any INVERT parameters in DJDE records in EDL forms.
•
Perform right-justification of the DMG.SET.NUMBER tag with the new
RTJUSTIFY parameter for the MERGE command.
The format of this parameter is
RTJUSTIFY=DMG.SET.NUMBER
Specify this on any MERGE command to cause BPSDs that use the
DMG.SET.NUMBER tag to be right-justified with this BPSD area. Remember that
right-justification is on a character basis and generally requires a fixed-pitch font for
desired results.
•
Use bit (dash code) processing with the DMG.SET.NUMBER tag.
Use tag names “DMG.SET.NUMBER.BIT.x” where “x” is a value from 1 to 99. See
“Reserved Tags and Dash Codes” in the Documerge Reference Guide for more
information on bit processing.
•
List reserved tag names in TAG parameters in the DMGMERGE SYSIN.
To allow this, use the following new GLOBAL parameter:
TAGPARMRN=Y
-orTAGPARMRN=YES
The default value for this new TAGPARMRN option is “N” (or No), meaning reserved
tag names are ignored if placed in DMGMERGE SYSIN TAG parameters (as is the case
with Documerge 3.2.0). The following reserved tags are affect by this:
•
DMG.MISSING.FORMS
•
DMG.VDR.ERRORS
•
DMG.DD.groupname
•
DMG.ERDD.groupname
•
DMG.ERROR.VRF
•
DMG.GCOPY.groupname
3
Product Update Bulletin
•
DMG.MDEF.groupname
•
DMG.FDEF.groupname
Specifically, this feature was added to allow dynamic building of DMG.DD.groupname
tag values using Command Tag processing.
Documerge 3.2 Level 0 Features and Enhancement
Documerge 3.2 Level 0 offers the following new features and enhancements:
•
Speed improvements for use with IBM zSeries machines. Documerge 3.2 programs have
been modified to run faster on the IBM zSeries machines.
•
Optimization of Metacode output (most effective when used with portrait imposition
and logical pages features). You can optimize DMGMERGE Metacode output —
combining records into one larger record when possible. This can result in faster print,
eliminating the Xerox message "Output has caught up with input."
•
Selection of input trays for banner and trailer forms. DMGMERGE allows input tray
selection for user banner and trailer forms.
•
Implementation of the TAG= parameter for the GLOBAL and FILEDEF commands.
You can now code TAG= paramameters for the GLOBAL and FILEDEF commands,
similar to the current TAG= command for the MERGE command.
•
Online distribution (email) of Trouble Ticket fixes. When possible, Oracle will email
Trouble Ticket fixes, reducing the time needed to distribute them.
PRODUCT DOCUMENTATION
Other than this product bulletin, there are no documentation changes for Documerge z/OS
3.2 level 3.
4
Product Update Bulletin
FIXED TROUBLE TICKETS
DOCUMERGE 3.2 LEVEL 3 TROUBLE TICKET LOG
Table 1: Documerge 3.2 Level 3 Trouble Ticket Log
Trouble Ticket # Activity #
Explanation
TT016288
87699
Overlays with options LAST, NOTLAST or MIDDLE were printing on the wrong
page. Also, when the rulebase used a DTN with SHEET overlays and followed
with a DTN of PHYSICAL overlays, the SHEET overlays would sometimes
print with the PHYSICAL overlays.
TT016423
90637
Rulebase FEED (input tray) was being ignored if the form is not the first form
on a new sheet of paper. Now the input tray change is queued to take effect
on the next sheet. For example, now you can concatenate factored DTNs
where the 1st DTN uses TRAY1 and the 2nd DTN uses TRAY2. Without this
fix, all sheets were using TRAY1 for the concatenation set.
9964678
3-1925064451 AFP MCF2 records were not being handled properly in DMGMERGE, causing
an S0C4 abend or PSF error.
DOCUMERGE 3.2 LEVEL 2 TROUBLE TICKET LOG
Table 2: Documerge 3.2 Level 2 Trouble Ticket Log
Trouble Ticket # Activity #
Explanation
TT011479
64930
S0C4 abend in program DMGMETDF with DMGMERGE COMMONFONTS.
TT013431
67669
At signs printed on left side of paper (portratit mode) with metacode inline
forms.
TT013831
67669
Incorrect vertical spacing with metacode tumble.
TT013891
72487
Spacing problems in DMGAFPP output on 2nd and subsequent page of
multipage form.
TT014110
73232
In DMGAFPP output with multiple BPT/EPT blocks on same page, landscape
text was printing portrait.
TT014455
74310
Adding new EXEC PARM “RBOPEN” to avoid VDR error message
“DMGRFM210F Error opening file RBLIB”
TT015022
76229
Fix S0C4 in program ISISEQIO when using BMC Batch Optimizer.
TT015089
76900
With ALLERROR=YES, the user banner page does not print on ERRDDN.
TT015134
76277
Adding new EXEC PARM “EDTBDT” to write EDT/BDT sequence instead of
IMM to force new sheet of paper for AFP.
TT015634
81014
In DMGAFPP output, when the first text is a BPSD, horizontal spacing problems
can occur due to an incorrect SVI value being generated.
TT015947
84872
Trailer forms use wrong FILEDEF TAG values.
5
Product Update Bulletin
Table 2: Documerge 3.2 Level 2 Trouble Ticket Log (Continued)
Trouble Ticket # Activity #
Explanation
TT016089
85106
Loop in common fonts program DMGMETDF when more than one page
oriented DJDE is in a form.
TT016159
76209
DMGMERGE message DMGMRG1866I prints garbage for the cluster feed
names.
TT016160
86948
DMGMERGE message DMGMRG252I prints garbage or an incorrect form
name for missing overlay forms.
TT016205
N/A
Remove compression routines from archive output DMGMERGE.
DOCUMERGE 3.2 LEVEL 1 TROUBLE TICKET LOG
Table 3: Documerge 3.2 Level 1 Trouble Ticket Log
Trouble Ticket # Activity #
Explanation
TT010016
58443
(Metacode users only) DMGMERGE wasn’t properly handling STACK/
OFFSET printer options with multiple Metacode output files.
TT010155
59265
DMGMERGE wasn’t always placing the proper Documerge overlays on the
last page of a package.
TT010245
59460
(Metacode users only) Forms with “FORMS=NONE” in the DJDE records
would sometimes be written without the “FORMS=NONE”.
TT010377
60351
(Metacode users only) Documerge now supports metacode FEED values
longer than six (6) characters.
TT010404
60438
(Metacode users only) DMGMERGE with Metacode tumble processing would
sometimes incorrectly generate message DMGMRG863E (font not found in
font group def) even though the font is present.
TT010531
61311
DMGRBMUT report page numbering wasn’t sequential.
TT010703
62105
In DMGMERGE, DTN-level SHEET overlays were sometimes printing on the
wrong pages.
TT010733
62209
(Metacode users only) DMGMERGE no longer loops when using
COMMONFONTS with Docuword forms.
TT011279
-none-
(Metacode users only) When using COMMONFONTS and overlays, and
FORMSBUFF was too small, DMGMERGE was issuing error message:
DMGMRG422E,RC=910,RS=4992.
TT011457
65845
(Metacode users only) When using a Docuword form with COMMONFONTS,
subsequent forms (either Docuword or non-ocuword) sometimes didn’t get
changes to match the new COMMONFONTS list.
TT011479
64930
(Metacode users only) On rare occasions, DMGMERGE with
COMMONFONTS would abend S0C4.
6
Product Update Bulletin
Table 3: Documerge 3.2 Level 1 Trouble Ticket Log (Continued)
Trouble Ticket # Activity #
Explanation
TT011501
64389
In DMGMERGE, optionally allow SYSIN TAG parameters to contain reserved
tag names.
Adding new GLOBAL parameter: TAGPARMRN=x where x is Y or
YES or N or NO.
The default is NO.
Y or YES honors reserved tag names found in DMGMERGE SYSIN TAG
parameters.
TT011726
66762
BPSDs using tag name DMG.SET.NUMBER can now be right-justified by
specifying the following MERGE command parameter in the DMGMERGE
SYSIN: RTJUSTIFY=DMG.SET.NUMBER.
TT011728
66773
BPSDs can now use “.bit” (dash code) processing with tag name
DMG.SET.NUMBER.
TT011906
67276
In DMGMERGE, Documerge overlays with the LAST option weren’t always
written when overlays with MIDDLE or NOTLAST were also used in a package.
TT012006
67347
DMGMERGE no longer abends S0C4 when the DMG.FLST.groupname tag
contains no data.
TT012132
65468
(AFP users only) In DMGMERGE, an incorrect IMM could be used
when using DYNAMICCG=N and a form with no IMM follows a form with an
embedded IMM in the EDL.
TT012139
67767
(Metacode users only) In DMGMERGE, release 3.2 was removing any
INVERT parameters from DJDEs in EDL forms, where release 3.0 did not.
DMGMERGE SYSIN now has a new GLOBAL parameter:
STRIPINVERT=x where x is Y or YES or N or NO.
The default is YES.
N or NO keeps any INVERT DJDE parameters that exist in EDL forms.
TT012307
55620
(Metacode users only) DMGMERGE Metacode now properly handles more
than 100 inline graphics records (GRAPHIC= in DJDE) in a form.
TT012308
48380
With PARMFILE=ddname in the EXEC PARM, Documerge would sometimes
incorrectly create an open error on the parm file.
7
Product Update Bulletin
VLAM 3.2 LEVEL 1 TROUBLE TICKET LOG
Table 4: VLAM 3.2 Level 1 Trouble Ticket Log
Trouble Ticket # Activity #
Explanation
-none-
-none-
(Commcommander 2.1-specific enhancements) Several enhancements to
VLAM required by Commcommander 2.1 and implementation of its multitasking support.
TT002397
29478
(Enhancement) Implemented a “global” VLMMAINT parameter to allow users
to control whether the member's “last access date” will be updated. The
ACCESS= global parameter was implemented to control specific VLMMAINT
commands.
TT009076
55019
(Retrofit from VLAM 3.1) When accessing multiple EDL’s, the application would
periodically and randomly receive a “record not found” error. Corrected the
program logic pertaining to the handling of internal VLAM Library “alpha index”
control blocks.
TT009518
-none-
When running the VLMMAINT RESTORE command and using the wild card
feature to select all members from the backup file to be restored (MEM=*), the
job would end with a condition code zero, but with the error message that “no
Members matched the selection criteria”. No members are restored to the
VLAM Library. Corrected program logic that was incorrectly handling the
Member’s expiration date (EXPDATE) field.
TT009730
-none-
(Commcommander 2.1-specific enhancement) Enhanced the DD Name query
function in the dynamic dataset allocation module VLMSVC99. This
enhancement was implemented for the Commcommander 2.1 VLAM Driver.
TT009986
-none-
When running the VLMMAINT FORMAT command on a VSAM dataset that
had been allocated and defined with the VSAM ‘SPEED’ attribute, the job
ended with a return code 20 and error message VLM1134P “No error message
matches the given return/reason code combination”. This correction now
allows the FORMAT command to process with the VSAM ‘SPEED’ attribute.
TT010333
59951
When running the VLMMAINT BACKUP and COPY commands and accessing
a VLAM Library in ‘read only’ mode (VLMMAINT parameter ACCESS=READ),
the job would receive RACF system error message
“INSUFFICIENT ACCESS AUTHORITY”
This corrects the VLMMAINT BACKUP and COPY commands and allows the
job to run in ‘read only’ mode. Also see TT011128 below.
TT010393
-none-
Corrected VLAM modules that use the internal ISITIME macro so that they can
be linked reentrant.
TT010540
-none-
(Enhancement) Implement support of Relative Record Data Sets (RRDS)
VSAM files greater than four gigabytes (GB) in size. This implements IBM’s
VSAM Extended Addressability feature. Previously, VLAM Libraries have been
limited to a maximum size of four GB because of this VSAM limitation.
TT010626
-none-
When running VLMMAINT BACKUP command with the DISP=ARCHIVE
parameter against a large EDL, the job issues error message VLMBCK1041P
“VSAM GET failed while acquiring a block for update” and VSAM Return
Code=8 Feedback=64. Also, the job step can abend with a SOC4-011 in
module VLMAICTR. This fix corrects the problem.
8
Product Update Bulletin
Table 4: VLAM 3.2 Level 1 Trouble Ticket Log (Continued)
Trouble Ticket # Activity #
Explanation
TT010640
-none-
When using the VLMMAINT ALTER command to change a Members
Expiration Date, an invalid date is stored in the Members Directory. An
Expiration Date of EXPDATE=0999999F was created incorrectly. This has
been fixed to store a valid date.
TT010641
61916
The VLMMAINT DIRECTORY command using the EXPDATE= selection
parameter was not working correctly. This fix will now allow the DIRECTORY
command to process the Expiration Date parameter ?qual to or less
than?(EXPDATE=<) and the “Equal to or greater than” (EXPDATE=>)
parameters to select and report the correct VLAM Members from the VLAM
Library. Also, you can now specify a zero in a the “date range” selection format
to select and report VLAM Members with an Expiration Date of zero (e.g.,
EXPDATE=0000/00/ 00-2005/01/15).
TT011128
64407
When running the VLMMAINT Directory command and accessing a VLAM
Library in ‘read only’ mode (VLMMAINT parameter ACCESS=READ), the job
would receive RACF system error message
“INSUFFICIENT ACCESS AUTHORITY”
This corrects the VLMMAINT DIRECTORY command and allows the job to run
in ‘read only’ mode. Also see TT010333 above.
TT011654
-none-
(Commcommander 2.1-specific enhancement) Implemented new ‘Deallocate’
Data Definition (DDN) and Dataset Name (DSN) functions in the dynamic
dataset allocation module VLMSVC99. This enhancement was implemented
for the Commcommander 2.1 VLAM Driver.
TT002286
-none-
(Enhancement) Implement a new member “expiration date” field. This new field
will work the opposite as the existing member's “effective date” field. This has
been implemented as part of TT004949 described below.
TT002537
-none-
(Enhancement) Implement a new vlmaccess=ro (read only) for the VLMMAINT
BACKUP command. This enhancement allows users to control whether the
member’s LASTACCESSDate is updated.
TT002538
30396
(Enhancement) Implement a new vlmaccess=ro (read only) for the VLMMAINT
COPY command. This enhancement allows users to control whether the
member’s LASTACCESSDate is updated.
TT004949
42766
(Enhancement) Implement a “policy expiration date” processing. A new
member attribute was added to the VLAM Library for the user to specify the
member's “policy expiration date”. This enhancement depends on the
additional enhancement to Documerge that processes this new date field.
TT008541
52495
This APAR corrected an error causing VSAM return/reason code 44/ 1604.
This is a “VSAM” ‘put’ failed while writing system buffers.” This error occurs
when running multiple applications that are updating (writing) to the same
VLAM Library at the same time. This error was identified when running the
I.R.I.S. and Commcommander VLAM Driver products. An internal VLAM
program was corrected to downgrade its BFL/RPL before attempting buffer
writes in its 'flush' routine.
TT008741
-none-
This APAR corrected an internal error that now allows VLMSRVW to process
OPENNEWR correctly. This error was identified from the Commcommander
VLAM Driver product.
9
Product Update Bulletin
Table 4: VLAM 3.2 Level 1 Trouble Ticket Log (Continued)
Trouble Ticket # Activity #
Explanation
TT008995
When printing a VLMMAINT directory report using TYPE=DOCUMERGE, it
was printing a 0 for the DTN number. This error occurred after printing more
than 500 members from EDLs that contained a large number of members. The
program was corrected by closing the member after reading its DTNS chain
data.
54927
SUPPPORTED AND DISCOUNTED VERSION/RELEASE/LEVEL
NOTIFICATION
SUPPORTED VERSIONS/RELEASES/LEVELS
•
Documerge 3.2 (all levels)
•
Documerge 3.1 (all levels)
DISCONTINUED VERSION/RELEASES/LEVELS
•
Documerge 3.0 (all levels)
PRODUCT ORDERING INSTRUCTIONS
To receive Documerge Version 3.2, Level 3, your organization must:
•
Be a licensed user of Documerge
•
Be current on Documerge software maintenance fees
If you need further assistance, please log a Service Request using My Oracle Support at
https://support.oracle.com
Address any additional inquiries to:
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
10