file create failed

[adarsh_4]

we have application written in gembase v7.2 running on vms v7.3, when ever this user submits a job to a batch que through one of our application, the following error occurs.

terminated with error status

%RMS-E-CRE, ACP file create failed

please advise.

[RBrown_1]

>>>>
terminated with error status

%RMS-E-CRE, ACP file create failed
<<<<

Where does this error appear? In the batch log? On the submitting user's terminal? Immediately? After a delay? Has is ever worked?

If it appears on the submitter's terminal immediately, I would suspect a problem in your application, and run it in the debugger to see what is going on.

[Richard J Maher]

Hi Adarsh,

The secondary error status/message is the one you want. (i.e. Why the create failed) But I'll take a punt on either Insufficient Privilege or invalid directory.

What is the file-spec being opened?

Are logical names different in batch than interactive?

Does the login.com behave differently on f$mode() etc

Is the batch username different than the interactive username?

Cheers Richard

[Jon Pinkley]

adarsh,

My guess is that the job is being submitted with a logfile specified, and this logfile can't be created by the username the batch job is executing from.

There are multiple possible reasons. Here are some.

insufficient space (device full, quota exceeded - will not use overdraft)
output directory not found
directory full and can't be extended due to lack of contiguous space
highest legal version (;32767) of log file already exists
user does not have write access to directory.

See my post dated Jun 6, 2010 22:28:04 GMT in the thread

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1433428

Jon

[Andy Bustamante]

Jon has a very nice reply above. I'll add has a disk been filled to capacity or failed? In addition,

Did this ever work?

Has something been changed?

Does this work for user A and not user B?

[P Muralidhar Kini]

Hi Adarsh,

As others have already mentioned, you need to provide the complete
error message i.e. the secondary error message and also give some details
about the application.

Jon has nicely listed out a number of reasons for the failure,
My guess would be
>> insufficient space (device full, quota exceeded - will not use overdraft)

But then you need to give more information about the application before
we find out the cause for the problem.

Did the application ever work ?
Does the application work if submitted by another user ?
Which disk does the application use and how much free space does it have ?

If there is a logfile created by the applicaiton, you can provide that as a
attachement.

Hope this helps.

Regards,
Murali

[adarsh_4]

thank u every1 for replying. there is no log file for this because the job gets terminated from the queue b4 the job can run. this was working before but now its not working for any1. below is the error in full

Job POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH (queue FIN$BATCH, entry 1176) terminated with errorstatus |
%RMS-E-CRE, ACP file create failed

i did not get any other error.50G of space still available and the user was granted bypass but still no luck.

we also did not make any changes to the system.

[adarsh_4]

i did a set que/retain=error on the batch que and submitted the job again, the error i got this time is below. i guess this the secondary error every1 was asking for.

%RMS-E-CRE, ACP file create failed
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILENAME, bad file name syntax


please advise

[P Muralidhar Kini · Accepted solution]

Hi Adarsh,

>> 50G of space still available and the user was granted bypass but still no
>> luck.
Does not look like a disk space problem.

>> %RMS-E-CRE, ACP file create failed
>> -RMS-E-CRE, ACP file create failed
>> -SYSTEM-W-BADFILENAME, bad file name syntax
The secondary error message here is "SYSTEM-W-BADFILENAME".
Looks like the application
either
tried to create a file with illegal characters in it
or
tried to create a file with name longer than the maximum allowed limit.

The help message for the above error is as follows -
$help/message BADFILENAME
BADFILENAME, bad file name syntax

Facility: SYSTEM, System Services

Explanation: This message is associated with a status code returned from a
file system ACP QIO request. The file name string for a file
specification contains illegal characters or is longer than 39
characters.

User Action: Check for a programming error. Verify that the file name
strings consist only of the characters A through Z and 0
through 9, and are no longer than nine characters.

Next step is to find out which source line in the application is throwing the above error -

What you need to do now is to modify the application by adding print
statements. (i.e. $write sys$output "..."). Then run the application, look at the
print statements that have got printed before the error message is displayed.
This way you should be able to locate the exact line in the application that is
throwing up the above error message.

>> thank u every1 for replying.
Refer the following link which says how you can thank the forum -
http://forums13.itrc.hp.com/service/forums/helptips.do?#28

Hope this helps.

Regards,
Murali

[Steven Schweda]

> -SYSTEM-W-BADFILENAME, bad file name syntax

help /mess BADFILENAME /faci = system

Am I missing something obvious, or have
you not shown us the actual failing command?

With my weak psychic powers, I can't see the
bad file name from here. You're probably
closer than I am. Perhaps you could look,
and report back what you find.

[Hein van den Heuvel]

Allright. That helps some. Good work.

Just shorten those job names some and be happy.

That job name itself is long ( 36 ) characters, but valid as a file_name, because the max is 39 characters for name and for extensions each.

But I suspect a piece of string is added for the log file name.

Please study (or share here) the output from SHOW ENTRY xxx/FULL.

Look at the COM file name and LOG file names.
How long is that log file?

I suspect GEMBASE is submitting the job with an explicit, and bad, log file name.

Without writing a program I can reproduce the error in a SILLY way, but highlighting the likely error cause:

$ define/system POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH_12345

$ subm/noti /nam=POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH tmp.com/retain=error

$ show entry 195 /full
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
195 POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH
HEIN Retained on error
%RMS-E-CRE, ACP file create failed
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILENAME, bad file name syntax
On idle batch queue SYS$BATCH
Submitted 29-JUN-2010 22:05:53.62 /KEEP
/LOG=xxx:[HEIN]POP_R_PURCHASES_BY_VENDOR_BY_D_BATCH_12345.LOG; /NOTIFY /NOPRINT /PRIORITY=100
/RETAIN=ERROR
File: xxx:[HEIN]TMP.COM;32
Completed 29-JUN-2010 22:05:53.65 on queue SYS$BATCH


Good luck,
Hein

[P Muralidhar Kini]

Hein,

>> Without writing a program I can reproduce the error in a SILLY way,
>> but highlighting the likely error cause:
Thats a nice catch.

I had also tried the same thing on a V73-2 node but did not get a error.
May be the VMS version matters...

Regards,
Murali

[adarsh_4]

thanks every1, the name of the log file to be created was longer than 39. thanks Mr Hein, i was also counting 36 until u showed an example by adding extra characters.i debugged the program and found out that the username is later added to the file name and it makes it more than 39 characters.

thanks every1. take care and god bless

[P Muralidhar Kini]

Hi Adarsh,

Good to know that your problem is resolved.

Also,
>> we have application written in gembase v7.2 running on vms v7.3
Looks like you are using OpenVMS V7.3 Alpha.
I would recommend you to upgrade to supported version of OpenVMS i.e.
OpenVMS V73-2 or onwards.

This way you would be able to get patches with fix for all the known problem
that are reported and fixed so far.

Hope this helps.

Regards,
Murali