Errores XCOM

CA XCOM Data Transport for z/OS 11.
6
CA RS 1306 Service List
Release
11.6
Service
Description
Hiper
RO52697
XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0
RO53137
BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API
RO53772
BATCH - RETRY FAILS FOR TCPIP TRANSFERS WITH TYPE=EXECUTE
RO54032
XCOMN0531E GATEWAY FAILED TO IMPORT FILE
RO54346
BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I
RO54373
CONTINUE EXEC PARAMETER DEFAULT VALUE CHANGED INCORRECTLY
RO54666
XCOMJOBH SAMPLE FAILS WITH RC=16
RO55001
BATCH - XCOMINQ STORAGE LEAK PROBLEM
RO55407
DEST - TCP/IP SESSIONS MAY EXCEED DESTINATION TCPSESS
RO55608
XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG
RO56104
INCORRECT XCOMM0656I MESSAGE DURING XCOMJOB TYPE=INQUIRE

The CA RS 1306 service count for this release is
11
CA XCOM Data Transport for z/OS 11.5

CA RS 1306 Service List
Release
11.5
Service
Description
Hiper
RO52698
RO52735
CBXGJCL: UPDATE MEMBERS
RO53136
RO53831
RO54371
RO54595
RO54847
RO55617
XCOMM0124E DATASET IS NOT A PDSE SENDING FROM R11.5 TO R11.6
RO55737
SERVER - S0C4 ABEND IN XCOMHENJ AT X'51E'

The CA RS 1306 service count for this release is
CA XCOM Data Transport for z/OS

CA RS 1306 Service List for CBXGB50
FMID
CBXGB50
Service
Description
Hiper
RO52698
RO52735
RO53136
RO53831
RO54371
RO54595
RO54847
RO55617
RO55737

The CA RS 1306 service count for this FMID is
CA XCOM Data Transport for z/OS

CA RS 1306 Service List for CBXGB60
FMID
CBXGB60
Service
Description
RO52697
RO53137
RO53772
RO54032
RO54346
RO54373
RO54666
RO55001
RO55407
RO55608
RO56104

The CA RS 1306 service count for this FMID is 11
Hiper

CA RS 1306 - PTF RO52697 Details
Release Service
11.6
RO52697 RO52697
M.C.S. ENTRIES
Details
= ++PTF (RO52697)

PROBLEM DESCRIPTION:
After starting a server with the global parameter SNA=NO,
any XCOMJOB that is run against this server that omits
the STCIP and STCPORT parameters will not get scheduled
and will end incorrectly with a RC=0.
SYMPTOMS:
The following error message is displayed in the xcomlog
with a return code of 0:
XCOMM0817E STCIP= PARAMETER MISSING - CANNOT CONNECT
TO SERVER
IMPACT:
Users might assume that an XCOMJOB transfer has completed
successfully because of the RC=0 when in fact the transfer
has failed.
CIRCUMVENTION:
Ensure that the STCIP and STCPORT parameters are specified
in the XCOMJOB when the SNA global parameter is set to NO.
PRODUCT(S) AFFECTED:
CA XCOM Data Transport for z/OS r11.5
Star Problem(s):
XCMVS 1057
Copyright (C) 2013 CA. All rights reserved. R00050-BXG116-SP1
DESC(XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50360 RO50361 RO50683 )
SUP ( TR52697 )

Release Service
11.6
RO53137 RO53137
M.C.S. ENTRIES
Details
= ++PTF (RO53137)

A long-running STC which calls the XCOM API (XCOMJOB) repeatedly gets its
storage exhausted over time and needs to be recycled to resolve the problem.
This is due to the NETDSECT not getting freed at the end of each call to
XCOMJOB.
SYMPTOMS:
The following messages are displayed on XCOMLOG.
XCOMM0128I FOLLOWING FMH7 SENT TO CONVERSATION PARTNER
XCOMM0516E UNABLE TO GETMAIN STORAGE FOR FILE CONTROL BLOCK AREA
- TRANSFER TERMINATED
These messages are then followed by S878 and/or S80A abends.
IMPACT:
Jobs that call XCOMJOB via the API repeatedly without ending may run into
problems with storage getting exhausted.
CIRCUMVENTION:
Limit the number of times your API program makes calls to XCOMJOB or
increase the size of the region where your API program runs.
PRODUCTS AFFECTED:
CA XCOM Data Transport r11.5
Star Problem(s):
XCMVS 1067
DESC(BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50360 RO50361 RO50683 )
SUP ( RO52697 TR52697 TR53137 )

Release Service
11.6
RO53772 RO53772
M.C.S. ENTRIES
Details
= ++PTF (RO53772)

A CA XCOM TYPE=EXECUTE batch job may fail during a retry of a TCP/IP
transfer and no other retries are attempted.
SYMPTOMS:
The following messages appear in XCOMLOG on XCOM batch job:
XCOMM0094E INVALID STATE FOR SEND
COMMAND
XCOMXATT R
XCOMM0780E Txpi 215: Socket send error return value = 140
The following message is displayed in XCOMLOG on XCOM server:
XCOMM0780E Txpi 226: Select timed out with no data available
IMPACT:
TCP/IP transfers from a TYPE=EXECUTE batch job that receive retryable error
conditions will fail instead of attempting a retry.
CIRCUMVENTION:
Change the batch job to TYPE=SCHEDULE or use SNA connection instead of
TCP/IP.
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1015
DESC(BATCH - RETRY FAILS FOR TCPIP TRANSFERS WITH TYPE=EXECUTE) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50683 RO51213 RO51305 RO52043 RO52912 )
SUP ( TR53772 )

Release Service
11.6
RO54032 RO54032
M.C.S. ENTRIES
Details
= ++PTF (RO54032)

Transferring files into CA XCOM Gateway 11.6 results in the transfer failing
with error message XCOMN0531E GATEWAY FAILED TO IMPORT FILE.
This is due to not indicating to the Gateway that the transfer is from
CA XCOM Data Transport.
SYMPTOMS:
An XCOMN0531E message occurs from CA XCOM Gateway 11.6 and the transfer
is terminated.
IMPACT:
No transfers can take place from CA XCOM Data Transport 11.6 to CA XCOM
Gateway 11.6.
CIRCUMVENTION:
None.
Star Problem(s):
XCMVS 1069
DESC(XCOMN0531E GATEWAY FAILED TO IMPORT FILE) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO51058 RO52043 )
SUP ( TR54032 )

Release Service
11.6
RO54346 RO54346
M.C.S. ENTRIES
Details
= ++PTF (RO54346)

An XCOMJOB TYPE=INQUIRE may get a false error saying no history record for
request nnnnnn. This is due to a timing problem when a set of XTC transfers
is scheduled and if a transfer being inquired is also being purged by the
XCOM server at the same time.
SYMPTOMS:
The following message is displayed in the XCOMLOG:
XCOMM0656I NO HISTORY RECORD FOR REQUEST nnnnnn.
IMPACT:
The wrong transfer status is displayed by the TYPE=INQUIRE step.
CIRCUMVENTION:
None
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1074
DESC(BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I) .
++VER (Z038)
FMID (CBXGB60)
SUP ( TR54346 )

Release Service
11.6
RO54373 RO54373
M.C.S. ENTRIES
Details
= ++PTF (RO54373)

The default setting of the CONTINUE parameter was incorrectly changed
from CONTINUE=YES to CONTINUE=NO in the new release of XCOM for z/OS
- r11.6 which will affect batch processing when transfer errors occur.
SYMPTOMS:
A batch job, where the first transfer fails, will immediately end with
a RC=16 and with the following message:
XCOMM0447E EXECUTE REQUEST ENDED WITH ERRORS - CONTINUE=YES NOT
SPECIFIED
IMPACT:
Existing XCOM for z/OS users will assume the CONTINUE parameter is set
to YES by default and will expect batch processing to work as it has in
prior releases.
CIRCUMVENTION:
Specify the CONTINUE=YES parameter with TYPE=EXECUTE transfers.
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1083
DESC(CONTINUE EXEC PARAMETER DEFAULT VALUE CHANGED INCORRECTLY) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50360 RO50361 RO50683 RO50746 RO51243 )
SUP ( RO52697 RO53137 TR52697 TR53137 TR54373 )
10

Release Service
11.6
RO54666 RO54666
M.C.S. ENTRIES
Details
= ++PTF (RO54666)

When using the sample JCL job, XCOMJOBH, to generate an Easytrieve
report,it is failing with a rc=16. This is due to Easytrieve now
being distributed as an install with Common Services r14.1 and as
a result requires XCOMJOBH to be updated to reflect these changes
to the load library and maclib locations. In addition, an LMPKEY is
not needed to run the reports.
SYMPTOMS:
The following error message is displayed when executing
XCOMJOBH.
*******B006 MACRO SYSTEM - PDS , DATECONV - MEMBER NOT FOUND
%DATECONV START-DATE-JULIAN YYDDD START-DATE CCYYMMDD THRESHOLD 90
*******B076 REMAINDER OF STATEMENT IS IGNORED
IMPACT:
Users are not able to successfully display sample history Easytrieve reports.
CIRCUMVENTION:
Comment out any line with the macro, %DATECONV, in the XCOMEHRP and
XCOMESTT sample members and re-submit the XCOMJOBH sample JCL.
PRODUCT(S) AFFECTED: CA XCOM Data Transport for z/OS r11.5
Star Problem(s):
XCMVS 1086
DESC(XCOMJOBH SAMPLE FAILS WITH RC=16) .
++VER (Z038)
FMID (CBXGB60)
SUP ( TR54666 )
11

Release Service
11.6
RO55001 RO55001
M.C.S. ENTRIES
Details
= ++PTF (RO55001)

A long-running STC which calls the XCOM API (XCOMJOB) TYPE=INQUIRE
repeatedly gets its storage exhausted over time and needs to be recycled
to resolve the problem. This is due to the XCOMHIST buffer not completely
getting freed at the end of each call to XCOMJOB.
SYMPTOMS:
IMPACT:
CIRCUMVENTION:
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1084
DESC(BATCH - XCOMINQ STORAGE LEAK PROBLEM) .
++VER (Z038)
FMID (CBXGB60)
SUP ( RO54346 TR54346 TR55001 )
12

Release Service
11.6
RO55407 RO55407
M.C.S. ENTRIES
Details
= ++PTF (RO55407)

The TCP/IP session count in the destination member is not maintained
consistently which may cause the number of concurrent local TCP/IP file
transfers to exceed the TCPSESS value specified in the destination
member.
SYMPTOMS:
The number of concurrent local TCP/IP file transfers may exceed the value
of TCPSESS specified in the destination member. Also, the MODIFY command
LIST will show the incorrect number of current sessions.
IMPACT:
The additional concurrent local TCP/IP file transfers will cause additional
resource usage on both the local and remote partners to handle the additional
sessions.
CIRCUMVENTION:
Use the TCPSESS parameter in the Default Options Table to set the maximum
number of TCP/IP file transfers that the server can perform concurrently
to any one IP address.
PRODUCTS AFFECTED:
PRODUCT(S) AFFECTED: CA XCOM Data Transport for z/OS
Release 11.6
Star Problem(s):
XCMVS 1088
DESC(DEST - TCP/IP SESSIONS MAY EXCEED DESTINATION TCPSESS) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50351 RO50354 RO50360 RO50683 RO50746 RO51243
RO51256 RO52912 RO53287 )
SUP ( TR55407 )
13

Release Service
11.6
RO55608 RO55608
M.C.S. ENTRIES
Details
= ++PTF (RO55608)

When transferring a PDS that has a bad ALIAS, an error message XCOMM0380E
is displayed on the XCOMLOG of the sending XCOM partner but not on the
receiving XCOM partner. This is because the bad ALIAS on the PDS can only
be detected by the sending XCOM partner. The bad ALIAS entry is not sent
to the target PDS and the receiving XCOM partner is not aware of the error.
SYMPTOMS:
The following message is displayed on XCOMLOG.
XCOMM0380E xxxxxxxx MEMBER NOT FOUND FOR ALIAS TTR
IMPACT:
If the PDS that has a bad ALIAS is initiated by the sending XCOM partner,
the sender is aware of this logic error on the PDS. If the transfer is
initiated by the receiving XCOM partner, the receiving partner is not
aware of this logic error on the PDS.
CIRCUMVENTION:
None
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1087
DESC(XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50350 RO51058 RO51241 RO51242 RO51355 RO52572 )
SUP ( RO52044 RO52350 TR50347 TR52044 TR52350 TR55608 )
14

Release Service
11.6
RO56104 RO56104
M.C.S. ENTRIES
Details
= ++PTF (RO56104)

After multiple transfers have been scheduled to a PLEXQ group
of servers, a TYPE=INQUIRE XCOMJOB to the PLEXQ will then
result in an incorrect error message being returned.
SYMPTOMS:
The following incorrect error message is returned for a TYPE=
INQUIRE XCOMJOB after multiple transfers have been scheduled
to a PLEXQ group of servers:
"XCOMM0656I NO HISTORY RECORD FOR REQUEST nnnnnn"
IMPACT:
Unable to properly determine the status of the transfer requests
when running an XCOMJOB TYPE=INQUIRE.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1090
DESC(INCORRECT XCOMM0656I MESSAGE DURING XCOMJOB TYPE=INQUIRE) .
++VER (Z038)
FMID (CBXGB60)
PRE ( RO50484 )
SUP ( RO54346 RO55001 TR54346 TR55001 TR56104 )
15

Release Service
11.5
RO52698 RO52698
M.C.S. ENTRIES
Details
= ++PTF (RO52698)

After starting a server with the global parameter SNA=NO,
any XCOMJOB that is run against this server that omits
the STCIP and STCPORT parameters will not get scheduled
and will end incorrectly with a RC=0.
SYMPTOMS:
The following error message is displayed in the xcomlog
with a return code of 0:
XCOMM0817E STCIP= PARAMETER MISSING - CANNOT CONNECT
TO SERVER
IMPACT:
Users might assume that an XCOMJOB transfer has completed
successfully because of the RC=0 when in fact the transfer
has failed.
CIRCUMVENTION:
Ensure that the STCIP and STCPORT parameters are specified
in the XCOMJOB when the SNA global parameter is set to NO.
Star Problem(s):
XCMVS 1057
DESC(XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0) .
++VER (Z038)
FMID (CBXGB50)
SUP ( RO34910 RO36068 RO42676 TR34910 TR36068 TR42676
TR52698 )
16

Release Service
11.5
RO52735 RO52735
M.C.S. ENTRIES
Details
= ++PTF (RO52735)

The CAI.CBXGJCL dataset members LINKRACF, LINKTOPS, XCOM, XCOMADM, XCOMENCR,
XCOMJOBH, XCOMJOBR, XCOMJOBS and XCSMPRPT did not specify a STEPLIB
and the comments were not consistent with other members.
SYMPTOMS:
Inconsistent comments in the members and missing STEPLIB.
IMPACT:
The comments in these members were not consistent with the comments in
other members which could cause problems executing the JCL members. The
missing STEPLIB might also cause the job to fail unless CA Data Transport
installation loadlib was in the LPA.
CIRCUMVENTION:
Correct the comments to include CAI as the high level qualifier used in
members XCOMENCR, XCOMJOBH, XCOMJOBR and XCOMJOBS. Change the
default prefixes to XCOM.RB5 in XCOM and XCOMADM. Also add comments to update
JOBCARD in LINKRACF and LINKTOPS.
PRODUCT(S) AFFECTED: CA XCOM Data Transport for z/OS
r11.5
Star Problem(s):
XCMVS 866
DESC(CBXGJCL: UPDATE MEMBERS) .
++VER (Z038)
FMID (CBXGB50)
PRE ( RO18001 RO19522 RO22200 )
SUP ( TR25147 TR52735 )
17

Release Service
11.5
RO53136 RO53136
M.C.S. ENTRIES
Details
= ++PTF (RO53136)

A long-running STC which calls the XCOM API (XCOMJOB) repeatedly gets its
storage exhausted over time and needs to be recycled to resolve the problem.
This is due to the NETDSECT not getting freed at the end of each call to
XCOMJOB.
SYMPTOMS:
IMPACT:
CIRCUMVENTION:
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1067
DESC(BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API) .
++VER (Z038)
FMID (CBXGB50)
SUP ( RO34910 RO36068 RO42676 RO52698 TR34910 TR36068
TR42676 TR52698 TR53136 )
18

Release Service
11.5
RO53831 RO53831
M.C.S. ENTRIES
Details
= ++PTF (RO53831)

An XCOMJOB TYPE=INQUIRE may get a false error saying no history record for
request nnnnnn. This is due to a timing problem when a set of XTC transfers
is scheduled and if a transfer being inquired is also being purged by the
XCOM server at the same time.
SYMPTOMS:
The following message is displayed in the XCOMLOG:
XCOMM0656I NO HISTORY RECORD FOR REQUEST nnnnnn.
IMPACT:
The wrong transfer status is displayed by the TYPE=INQUIRE step.
CIRCUMVENTION:
None
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1074
DESC(BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I) .
++VER (Z038)
FMID (CBXGB50)
PRE ( RO22200 )
SUP ( RO35965 RO51064 TR35965 TR51064 TR53831 )
19

Release Service
11.5
RO54371 RO54371
M.C.S. ENTRIES
Details
= ++PTF (RO54371)

A long-running STC which calls the XCOM API (XCOMJOB) TYPE=INQUIRE
repeatedly gets its storage exhausted over time and needs to be recycled
to resolve the problem. This is due to the XCOMHIST buffer not completely
getting freed at the end of each call to XCOMJOB.
SYMPTOMS:
IMPACT:
CIRCUMVENTION:
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1084
DESC(BATCH - XCOMINQ STORAGE LEAK PROBLEM) .
++VER (Z038)
FMID (CBXGB50)
PRE ( RO22200 )
SUP ( RO35965 RO51064 RO53831 TR35965 TR51064 TR53831
TR54371 )
20

Release Service
11.5
RO54595 RO54595
M.C.S. ENTRIES
Details
= ++PTF (RO54595)

When using the sample JCL job, XCOMJOBH, to generate an Easytrieve
report,it is failing with a rc=16. This is due to Easytrieve now
being distributed as an install with Common Services r14.1 and as
a result requires XCOMJOBH to be updated to reflect these changes
to the load library and maclib locations. In addition, an LMPKEY is
not needed to run the reports.
SYMPTOMS:
The following error message is displayed when executing
XCOMJOBH.
*******B006 MACRO SYSTEM - PDS , DATECONV - MEMBER NOT FOUND
%DATECONV START-DATE-JULIAN YYDDD START-DATE CCYYMMDD THRESHOLD 90
*******B076 REMAINDER OF STATEMENT IS IGNORED
IMPACT:
Users are not able to successfully display sample history Easytrieve reports.
CIRCUMVENTION:
Comment out any line with the macro, %DATECONV, in the XCOMEHRP and
XCOMESTT sample members and re-submit the XCOMJOBH sample JCL.
PRODUCT(S) AFFECTED: CA XCOM Data Transport for z/OS r11.5
Star Problem(s):
XCMVS 1086
DESC(XCOMJOBH SAMPLE FAILS WITH RC=16) .
++VER (Z038)
FMID (CBXGB50)
PRE ( RO18001 RO19522 RO22200 RO52735 )
SUP ( TR54595 )
21

Release Service
11.5
RO54847 RO54847
M.C.S. ENTRIES
Details
= ++PTF (RO54847)

When transferring a PDS that has a bad ALIAS, an error message XCOMM0380E
is displayed on the XCOMLOG of the sending XCOM partner but not on the
receiving XCOM partner. This is because the bad ALIAS on the PDS can only
be detected by the sending XCOM partner. The bad ALIAS entry is not sent
to the target PDS and the receiving XCOM partner is not aware of the error.
SYMPTOMS:
XCOMM0380E xxxxxxxx MEMBER NOT FOUND FOR ALIAS TTR
IMPACT:
If the PDS that has a bad ALIAS is initiated by the sending XCOM partner,
the sender is aware of this logic error on the PDS. If the transfer is
initiated by the receiving XCOM partner, the receiving partner is not
aware of this logic error on the PDS.
CIRCUMVENTION:
None
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1087
DESC(XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG) .
++VER (Z038)
FMID (CBXGB50)
RO24536 RO26520 RO26803 RO31175 RO33460 RO37606
RO41249 RO42212 RO48443 RO49052 RO49786 RO50921
RO51843 RO52175 )
SUP ( TR54847 )
22

Release Service
11.5
RO55617 RO55617
M.C.S. ENTRIES
Details
= ++PTF (RO55617)

Transferring a PDSE library from XCOM r11.5 to r11.6 will cause the
error XCOMM0124E to occur. This is due to additional DSNTYPE values
that were introduced in XCOM r11.6 and which are causing XCOM r11.6
to think that the library that is being transferred is not a PDSE.
SYMPTOMS:
XCOMM0124E 192.168.19.40
#REQnnnn DATASET IS NOT A PDSE
IMPACT:
Transferring PDSE libraries from XCOM r11.5 to XCOM r11.6 will fail.
CIRCUMVENTION:
Initiate the PDSE transfers from XCOM r11.6 to XCOM r11.5.
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1093
DESC(XCOMM0124E DATASET IS NOT A PDSE SENDING FROM R11.5 TO R11.6) .
++VER (Z038)
FMID (CBXGB50)
RO27468 RO37606 RO41249 RO42214 RO52905 )
SUP ( RO50922 TR50922 TR55617 )
23

Release Service
11.5
RO55737 RO55737
M.C.S. ENTRIES
Details
= ++PTF (RO55737)

A S0C4 abend in XCOMHENJ at +051E may occur after getting a session
failure due to a TCP/IP exception if an RRQ has not been attached to the
transfer when it was terminated.
SYMPTOMS:
The following messages are displayed in the XCOMLOG:
XCOMM0780E Txpi 228: Select exception condition for socket 3
XCOMM0783E 10.126.135.210
REMOTE RECEIVE REQUEST ENDED DUE TO TCP/IP
ERROR
IMPACT:
The transfer will terminate abnormally with a S0C4 abend but the XCOM
server will remain active doing other transfers.
CIRCUMVENTION:
NONE.
PRODUCTS AFFECTED:
Star Problem(s):
XCMVS 1094
DESC(SERVER - S0C4 ABEND IN XCOMHENJ AT X'51E') .
++VER (Z038)
FMID (CBXGB50)
RO36673 RO41249 RO43694 RO47576 RO48097 )
SUP ( TR55737 )
24

Errores XCOM

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Errores XCOM

Hochgeladen von

Copyright:

Verfügbare Formate

CA XCOM Data Transport for z/OS 11.

XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0

BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API

BATCH - RETRY FAILS FOR TCPIP TRANSFERS WITH TYPE=EXECUTE

XCOMN0531E GATEWAY FAILED TO IMPORT FILE

BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I

CONTINUE EXEC PARAMETER DEFAULT VALUE CHANGED INCORRECTLY

XCOMJOBH SAMPLE FAILS WITH RC=16

BATCH - XCOMINQ STORAGE LEAK PROBLEM

DEST - TCP/IP SESSIONS MAY EXCEED DESTINATION TCPSESS

XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG

INCORRECT XCOMM0656I MESSAGE DURING XCOMJOB TYPE=INQUIRE

CA XCOM Data Transport for z/OS 11.5

XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0

CBXGJCL: UPDATE MEMBERS

BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API

BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I

BATCH - XCOMINQ STORAGE LEAK PROBLEM

XCOMJOBH SAMPLE FAILS WITH RC=16

XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG

XCOMM0124E DATASET IS NOT A PDSE SENDING FROM R11.5 TO R11.6

SERVER - S0C4 ABEND IN XCOMHENJ AT X'51E'

CA XCOM Data Transport for z/OS

XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0

CBXGJCL: UPDATE MEMBERS

BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API

BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I

BATCH - XCOMINQ STORAGE LEAK PROBLEM

XCOMJOBH SAMPLE FAILS WITH RC=16

XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG

XCOMM0124E DATASET IS NOT A PDSE SENDING FROM R11.5 TO R11.6

SERVER - S0C4 ABEND IN XCOMHENJ AT X'51E'

CA XCOM Data Transport for z/OS

XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0

BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API

BATCH - RETRY FAILS FOR TCPIP TRANSFERS WITH TYPE=EXECUTE

XCOMN0531E GATEWAY FAILED TO IMPORT FILE

BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I

CONTINUE EXEC PARAMETER DEFAULT VALUE CHANGED INCORRECTLY

XCOMJOBH SAMPLE FAILS WITH RC=16

BATCH - XCOMINQ STORAGE LEAK PROBLEM

DEST - TCP/IP SESSIONS MAY EXCEED DESTINATION TCPSESS

XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG

INCORRECT XCOMM0656I MESSAGE DURING XCOMJOB TYPE=INQUIRE

CA XCOM Data Transport for z/OS 11.6

XCOMJOB FAILS WITH XCOMM0817E BUT GETS A RC=0

CA XCOM Data Transport for z/OS 11.6

BATCH - NETDSECT NOT FREED IF XCOMJOB CALLED VIA API

CA XCOM Data Transport for z/OS 11.6

BATCH - RETRY FAILS FOR TCPIP TRANSFERS WITH TYPE=EXECUTE

CA XCOM Data Transport for z/OS 11.6

XCOMN0531E GATEWAY FAILED TO IMPORT FILE

CA XCOM Data Transport for z/OS 11.6

BATCH - TYPE=INQUIRE XTC TRANSFERS MAY GET RC=48 XCOMM0656I

CA XCOM Data Transport for z/OS 11.6

CONTINUE EXEC PARAMETER DEFAULT VALUE CHANGED INCORRECTLY

CA XCOM Data Transport for z/OS 11.6

XCOMJOBH SAMPLE FAILS WITH RC=16

CA XCOM Data Transport for z/OS 11.6

BATCH - XCOMINQ STORAGE LEAK PROBLEM

CA XCOM Data Transport for z/OS 11.6

DEST - TCP/IP SESSIONS MAY EXCEED DESTINATION TCPSESS

CA XCOM Data Transport for z/OS 11.6

XCOMM0380E NOT DISPLAYED ON RECEIVING XCOMLOG