If you're running on Linux the first thing to check is the file permissions. Make sure the user running the program can create files in that folder.

Hi Shubham,

Which release of UniVerse are you running?

I noticed that the error references "ARC.XCOM" but the code is using "ARC.XC". Does ARC.XCOM exist on the subscriber?

Thanks,

Neil

Hi Neil,

Thanks for your response.

We are using UniVerse 11.4.1. Please ignore ARC.XC, it is actually ARC.XCOM and yes, it does exist in subscriber.

------------------------------
Shubham Nigam
Rocket Forum Shared Account
------------------------------

Hi Shubham,

I performed a quick test on a couple of Unix systems running 11.3.5 and didn't encounter any problems. I don't believe anything was modified with this functionality in 11.4.1. The only things I can think of are:

• Permissions issue on the ARC.XCOM directory/folder on the subscriber?
• Not having a valid VOC pointer for ARC.XCOM on the subscriber?
• Having the sequential file already existing in the ARC.XCOM directory/folder on the subscriber?

Are you able to use the EDitor to create a new record in the ARC.XCOM directory/folder on the publisher and have it created successfully on the subscriber? The CREATE operation would essentially be doing the same thing. Might provide some clue if it also has a problem. Or indicate the issue is specific to the CREATE operation.

Thanks,

Neil

Shunham,

When checking permissions, please also check ACLs. If in use then I suggest removing them on the directory concerned ( at least temporarily ). Then set the directory permissions using chgrp for the right group as used by uniVerse and set rwx the group and add chmod g+s to make permissions inheritable. You will also want to 'fox' the ownership and permissions of any files currently in the direcctory as well.

I think native support for ACLs was added at version 12, though Neil can correct me on this if needed.

Regards

JJ 

Thanks all for your suggestions.
As per Rocket documentation: "In order to replicate a sequential file, the directory or folder in which the sequential file resides must be a replication object" but in our case even though the program resides in replicable object but we are writing the sequential file on non-replicable object thus causing replication failure.

Shubham,

More than one entry in a VOC for the same file and falling foul of an exclusiom rule possibly?

Regards

JJ