file create failed

[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