Binder causing BSTCOPY to fail when copying an object to a PDSe.
Release : all
Component : Endevor Software Change Manager
C1G0190W means that an error occurred during the processing of an object in a program object library (PDSE).
Usually the PDSE ran out of room to extend with reason code 83000405 Endevor will use the Binder interface during the footprint process of a loadmodule in a PDSE.
The return and reason codes are issued by the IBM Binder interface, see the 'z/OS MVS Program Management: Advanced Facilities manual' for details.
A common reported reason code is 83000405 ;
'A permanent write error was encountered while attempting to write the module. Module not saved.'
This symptom indicates that an out of space failure occurred on a PDSE.
This could occur when no secondary extents are allowed on the PDSE, or if there is no room on the volume.
Depending on the case;
Increase the PDSE allocation size, or
Free DASD space to allow secondary extents for the PDSe or move the PDSe to another DASD if there is no room on the volume.
For further diagnostic, allocate the trace "//EN$TRBND DD SYSOUT=*" in you C1BM3000 Job.
The trace will shows the IEWBIND RC and Reason Codes in the form of 83000xxx,