On our Production server, the XCOM file transfer gets rejected with error *LIBL not found. The job log is below.
It worked last night at 12:18PM and worked this Morning 09:08AM after that when we try now it failed.
Please give me a call i am ready to share my screen, we need to fix the issue with in 2 hours.
Message ID . . . . . . : CPF1269 Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 20/06/02 Time sent . . . . . . : 13:04:53
Message . . . . : Program start request received on communications device
XCOMCT1F was rejected with reason codes 605, 1518.
Cause . . . . . : The program start request was rejected in job
216556/VETRI/XCOMCT1F. The device belongs to remote location XCOMCT1F. If
the device is an advanced program-to-program communications (APPC) device,
the program start request was received on mode XCOM16K with unit-of-work
identifier FIDD.UNISEN08-D8029D764DEC-0001. The first reason code means:
Program was not found in the library specified. The second reason code
means: Problem phase program not found in QSSP.
Recovery . . . : See the job log for more information about the problem.
This message is due to the device being allocated to the wrong subsystem. To correct, this vary the device off and back on to be allocated to the correct subsystem. You should also check the iSeries QCMN subsystem to determine if the device was allocated to it.
Release : 11.0
Component : CA XCOM Data Transport for AS/400 i5/OS
Check the communication entries for the XCOM subsystem XCOM2SBS by doing a:
from the command line. Next select the option for communication entries. You should have something like the following:
Device Mode Job Description Library User Max active
XCOMDEV XCOMMODE XCOM XCOM2 XCOM *NOMAX
where XCOMDEV is the device used for XCOM transfers, and XCOM2 is the library where XCOM is installed. Make sure the user is XCOM as that is where the security violation comes from.
This problem is a result of the device being allocated to QCMN which has a default user of *SYS instead of XCOM. XCOM does not recognize this, therefore the security violation results.
If the communication entry is correct already, then you simply need to vary the device off and back on again to make sure the device is allocated to XCOM2SBS. The device can be varied on/off with the
WRKCFGSTS *DEV XCOMDEV
Once device is varied off, start XCOM2SBS using
from the command line. Once XCOM2SBS is active, use
WRKCFGSTS *DEV XCOMDEV
to vary the device on. Now device should be allocated to XCOM2SBS.
Additional message in the joblog:
CPC1116 Message . . . . : CPC1116 Program XCOMSEND in library *LIBL not found.