Archives of the TeradataForum

Message Posted: Tue, 21 Aug 2001 @ 19:29:06 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

John pointed in the right direction:

examples of this error:

UTY4014 Access module error '34' received during 'file open' operation: 'pmUnxDskOpen : fopen error

UTY4014 Access module error '7' received during 'get position' operation: 'Invalid pmFp parameter'

UTY4015 Access module error '34' received during 'read' operation on record number '0': 'PMMFRD: MFILOC FAILED, MFI rc=20'

Probable Cause:
Teradata Utility Message Manual states " An error was encountered during a call to the current access module. Generated by: UTYIO" Could be cause by several I/O conditions relating to the file being read or the file being written. For example the above fopen error could occur because the job does not have permission to open or create a file. A write error could occur because the ulimit (usually 32MB) has been exceeded or the disk has run out of free space.

Other possible causes:

- Invalid file name

- Any file I/O error

- tape positioning error

- file seek error

- there have been some DR's opened to address problems opening empty files

Error can occur in any OS; MVS, UNIX, NT

This is a Teradata Utility error message.

Solution:
Correct the I/O problem and resubmit the job. For example setting the permissions to allow write access to the user or increasing the ulimit (UNIX file size limit). Possibly correct the input or output file syntax.

Regards,

Ysbrand

Ysbrand Bergman
Support Specialist
EMEA RTS
NCR Worldwide Customer Services

	<Prev	Next>		<<First	<Prev	Next>	Last>>