Endevor Package Shipping with Direct Connect not functioning

book

Article ID: 143309

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

When shipping a package to another LPAR, the transmission is successful.  The problem happens when the attempt to write the shipped Endevor Libraries is made.  It fails and the messages are not helpful at all.  It just gives a RC=8, RN=8 from Direct Connect.

This is a new setup for Connect Direct with package ship. 

Getting messages in the JES log like these indicating that Connect Direct could not read or write to a dataset.

SDAA004I - OBTAIN TSODSN=NO DSN=BST.RICH.D200115.T113450.PRD.AH002

SDAC006I (LOCATE) - R15=0008, R0=0008, WTO of return codes from LOCATE.

IKJ56228I DATA SET BST.RICH.D200115.T113450.PRD.AH002 NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED

SDAA004I - ALLOC         DD=NDM00042 TSODSN=NO RETURN=(DSORG,DEVTYPE,371

SDAA004I -  VOL,STORCLAS,DATACLAS,MGMTCLAS)

Environment

Release : 18.0

Component : CA Endevor Software Change Manager

Resolution

This may be a Connect Direct parm error. In the above case the PNODE and the SNODE values were be incorrect. Change the Connect Direct parm error in the Endevor Skels.