BSTCOPY not working in CA Endevor processors. Getting the following error: C1X0500E INVALID SYNTAX IN INPUT DATA

book

Article ID: 5477

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

Updating the Generate and Move processors to include a BSTCOPY step.

Copied the BSTCOPY processor example shown in the Extended Processors Guide but getting the following error:

C1X0511I COP I=ILIB,O=OLIB

C1X0500E INVALID SYNTAX IN INPUT DATA 

Cause

The most common reason for a C1X0500E error in BSTCOPY or BSTXCOPY is the SYSIN control statements are starting in column 1. 

Environment

Release:
Component: ENDBAS

Resolution

Check the SYSIN control statements and verify they are not starting in column 1.

If they start in column 1, move them over a couple of spaces and retest. 

If the control statements are not starting in column 1, please open a CA Support Online request and attach the complete output from the processor execution or the BSTXCOPY job.  

Additional Information

For more information about BSTCOPY and BSTXCOPY, please refer to the CA DocOps site.

BSTCOPY - 

+Administrating

+Extended Processors

- Processor Utilities

 

BSTXCOPY -

+Administarting

- BSTXCOPY Utility Copies Between Load Libraries