IBM Mainframe Forum

does anyone have a way for me to accomplish this.

but d.sch.
since you asked the original file is being edited with updateds by user from another group. the current process is when one person is in there doing updates the others must wait. also NO ONE can be in file when certain SAS jobS are running which uses data from this file.

so I have created IPSF PANELS using CLIST in which a user would click on certain options and will take them to the file MAKE A COPY OF IT AND OPEN IT IN EDIT MODE.
once the user saves the changes then im going to use code logic to check for errors (AS THERE IS A NAMING STANDARD USED IN THIS FILE)

THEN I WILL USE SUPERC to compare the copy and original and add the changes to the original file. SO THIS WAY MULTIPLE USERS CAN HAVE A COPY AND CHANGES WILL BE SAVED LATER. and then deleted
hope this answer ur question also

THIS WILL ALL BE ACCOMPLISHED USING CODE NO MANUAL PROCESS

Hello,

THEN I WILL USE SUPERC to compare the copy and original and add the changes to the original file. SO THIS WAY MULTIPLE USERS CAN HAVE A COPY AND CHANGES WILL BE SAVED LATER. and then deleted
hope this answer ur question also

THIS WILL ALL BE ACCOMPLISHED USING CODE NO MANUAL PROCESS

Before this is ever released to someone to use, suggest you make a couple of backup copies of any pds involved. . .

What you propose will only automate the corruption of the primary library. If 5 users are able to make changes to the same module, it will not take long before some user makes a change that destroys some other user's recent modification. Keep in mind that multiple users will make changes to the same parts of the code and there will be no way for the process to determine which change should take precedence.

For example, if Fred makes a change on Monday, and Mary makes a change on Tuesday and promotes this and you make a change on Wednesday and promote your change, then Fred promotes his change, your change and Mary's change will be undone or broken.

A most important part of products like Endevor and Changeman are to protect against this very problem (multiple updates to the same source).

how about create a temp pds with the user id attached to it like sysuid when they click on that option.

Hello,

The problem is the re-integration of several sets of changes back into the main module. There is no way for superc or any other system utility to make the decision which code of multiple sets of changes is what should be currently in the main module. The most recent is not necessarily the correct code at the time.

Suggest someone become the coordinator for these modules and only update the main module by integrating whatever changes are deemed to be part of the next update. Each user would have their own module to work on independently and they should be able to test independently (unless there are data allocation issues as well).

One way to cut down the allocation problems would be to make a library/member that is only used by production jobs. When an update to this member was needed, it would be when no production was scheduled/running.

ok maybe im wording this wrong.

I need example code on how I can make a new pds using the userid part of the naming convention