What to do next
When you create an
IBM i member,
a local file is created in the workspace with an extension that maps directly
to the source type. It is copied to the server the next time that you select
Push
Selected or
Push Changes. If there is already
a member of that name on the server, a conflict is detected and a warning
is issued.
Note: A conflict is defined as a push of a member where the member
on the server has been updated since the last push. If this is the first push
of this member to this server and the associated library and the member already
exists, it is assumed to be in conflict and the warning is issued.
Restriction: If you create a member with an extension and a type of *BLANK,
the extension is interpreted as the type. For example, for a member TEST.CL with
type *BLANK, the extension .CL is interpreted
as type CL. If you then attempt to create another member
with a type that matches the extension of the first member, then the new member
is interpreted as identical to the first member, a conflict occurs, and the
member will not be created. For example, TEST.CL with type *BLANK,
and TEST with type CL are considered identical
members, and both cannot exist in the same source physical file of an i Project.