Errors often encountered in Coolgen

By J.D.S.Prabakaran
Download error codes:
100 Occurs when trying to download a subset which is already downloaded.
348 Occurs if any of the files used by the download job(such as userid.ief.tran,
userid.iefxlog and userid.ief.logfile) are already open during the download job. Occurred
also when the system was not able to write to the above mentioned files when there was a
SPACE problem(such as SE37). The library in issue has to be compressed.
1020 Occurs due to attribute or size mismatch of userid.ief.tran. Required attributes for
userid.ief.tran are:
1) Record Format VB
2) Record Length 4092
3) Block Size 4096
1000 Occurs if there is contention for any of the DB2 objects used by the download job.
Upload error codes:
10 (TIEC010E) Subset not found in the encyclopedia.
12 (TIEC012E) System Error: Error reading transaction file [RC=xx]. Processing
stopped before end-of-file.
13 (TIEC013E) System Error: Error processing transaction file.
32 (TIEC032E) Upload has already been done using the current userid.ief.tran.
37 (TIEC037E) Resource Conflict.
49 (TIEC049E) Occurs when upload is done using a userid which is not the checkout
userid.
56 (TIEC056E) Occurs when the subset uploaded is not the latest version.
1016 Occurs if a required DB2 resource is not available during upload.

Client Server Runtime Error messages:

TIRM729E
Type: Client/Server LU6.2/APPC Communications
This message indicates that the client application specified a program name that CICS
does not recognize.
Possible Corrective Action(s):
Verify that the transaction code is included in the proper tables on CICS.
Verify that the transaction code is associated with the correct load module. On CICS,
execute the transaction CEMT I TRA(trancode) to see the matching load module.
Check if you changed a transaction code for the server application. If so, you must
regenerate and reinstall the client window manager(s).
TIRM733E
Type: Client/Server LU6.2/APPC Communications
This message indicates that the server application abended on the host platform. The
source of the error notification is either the server application or the partner LU.
You may also see information about CICS TWALENG=0 or ABEND IEFC with this
message.
Possible Corrective Action(s):
Regenerate the server application with trace code. Reinstall the server application.
Execute the CICS transaction CEBR TRCEterminalid to browse trace code, then restart
the server application.
Note: Generate the server application with trace only if you think you have a problem in
the PAD logic. After you solve the problem, regenerate the server application without
trace code and reinstall the application. Computer Associates reserves the right to change
the current trace implementation for server applications.
Set up the transaction correctly if you receive a CICS TWALENG=0 or ABEND IEFC
message. Execute the CICS transaction CEMT for the transaction, the TWASIZE must be
8.
Ensure that the runtime module TIRENTC is copied into the CICS load library for the
server application and that TIRENTC is identified to CICS.

TIRM723E
Type: Client/Server LU6.2/APPC Communications
This message indicates that APPC cannot properly allocate a conversation. The
connection is out of service. Usually, this error indicates that something is wrong with the
host platform, but this is not always the case.
Possible Corrective Action(s):
Verify that the local LU for the workstation on which the Communication Bridge
resides is configured as an independent LU.
TIRM601E
Type: Client/Server Communications
This message indicates an error pertaining to the common format buffer. TIRM601E
applies to the host (server) platform.
This message indicates that the import view for one procedure step does not match the
export view from another procedure step. Import and export is relative to which platform
is sending and which platform is receiving.
Possible Causes:
The views are mismatched. For example, if you change the length of a work attribute for
the client application and regenerate the client application but not the server application,
the views will not match.
The generated code for client application and the server application is out of
synchronization.
The code for the server application is not bound against the DB2 session that the CICS
region can access.
Possible Corrective Actions:
Complete view matching for the application model.
Regenerate and reinstall the client application and the server application.
Ensure that none of the generated code was hand modified.
Ensure that server code is bound against the DB2 session that the CICS region can
access.

TIRM602E
Type: Client/Server Communications
This message indicates that while a Client/Server application was executing, an error
occurred on the remote (server) platform.
TIRM630E
Type: Client/Server Communications
This message indicates that the Client Manager was stopped by the user. The Client
Manager was waiting for a response from the host when it was stopped.
Possible Corrective Action(s):
Restart the Client Manager. Ensure that it is connected to the correct server.
TIRM629E
Type: Client/Server Communications
This message indicates that the Client Manager could not communicate with the server
platform on which the Communication Bridge resides.
Possible Corrective Action(s):
Ensure that the Client Manager is connected to the server on which is the
Communications Bridge resides. If not, connect to the correct server.
Ensure that the Communications Bridge is executing.
Stop and restart the Client Manager.
The following 2 errors occurred as the RI trigger was not generated.
TIRM152E
Type: Fatal Error
Referential Integrity checking is preventing the deletion of this record occurrence. The
record occurrence to be deleted is protected by the Deletion Rule property of a
relationship membership in which it participates. The Deletion Rule is set to disallow the
deletion of this record occurrence because it has a relationship with an occurrence of
another entity type. The relationship may be direct, or it may be related by cascading.

TIRM154E
Type: Fatal Error
A view was not populated under one of the following conditions:
1)
In a READ qualified by a WHERE clause that uses CURRENT OF views, the
view that should be CURRENT has not been read or has gone out of scope.
2)

A view for an UPDATE has not been populated and locked.

3)
An action block that uses a persistent view was called without the view being
populated and the action block attempted to use the view in a READ, UPDATE,
ASSOCIATE, DISASSOCIATE, or TRANSFER.
4)
One or more of the views in an ASSOCIATE or TRANSFER statement has not
been populated.
Correct the action diagram. Usually there is a flow of control where a READ has not
been performed but has been assumed.
CSU-ERROR
Occurs when the client manager is closed after the client window is opened and an
attempt is made to connect to the server.
Consistency Check Error Messages:
ICCEN08E
A CURRENT persistent relationship view used in a WHERE expression must be
properly populated. The view has not been populated by a READ or CREATE action.
File Error Messages:
FIL301: Invalid file name given.
Can Occur in CreateTextFile, DeleteFile, FileExists, FileLength, Launch,
OpenTextFile
Cause
Recovery

The given file name is an empty string.

Provide a non-empty file name string.

FIL302: File already exists. Cannot create.

Can Occur in CopyFile, CreateTextFile, RenameFile

Cause
An attempt has been made to create a file that already exists.
Recovery Use the FileExists function to determine if the file has been created before
trying to create it.
FIL303: File does not exist. Cannot open.
Can Occur in OpenTextFile
Cause
An attempt has been made to open a file that did not exist.
Recovery Use the FileExists function to determine if the file exists before attempting
to open it. You may want to add logic that attempts to open a file and, if the file does not
exist, creates it.
FIL305: Cannot open file.
Can Occur in FileLength, OpenTextFile
Cause
The file may already be opened by this or another application with an
incompatible share mode (that is, the file is locked by the application that owns it.)
Recovery If the file must be accessed, exit all other applications and close all files
opened by the application.
FIL307: File specified is open for read operations only.
Can Occur in PutText
Cause
The file was opened for read only operations. The PutText function writes to
a file.
Recovery Close all numbers associated with the file and re-open the file for write access
before using the PutText function.
FIL308: File specified is open for write operations only.
Can Occur in GetText, PositionFile
Cause
The file was opened for write operations. The GetText and PositionFile
functions are read operations.
Recovery Review the action statements for the intent of the function used. The file may
need to be closed and reopened for read.
FIL309: File write operation failed. Check file.
Can Occur in PutText
Cause 1 An attempt was made to write to the file with the PutText function. There
may not be enough disk space available to write the file.

Recovery Remove files from the drive to make space or write to a drive that has
sufficient enough space.
Cause 2 An attempt was made to write to the file with the PutText function. If the file
was on a remote server or floppy, the server or floppy may have become unavailable
during the operation.
Recovery Check the access to the floppy or server drive.
FIL310: An internal file operation failed.
Can Occur in CloseFile, CopyFile, FileLength, RenameFile
Cause
An attempt was made to close or rename a file and an internal error occurred.
Recovery None.
FIL311: File does not exist.
Can Occur in CopyFile, DeleteFile, FileLength, RenameFile
Cause
An attempt was made to delete, copy, or find the length of a file that did not
exist.
Recovery Check the file name to determine if it is the intended one.
FIL312: File is open.
Can Occur in DeleteFile, RenameFile
Cause
An attempt was made to delete a file that is already open by this or another
application.
Recovery Close all instances of the file before deleting it.
FIL313: Read past end of file.
Can Occur in GetText, PositionFile
Cause
An attempt was made to read past the end of the file.
Recovery
It is a common programming practice to attempt to read past the end of the
file to determine that all the data has been read. The application should contain logic to
handle the end of file condition.
FIL315: File seek operation failed. Check file attributes.
Can Occur in CreateTextFile, OpenTextFile, PositionFile
Cause
When positioning to the end of the file using OpenTextFile, PositionFile, or
a CreateTextFile, a seek error was encountered. When positioning to the beginning of
the file using PositionFile, a seek error was encountered.

Recovery Review file you are attempting to use.