ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

C1G0600C PROGRAM OBJECT FOOTPRINT ERROR, due to IEWBIND Reason code 83000405

book

Article ID: 49007

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS PanAudit Plus Easytrieve Report Generator PAN/SQL Endevor Software Change Manager (SCM) Endevor Software Change Manager - Natural Integration (SCM) Endevor Software Change Manager - ECLIPSE Plugin (SCM) Endevor Software Change Manager - Enterprise Workbench (SCM) CA 2E

Issue/Introduction

Description:

'C1G0600C PROGRAM OBJECT FOOTPRINT ERROR' means that an error occurred during the footprinting of a member in a program object library (PDSE).

For additional diagnostics add a //EN$TRBND DD SYSOUT=* trace statement.

Usually the PDSE ran out of room to extend with reason code 83000405 .

Solution:

'C1G0600C PROGRAM OBJECT FOOTPRINT ERROR' means that an error occurred during the footprinting of a member in a program object library (PDSE). For additional diagnostics add a //EN$TRBND DD SYSOUT=* trace statement. 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 following trace DD will provide additional diagnostics; like the IEWBIND RC and Reason Codes in the form of 83000xxx.

//EN$TRBND DD SYSOUT=*

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.

Note; don't use IEBCOPY to redefine or copy the PDSE, since *LOADMOD footprints will be lost.
See Technote TEC316937 for a technique using BSTCOPY.

Environment

Release:
Component: C21E