While running the interface between Connect:Direct (C:D) and NetMaster for File Transfer Management, what can cause C:D to reject commands coming from the NetMaster region with error IEE342I MODIFY REJECTED-TASK BUSY?
search cancel

While running the interface between Connect:Direct (C:D) and NetMaster for File Transfer Management, what can cause C:D to reject commands coming from the NetMaster region with error IEE342I MODIFY REJECTED-TASK BUSY?

book

Article ID: 21854

calendar_today

Updated On:

Products

CMDB for z/OS NetSpy Network Performance NetMaster Network Automation SOLVE NetMaster Network Management for SNA NetMaster Network Management for TCP/IP NetMaster File Transfer Management SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS

Issue/Introduction

During operations of the interface between C:D and NetMaster, why C:D region may reject commands arriving from the Net-Master region, with error message IEE342I MODIFY REJECTED-TASK BUSY appearing on the C:D STC JESLOG?

 

Environment

Release: SLOPFC00200-12.1-NetMaster-File Transfer Management
Component:

Resolution

According to the C:D documentation, the cause of this problem is due to an error in the MCS.SIGNON parameter in  Sterling Connect:Direct initialization parameters.

The action to resolve this problem is:

 

  • Ensure the MCS.SIGNON parameter reflects a valid userid-password combination with Sterling Connect:Direct operator authority

  • Ensure the network map is correctly specified on the MCS.SIGNON parameter

  • Remove comments from this parameter