Message C1LB016C for Endevor base library behaves differently depending on the location
search cancel

Message C1LB016C for Endevor base library behaves differently depending on the location

book

Article ID: 99527

calendar_today

Updated On:

Products

Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench

Issue/Introduction

The meaning of message C1LB016C "MEMBER NAME = name CONTAINS INVALID CHARACTERS" is rather clear. The store of a member in a library is failing as the member name is invalid.

You may receive this message related to base or source output libraries. Member names in delta libraries are generated by Endevor and are always valid

Depending on the setup, you could have an element successfully added in one stage and receive this message for the base library when moving the element up the map.

How can it happen?

Environment

Release: ENDAE.00200-18.0-Endevor-Software Change Manager
Component:

Cause

The message is related to the  Endevor/Lib (ELIB) library structure, which is more restrictive than PDS regarding member names.

Member names in ELIB libraries can only contain:

  • Uppercase letters (A-Z)
  • Digits (0-9)
  • Dollar sign "$" (EBCDIC 0x5B)
  • Numeral sign "#"(EBCDIC 0x7B)
  • 'at' sign "@" (EBCDIC 0x7C

It may be surprising to see this message in the target stage of a MOVE action, but this may happen, for example, if all the following conditions are true

  • The base library at the source stage is a PDS
  • The base library at the target stage is an ELIB
  • The type definition sets that the base member name is not encrypted (so it matches the element name) 
  • The element name contains lowercase characters

When this happens, Endevor had stored without any error the member with a name matching the element name (having lowercase characters) in the base PDS library when the element raised the source stage. Then, the MOVE tried to store the base member in the base ELIB at the target stage which raised the error.

Resolution

This situation may be addressed by either:

  • Using a PDS as the base library for the target stage
  • Changing the type definition to specify COMPRESS BASE/ENCRYPT NAME so that the name of the base member is generated by Endevor