COMM-PRO
1997 - SHIP25 MAINTENANCE SUMMARY
SHIP25 MAINTENANCE SUMMARY
--------------------------
Date: December 31, 1997
Memorandum
To: All Comm-Pro Users at the SHIP25 Distribution Levels.
All references to SHIP25 also includes support for SHIP25 Mod 1
(SHIP25M1) and SHIP25 Mod 2 (SHIP25M2) unless otherwise noted.
The following is a summary of SHIP25 maintenance (APARs, etc.)
issued as of the noted dates. This summary is provided as a
reference for problem resolution or preventative maintenance.
The summary record contains the following information:
APAR - Assigned Comm-Pro APAR number (S25nnn)
REF/NOTE - Comm-Pro internal identification (R_name) for
miscellaneous fixes and enhancements.
IBM_NOTE - IBM product or support issues, including early
warning of IBM PTF/APAR or error conditions.
CP_NOTE - Comm-Pro product or support issues.
COMPONENT - The Comm-Pro package or resource type that the
corrective logic addresses.
DATE - For APARs and Enhancements, this date reflects
when the actual corrective logic was applied
to the standard Comm-Pro SHIP25 distribution
libraries.
For all others, this date reflects when the item
was added to the summary.
DESCRIPTION - Brief description of the problem. Refer to the
actual APAR Memo for additional information
and corrective logic, if available.
Please refer to the SHIP25 documentation manual in APPENDIX F
(Maintenance) for additional information.
SHIP25 Maintenance Summary Detail
-----------------------------------------------------------------------------
APAR/REF - COMPONENT
DATE DESCRIPTION.
R_XFSETUP - VM/CMS Environment - Comm-Pro Product Installation,
01-15-1997 Conditional execution logic added to the XFCOMMPRO EXEC.
Exec user will be prompted to allow XFSETUP to execute or
to NOP. Note that XFSETUP is shipped as a "sample' setup
EXEC which requires customization at each site. Additional
XFSETUP information was added to our SHIP25 documentation
manual on May 19, 1997.
R_XFCOMMPRO - VM/CMS Environment - Comm-Pro Product SYSGEN Support,
01-20-1997 XFCOMMPRO EXEC was modified to report an error condition if
the Comm-Pro Stage 1 input file is not RECFM=F. This condition
was previously causing our EXEC to "get lost" when it scanned
our BUILD macro. Logic was also added to detect unusual XFR90
and XFBR14 set-up to prevent our Stage 3 Table 1 and Table 2
assemblies from failing because IHR90 cannot be found.
R_ALIGN4 - 3745 MVS Environments - Comm-Pro Product SYSGEN Support,
03-17-1997 Newer SSP libraries no longer support the ALIGN4 link edit
parameter. Comm-Pro Stage 3 and 4 LKED step encounters error
message encountered 'IEW2020E OPTION NAME ALIGN4 IS INVALID.
OPTION IGNORED.' Solution removed the ALIGN4 parameter from
our LKED step parameter list.
R_BUILDJC - MVS and DOS/VSE Environments - Comm-Pro Product SYSGEN Support,
04-18-1997 Logic added to force our JOBCARD=YES option for TYPXEQ=AUTO
environments. This will prevent submission of the Stage 3 job
stream without a jobcard.
R_NEO-SNI - Users of Comm-Pro NEO Products Across SNI FAT Links,
05-04-1997 Comm-Pro DSP resources routed over an SNI FAT Link instead of
the Channel Adapter encountered buffer header data in with the
user data due to a secondary buffer boundary condition.
Solution is to change FMDX700 logic to apply the buffer offset
(U1OFFSET) when forming the SOD (Start of Data) pointer in the
secondary buffer.
S25098 - DSP, Network Address System Select Pool (Form 6) users,
07-01-1997 Introduction of our X.25 Buffer High Support on 06/17/1996
distribution caused us to reject the Network Address System
Select Call Request with a Clear Diagnostic 7F.
Solution is to disable unnecessary X.25 transmit and receive
buffer location debugging validity check logic that previously
required the Call Request packet buffer to be located between
the X.25 Receive and Transmit buffer header. Note that our
Buffer High Support relocates the buffer pool's, not the buffer
headers.
R_TNUNCT - DSP users,
Enhancement added to count DSP Response Undelivered events.
This global fullword counter will allow us to monitor and
identify the frequency or magnitude of the Response Undelivered
activity. Counter located via Comm-Pro Console display 'DCSA'
at entry XFTNUNCT.
R_RACXF25 - NAS NEO/NCP users,
07-01-1997 VRHELD and VRREL global fullword counters can now be located
via the Comm-Pro Console display 'DCSA' at entry XFSWTOCT.
S25099 - ITI/EP users,
07-29-1997 001B ABEND at offset X'50A' in module XFNSSC (RDTO200) due to
an unusual timing condition where input arrives after the
timeout expires but before CCBCLOCK is reset. A window exists
in XFNNQRMQ (Level 4 routine) that allows CCBCLOCK to continue
to run after a packet is enqueued to (CCXIQ) input queue.
CCBCLOCK is not reset for approximately 15 instruction cycles
after the enqueue. If the Level 3 input timer expires during
this window, the ABEND will occur at Level 3.
Solution is to change the Level 3 timeout logic to simply
ignore this condition which will allow the logic to correctly
handle the input sequence.
R_JC234XF25 - MVS and DOS/VSE Environments - Comm-Pro Product SYSGEN Support,
10-07-1997 We now provide users the ability to define unique jobcard JCL
for the Comm-Pro Stage 1 - 4 generation process.
R_NDFPLI900 - 3746-900 Attachment - Comm-Pro Product SYSGEN Support,
12-31-1997 Comm-Pro Stage 3 (NDFPLI Step) Sysgen, **ERROR** 'LINE ADDRESS
0 (DECIMAL) DEFINED AS NCP RESOURCE IN NDF AND EP RESOURCE IN
XF GEN'. Note that for logical ODLC lines (LOGICAL=1,OLDC=1),
NDF sets RLNUM=0 which is what we key on to set the NCP lines
in use indicator. It turns out that when real line address 0
is used in the Comm-Pro Stage 1 source (CPSTG1) we appear
(erroneously) to have a conflict.
Solution is to test for LOGICAL=1 when we decode the CXTACB
macro and, if found, simply bypass the macro.
Note that Comm-Pro resources are not currently supported on
the model 900.
-----------------------------------------------------------------------------
SHIP25 Maintenance Summary Detail End