CHKIN (Check In)

CHKIN Command syntax diagram

 

Purpose

The Check In (CHKIN) command checks in an object that had previously been checked out.

For more information about integrated file system commands, see the Integrated file system topic in the File systems and management category of the Information Center.

 

Restrictions

1. To check in an object that someone else has checked out, the user must own the object or have one of the following:

   • *ALL authority to the object
     
   • *ALLOBJ special authority

   
   

2. The user must have execute authority to each directory in the path.
   
3. Not all file systems support the CHKIN command.

 

Required Parameters

OBJ

Specifies the path name of the object or a pattern to match the path name or names of objects to be checked in.

The object path name can be either a simple name or a name that is qualified with the name of the directory in which the object is located. A pattern can be specified in the last part of the path name. An asterisk (*) matches any number of characters and a question mark (?) matches a single character. If the path name is qualified or contains a pattern, it must be enclosed in apostrophes.

Example for CHKIN

CHKIN   OBJ('W')

This command checks in file W in your current directory. If another user has the file checked out and this user has sufficient authority, the file is checked in.

Error messages for CHKIN

*ESCAPE Messages

CPFA09C

Not authorized to object.

CPFA09D

Error occurred in program &1.

CPFA0A1

An input or output error occurred.

CPFA0A3

Path name resolution causes looping.

CPFA0A7

Path name too long.

CPFA0A9

Object not found.

CPFA0AB

Object name not a directory.

CPFA0AD

Function not supported by file system.

CPFA0B2

No objects satisfy request.

CPFA0BE

&1 objects checked in. &2 objects failed.

CPFA0BF

&1 objects checked out. &2 objects failed.

CPFA0DA

Object name is a directory.