RE: [U2] New UV Accout VOC
Bill (and Will), As I stated I have done the directory copy many times with great success. It is not that difficult, but you have to be CAREFUL. See my earlier posts for some caveats to the process. As to the size of the files, Will has a point, but disk space is cheap. Also, if you are testing code having a full copy of the production data will allow you to better test your changes without having to recreate lots of master file data. At unix the process to copy an account located at /software/production to a sandbox account would be something like: Cp -R /software/production /software/sandbox You would then create a new UV account and point it at this new directory. I will repeat three major items to look out for in this process. 1) files with indexes as the index pointer is in the file header 2) Q-pointers and remote file pointers (F pointers with full paths to the file) as they will like still be pointing at the live account 3) Globally cataloged programs. If your 'sandbox' account is on the same box as the production account you should NEVER globally catalog from within your sandbox area. This will make your changes active everywhere which is probably not what you intended. >I think you might even be able to just copy the whole directory, but > I've > never actually done it that way myself. In general, for a test account > you > don't really need files with a modulo of a hundred thousand and its > pointless to > create them and then have to DELETE-FILE and CREATE-FILE fifty times ... > in > my opinion. >Creating a sandbox account isn't real easy. You should have saved the > headaches and just hired me ;) > Will Johnson > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] New UV Accout VOC
Goo'day, Bill and Will At 01:41 10/08/05 -0400, you wrote: In a message dated 8/9/2005 8:04:38 AM Pacific Daylight Time, [EMAIL PROTECTED] writes: > ED VOC FILENAME > > 1: F > 2: FILENAME > 3: D_FILENAME > > 3. Thus, further commentary would be appreciated. > > --Bill Bill these sorts of "F" pointers where attribute 2 is some short thing like MONKEY001 instead of something long like D:\mydir\myotherdir\mymonkey are relative path names. The files they point at, must be present in the local directory of the account. What you've done is copy the File Pointers, but not the files themselves. For each of these files, you need to do a CREATE-FILE MONKEY or whatever the file is named. That will allow you to create these files in a test location with sizes other than what production has. E... Not quite a complete enough explanation, Will.. You'll have to delete the Q-Pointers first, before you CREATE.FILE for a file with the same name otherwise you'll get this response: >CREATE-FILE PLTRANS 1 1 "PLTRANS" is already in your VOC file as a type "Q" record. File not created. > Ergo, failure! -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.10.5/67 - Release Date: 09/08/05 Regards, Bruce Nichol Talon Computer Services ALBURYNSW 2640 Australia http://www.taloncs.com.au Tel: +61 (0)411149636 Fax: +61 (0)260232119 If it ain't broke, fix it till it is! -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.10.5/67 - Release Date: 09/08/05 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] New UV Accout VOC
In a message dated 8/9/2005 8:04:38 AM Pacific Daylight Time, [EMAIL PROTECTED] writes: > ED VOC FILENAME > > 1: F > 2: FILENAME > 3: D_FILENAME > > 3. Thus, further commentary would be appreciated. > > --Bill Bill these sorts of "F" pointers where attribute 2 is some short thing like MONKEY001 instead of something long like D:\mydir\myotherdir\mymonkey are relative path names. The files they point at, must be present in the local directory of the account. What you've done is copy the File Pointers, but not the files themselves. For each of these files, you need to do a CREATE-FILE MONKEY or whatever the file is named. That will allow you to create these files in a test location with sizes other than what production has. If you want exact duplication of ALL data, then you can simply ACCOUNT-SAVE PRODUCTION and then ACCOUNT-RESTORE SANDBOX or something like that. I think you might even be able to just copy the whole directory, but I've never actually done it that way myself. In general, for a test account you don't really need files with a modulo of a hundred thousand and its pointless to create them and then have to DELETE-FILE and CREATE-FILE fifty times ... in my opinion. Creating a sandbox account isn't real easy. You should have saved the headaches and just hired me ;) Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
Sometimes this can be dangerous. We had a routine to open files in a common area. We had a live account in one directory and a test in another. If you switched back and forth between live and test you were still pointing to the same files. We had to create a 'close files' routine when switching back and forth. Anyway, we no longer share test and production on the same machine. Equipment is so cheap these days we bought a test server. Be careful ! Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 11:42 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC The problem here is that anything in the PRODUCTION voc that looks like <1>F <2>FILENAME <3>D_FILENAME will need to be changed in the SANDBOX account to <1>Q <2>PRODUCTION <3>FILENAME this is because these are actual files in the PRODUCTION account and they dont exist in the SANDBOX account, so you need to change these file defintions to pointers which tell you where the actual file is h [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/08/2005 15:58 Please respond to u2-users@listserver.u2ug.org To u2-users@listserver.u2ug.org cc Subject RE: [U2] New UV Accout VOC Will's answer is quite excellent but... 1. The SandBox VOC needs to know about files. So, I did something similar like... SELECT MYPOINTER WITH F1 = "F" COPY FROM MYPOINTER TO VOC SELECT MYPOINTER WITH F1 = "PA" COPY FROM MYPOINTER TO VOC 2. The first program that I tried ran OK. The second and third programs ended abnormally with messages like... "Improper data type" when trying to read a record from a file newly defined in the SANDBOX VOC... like read R.Record from F.FileName else R.Record = '' I suspect that it has to do with line three of the following... ED VOC FILENAME 1: F 2: FILENAME 3: D_FILENAME 3. Thus, further commentary would be appreciated. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, August 08, 2005 7:23 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] New UV Accout VOC Bill. From your sandbox account create a Q-pointer to your production account like this. Let's say the production account is called PRODUCTION ED VOC MYPOINTER NEW ITEM TOP .I 001 Q 002 PRODUCTION 003 VOC 004 .FI 'MYPOINTER' filed Now do this SELECT MYPOINTER WITH F1 = "V" 963 items selected COPY MYPOINTER TO: (VOC This should copy all the missing 'verbs' from PRODUCTION to SANDBOX. Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of George Gallen Sent: Tuesday, August 09, 2005 11:43 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC Bill, you copied the VOC to the account (and a new unix directory I'm assuming) but...the actual FILE and contents were not copied, only the VOC entry. 1. delete the VOC entry delte the VOC in the sandbox account, do not DELETE anything in the production account :) 2. CREATE-FILE FILENAME (1/19/30 - your choice) (in the sandbox) 3. LOGTO production 4. Create a Q pointer (QPFILE) in the VOC called NEWFILE <1>Q <2>sandbox-account-name <3>FILENAME just to clarify: Create a Q pointer in the VOC called QPFILE with <1>Q <2>sandbox-account-name <3>FILENAME 5. COPY FROM FILENAME TO QPFILE ALL COPY FROM DICT FILENAME TO DICT QPFILE ALL You will need to do that for all VOC entries in production that have F1 like "F..." Oh and one other thing. Before you go ANY further...make sure you a valid backup, not just a tape, but attempt to "restore" a file that doesn't not exist, so you know the tape is fully readable, and doesn't bomb out half way through the restore attempt (*** big time important ***) George - --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
I wouldn't change them to Q pointers. Otherwise the sandbox account will CHANGE the data in the PRODUCTION account, you need to copy them to the new account so you have your own files to muck with. George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 11:42 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC The problem here is that anything in the PRODUCTION voc that looks like <1>F <2>FILENAME <3>D_FILENAME will need to be changed in the SANDBOX account to <1>Q <2>PRODUCTION <3>FILENAME this is because these are actual files in the PRODUCTION account and they dont exist in the SANDBOX account, so you need to change these file defintions to pointers which tell you where the actual file is h [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/08/2005 15:58 Please respond to u2-users@listserver.u2ug.org To u2-users@listserver.u2ug.org cc Subject RE: [U2] New UV Accout VOC Will's answer is quite excellent but... 1. The SandBox VOC needs to know about files. So, I did something similar like... SELECT MYPOINTER WITH F1 = "F" COPY FROM MYPOINTER TO VOC SELECT MYPOINTER WITH F1 = "PA" COPY FROM MYPOINTER TO VOC 2. The first program that I tried ran OK. The second and third programs ended abnormally with messages like... "Improper data type" when trying to read a record from a file newly defined in the SANDBOX VOC... like read R.Record from F.FileName else R.Record = '' I suspect that it has to do with line three of the following... ED VOC FILENAME 1: F 2: FILENAME 3: D_FILENAME 3. Thus, further commentary would be appreciated. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, August 08, 2005 7:23 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] New UV Accout VOC Bill. From your sandbox account create a Q-pointer to your production account like this. Let's say the production account is called PRODUCTION ED VOC MYPOINTER NEW ITEM TOP .I 001 Q 002 PRODUCTION 003 VOC 004 .FI 'MYPOINTER' filed Now do this SELECT MYPOINTER WITH F1 = "V" 963 items selected COPY MYPOINTER TO: (VOC This should copy all the missing 'verbs' from PRODUCTION to SANDBOX. Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
Bill, you copied the VOC to the account (and a new unix directory I'm assuming) but...the actual FILE and contents were not copied, only the VOC entry. 1. delete the VOC entry 2. CREATE-FILE FILENAME (1/19/30 - your choice) (in the sandbox) 3. LOGTO production 4. Create a Q pointer (QPFILE) in the VOC called NEWFILE <1>Q <2>sandbox-account-name <3>FILENAME 5. COPY FROM FILENAME TO QPFILE ALL COPY FROM DICT FILENAME TO DICT QPFILE ALL You will need to do that for all VOC entries in production that have F1 like "F..." George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brutzman, Bill Sent: Tuesday, August 09, 2005 10:58 AM To: 'u2-users@listserver.u2ug.org' Subject: RE: [U2] New UV Accout VOC 2. The first program that I tried ran OK. The second and third programs ended abnormally with messages like... "Improper data type" when trying to read a record from a file newly defined in the SANDBOX VOC... like read R.Record from F.FileName else R.Record = '' I suspect that it has to do with line three of the following... ED VOC FILENAME 1: F 2: FILENAME 3: D_FILENAME 3. Thus, further commentary would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
The problem here is that anything in the PRODUCTION voc that looks like <1>F <2>FILENAME <3>D_FILENAME will need to be changed in the SANDBOX account to <1>Q <2>PRODUCTION <3>FILENAME this is because these are actual files in the PRODUCTION account and they dont exist in the SANDBOX account, so you need to change these file defintions to pointers which tell you where the actual file is h [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/08/2005 15:58 Please respond to u2-users@listserver.u2ug.org To u2-users@listserver.u2ug.org cc Subject RE: [U2] New UV Accout VOC Will's answer is quite excellent but... 1. The SandBox VOC needs to know about files. So, I did something similar like... SELECT MYPOINTER WITH F1 = "F" COPY FROM MYPOINTER TO VOC SELECT MYPOINTER WITH F1 = "PA" COPY FROM MYPOINTER TO VOC 2. The first program that I tried ran OK. The second and third programs ended abnormally with messages like... "Improper data type" when trying to read a record from a file newly defined in the SANDBOX VOC... like read R.Record from F.FileName else R.Record = '' I suspect that it has to do with line three of the following... ED VOC FILENAME 1: F 2: FILENAME 3: D_FILENAME 3. Thus, further commentary would be appreciated. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, August 08, 2005 7:23 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] New UV Accout VOC Bill. From your sandbox account create a Q-pointer to your production account like this. Let's say the production account is called PRODUCTION ED VOC MYPOINTER NEW ITEM TOP .I 001 Q 002 PRODUCTION 003 VOC 004 .FI 'MYPOINTER' filed Now do this SELECT MYPOINTER WITH F1 = "V" 963 items selected COPY MYPOINTER TO: (VOC This should copy all the missing 'verbs' from PRODUCTION to SANDBOX. Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
Will's answer is quite excellent but... 1. The SandBox VOC needs to know about files. So, I did something similar like... SELECT MYPOINTER WITH F1 = "F" COPY FROM MYPOINTER TO VOC SELECT MYPOINTER WITH F1 = "PA" COPY FROM MYPOINTER TO VOC 2. The first program that I tried ran OK. The second and third programs ended abnormally with messages like... "Improper data type" when trying to read a record from a file newly defined in the SANDBOX VOC... like read R.Record from F.FileName else R.Record = '' I suspect that it has to do with line three of the following... ED VOC FILENAME 1: F 2: FILENAME 3: D_FILENAME 3. Thus, further commentary would be appreciated. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, August 08, 2005 7:23 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] New UV Accout VOC Bill. From your sandbox account create a Q-pointer to your production account like this. Let's say the production account is called PRODUCTION ED VOC MYPOINTER NEW ITEM TOP .I 001 Q 002 PRODUCTION 003 VOC 004 .FI 'MYPOINTER' filed Now do this SELECT MYPOINTER WITH F1 = "V" 963 items selected COPY MYPOINTER TO: (VOC This should copy all the missing 'verbs' from PRODUCTION to SANDBOX. Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
As a general statement, want you are doing is not something you want to experiment with unless you have a completely separate development machine to work with that you can refresh if you mess it up. You need to have a much better understanding of the file structure used by your application before proceeding further. See additional responses below: > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Brutzman, Bill > Sent: Monday, August 08, 2005 3:34 PM > To: 'u2-users@listserver.u2ug.org' > Subject: RE: [U2] New UV Accout VOC > > [1] An example Q Pointer would help. It seems the downside to using > Q-Pointers is that we > would need a few hundred of them. On the other hand, for a SAND-BOX, > the Q-Pointers could > be added as needed. You miss-understand me. When you copied the VOC from another account it may have/probably contained Q-pointers that were valid for the production account. For example if you have a CORPORATE account with a file called GL there might have been a pointer that looked like: Q CORPORATE GL This would be potentially disastrous in your SANDBOX account as any writes performed to GL would up the live account. You should NEVER have a Q-pointer to a application file in the production/live account(s). In this scenario you would want to also create a SANDBOX-CORPORATE that is a copy of CORPORATE and change the Q-pointer in your. > > [2] I copied NEWACC to NEWACC.BAK and then overwrote NEWACC with VOC and > then ran > UPDATE.ACCOUNT. Doing so did not work. A message came back saying... > "The following records appear in NEWACC but not in VOC." Of course, > these well > all of the records that we need. > I am not sure what you are trying to accomplish here. The NEWACC file is the repository for UV to keep the VOC entries it needs/wants in a clean account. Basically, you should NOT be doing what you did. As I said before my preferred method is to copy the account at the OS level then do an UPDATE.ACCOUNT to be sure the UV entries are correct for the development system. Alternatively you could have setup a new account, which would already have a clean VOC install. Then create a Q-pointer to the other VOC file and copy the entries from the Q-pointer with NO OVERWRITE. If there are any conflicts make a note of them and deal with them manually. > [3] While our baseline ERP system is from www.GRMS.com, most of what we > use > is homegrown. > I am not familiar with them so I can't help there. > [4] Copies of VOC appear in half a dozen different places. When I change > VOC in our baseline > system, I can see the date change on the HP-Ux side. I was hoping > that > the only VOC that > matters is the one under the account itself. > Again, this is dependant on the application. If you are not familiar with the account structure this software you should contact your vendor before attempting something like this!!! > [5] I am unable to get change directories to get to > /u2/METAL/&TEMP&/NEWACC > and > > /u2/SANDBOX/&TEMP&/NEWACC to try the above > procedure. > > [6] Somehow our production system knows that the compiled code lives > here > > /u2/METAL/SOFTWARE/ACC.BPAccounting Code > /PUR.BPPurchasing Code > ... /etc etc > > while the data files are in... > > /u2/METAL/* > > Further suggestions would be appreciated. > > Thanks to those who responded... > > --Bill Brutzman > Manager, IT > HK MetalCraft Mfg Corp > PO Box 775 > 35 Industrial Road > Lodi NJ 07644-0775 > > [EMAIL PROTECTED] > > 973.471.7770 x145 .voice > 973.471.9666 .fax Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] New UV Accout VOC
In a message dated 8/8/05 12:40:47 PM Pacific Daylight Time, [EMAIL PROTECTED] writes: << I copied NEWACC to NEWACC.BAK and then overwrote NEWACC with VOC and then ran UPDATE.ACCOUNT. Doing so did not work. A message came back saying... "The following records appear in NEWACC but not in VOC." Of course, these well all of the records that we need. >> Bill. From your sandbox account create a Q-pointer to your production account like this. Let's say the production account is called PRODUCTION ED VOC MYPOINTER NEW ITEM TOP .I 001 Q 002 PRODUCTION 003 VOC 004 .FI 'MYPOINTER' filed Now do this SELECT MYPOINTER WITH F1 = "V" 963 items selected COPY MYPOINTER TO: (VOC This should copy all the missing 'verbs' from PRODUCTION to SANDBOX. Will Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] New UV Accout VOC
I mean no disrespect Bill but from reading these posts I have come to the conclusion that you should not be doing this. Maybe you should contact your VAR or a local contract person to help you out. - Original Message - From: "Brutzman, Bill" <[EMAIL PROTECTED]> To: Sent: Monday, August 08, 2005 2:34 PM Subject: RE: [U2] New UV Accout VOC [1] An example Q Pointer would help. It seems the downside to using Q-Pointers is that we would need a few hundred of them. On the other hand, for a SAND-BOX, the Q-Pointers could be added as needed. [2] I copied NEWACC to NEWACC.BAK and then overwrote NEWACC with VOC and then ran UPDATE.ACCOUNT. Doing so did not work. A message came back saying... "The following records appear in NEWACC but not in VOC." Of course, these well all of the records that we need. [3] While our baseline ERP system is from www.GRMS.com, most of what we use is homegrown. [4] Copies of VOC appear in half a dozen different places. When I change VOC in our baseline system, I can see the date change on the HP-Ux side. I was hoping that the only VOC that matters is the one under the account itself. [5] I am unable to get change directories to get to /u2/METAL/&TEMP&/NEWACC and /u2/SANDBOX/&TEMP&/NEWACC to try the above procedure. [6] Somehow our production system knows that the compiled code lives here /u2/METAL/SOFTWARE/ACC.BPAccounting Code /PUR.BPPurchasing Code ... /etc etc while the data files are in... /u2/METAL/* Further suggestions would be appreciated. Thanks to those who responded... --Bill Brutzman Manager, IT HK MetalCraft Mfg Corp PO Box 775 35 Industrial Road Lodi NJ 07644-0775 [EMAIL PROTECTED] 973.471.7770 x145 .voice 973.471.9666 .fax -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Richard Taylor Sent: Monday, August 08, 2005 12:22 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC Bill, I see you have received many responses some of which give some hints as to finding your missing verb so I will respond in general. I often copied accounts to new directories and had little trouble as long as you know what you are working with. Remember that in UV the voc holds pointers to files (local and remote), commands (the VOCLIB file was mentioned by someone else), and cataloged programs. Here are some of the pointers I would make to you: - Run Update.Account AFTER copying the remote VOC. Any conflicts will be moved to a holding file where you can review them and copy them back to the VOC if appropriate. - Watch out for local files as copying the VOC does not copy the underlying files. I usually copied the account directories first at the OS level then created a new account that pointed to that new location. - Watch out for Remote files (Q-pointers or hard path pointers) that point to files that are part of your live application. You may need to create copies of these accounts too to completely replicate your application environment to provide a Sandbox account. - Write a program to remove all voc entries for programs cataloged from your application program files. Then re-catalog the libraries that you need. - DANGER Watch out for indexes in files copied!! In UV the file header contains the full path to the index as it was created. This will now point to the old account which will mess up your indexes. In the new account use the SET-INDEX command to reset or remove the pointer in the file header. - Watch out for any VOC entries that are part of the application you are copying. These might include control records and/or flags that may, themselves, have embedded file paths. I did not have many of these to worry about, but that could mess you up. The bottom line is that there is nothing in a simple UV account VOC that would prevent you from copying it. The problem lies in the application whose account you are copying and how complex that application is. As I said I have done this many times with an application that was made up of 2 accounts at a minimum with great success. If you have any specific questions I would be happy to respond. Out of curiosity what is the application whose accounts you are trying to copy? Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Brutzman, Bill > Sent: Monday, August 08, 2005 10:19 AM > To: 'u2-users@lists
RE: [U2] New UV Accout VOC
[1] An example Q Pointer would help. It seems the downside to using Q-Pointers is that we would need a few hundred of them. On the other hand, for a SAND-BOX, the Q-Pointers could be added as needed. [2] I copied NEWACC to NEWACC.BAK and then overwrote NEWACC with VOC and then ran UPDATE.ACCOUNT. Doing so did not work. A message came back saying... "The following records appear in NEWACC but not in VOC." Of course, these well all of the records that we need. [3] While our baseline ERP system is from www.GRMS.com, most of what we use is homegrown. [4] Copies of VOC appear in half a dozen different places. When I change VOC in our baseline system, I can see the date change on the HP-Ux side. I was hoping that the only VOC that matters is the one under the account itself. [5] I am unable to get change directories to get to /u2/METAL/&TEMP&/NEWACC and /u2/SANDBOX/&TEMP&/NEWACC to try the above procedure. [6] Somehow our production system knows that the compiled code lives here /u2/METAL/SOFTWARE/ACC.BPAccounting Code /PUR.BPPurchasing Code ... /etc etc while the data files are in... /u2/METAL/* Further suggestions would be appreciated. Thanks to those who responded... --Bill Brutzman Manager, IT HK MetalCraft Mfg Corp PO Box 775 35 Industrial Road Lodi NJ 07644-0775 [EMAIL PROTECTED] 973.471.7770 x145 .voice 973.471.9666 .fax -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Richard Taylor Sent: Monday, August 08, 2005 12:22 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC Bill, I see you have received many responses some of which give some hints as to finding your missing verb so I will respond in general. I often copied accounts to new directories and had little trouble as long as you know what you are working with. Remember that in UV the voc holds pointers to files (local and remote), commands (the VOCLIB file was mentioned by someone else), and cataloged programs. Here are some of the pointers I would make to you: - Run Update.Account AFTER copying the remote VOC. Any conflicts will be moved to a holding file where you can review them and copy them back to the VOC if appropriate. - Watch out for local files as copying the VOC does not copy the underlying files. I usually copied the account directories first at the OS level then created a new account that pointed to that new location. - Watch out for Remote files (Q-pointers or hard path pointers) that point to files that are part of your live application. You may need to create copies of these accounts too to completely replicate your application environment to provide a Sandbox account. - Write a program to remove all voc entries for programs cataloged from your application program files. Then re-catalog the libraries that you need. - DANGER Watch out for indexes in files copied!! In UV the file header contains the full path to the index as it was created. This will now point to the old account which will mess up your indexes. In the new account use the SET-INDEX command to reset or remove the pointer in the file header. - Watch out for any VOC entries that are part of the application you are copying. These might include control records and/or flags that may, themselves, have embedded file paths. I did not have many of these to worry about, but that could mess you up. The bottom line is that there is nothing in a simple UV account VOC that would prevent you from copying it. The problem lies in the application whose account you are copying and how complex that application is. As I said I have done this many times with an application that was made up of 2 accounts at a minimum with great success. If you have any specific questions I would be happy to respond. Out of curiosity what is the application whose accounts you are trying to copy? Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Brutzman, Bill > Sent: Monday, August 08, 2005 10:19 AM > To: 'u2-users@listserver.u2ug.org' > Subject: [U2] New UV Accout VOC > > We need to setup a "Sand-Box" account for piloting. > > I created an account with UV Admin. I copied the data files (including > VOC) > over. > > The command >LOGTO SANDBOX seems to work ok. > > Upon issuing further commands
RE: [U2] New UV Accout VOC
Bill, I see you have received many responses some of which give some hints as to finding your missing verb so I will respond in general. I often copied accounts to new directories and had little trouble as long as you know what you are working with. Remember that in UV the voc holds pointers to files (local and remote), commands (the VOCLIB file was mentioned by someone else), and cataloged programs. Here are some of the pointers I would make to you: - Run Update.Account AFTER copying the remote VOC. Any conflicts will be moved to a holding file where you can review them and copy them back to the VOC if appropriate. - Watch out for local files as copying the VOC does not copy the underlying files. I usually copied the account directories first at the OS level then created a new account that pointed to that new location. - Watch out for Remote files (Q-pointers or hard path pointers) that point to files that are part of your live application. You may need to create copies of these accounts too to completely replicate your application environment to provide a Sandbox account. - Write a program to remove all voc entries for programs cataloged from your application program files. Then re-catalog the libraries that you need. - DANGER Watch out for indexes in files copied!! In UV the file header contains the full path to the index as it was created. This will now point to the old account which will mess up your indexes. In the new account use the SET-INDEX command to reset or remove the pointer in the file header. - Watch out for any VOC entries that are part of the application you are copying. These might include control records and/or flags that may, themselves, have embedded file paths. I did not have many of these to worry about, but that could mess you up. The bottom line is that there is nothing in a simple UV account VOC that would prevent you from copying it. The problem lies in the application whose account you are copying and how complex that application is. As I said I have done this many times with an application that was made up of 2 accounts at a minimum with great success. If you have any specific questions I would be happy to respond. Out of curiosity what is the application whose accounts you are trying to copy? Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Brutzman, Bill > Sent: Monday, August 08, 2005 10:19 AM > To: 'u2-users@listserver.u2ug.org' > Subject: [U2] New UV Accout VOC > > We need to setup a "Sand-Box" account for piloting. > > I created an account with UV Admin. I copied the data files (including > VOC) > over. > > The command >LOGTO SANDBOX seems to work ok. > > Upon issuing further commands from a TCL prompt, UniVerse comes back with > an > error message indicating... > > "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. > > Suggestions would be appreciated. > > --Bill > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
The "further command" you issued is looking for a program named MAIN.MENU probably. You need to look at the original account and see what MAIN.MENU is. It's possible that it wasn't originally cataloged, but was being found in the file that the program looking for it was run from. You may need to copy another file, or catalog some programs. MAIN.MENU may be refrenced by a program called from an I-type dictionary entry. Copying the entire VOC is almost never a good idea. You need to go through it and look at every q-pointer checking which ones point to the original account--some of them will need to point to the new account instead, while others will have to remain pointing to the old one. You may have some cataloged entries in there with relative file paths that need to be updated. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Brutzman, Bill > Sent: Monday, August 08, 2005 10:19 AM > To: 'u2-users@listserver.u2ug.org' > Subject: [U2] New UV Accout VOC > > > We need to setup a "Sand-Box" account for piloting. > > I created an account with UV Admin. I copied the data files > (including VOC) over. > > The command >LOGTO SANDBOX seems to work ok. > > Upon issuing further commands from a TCL prompt, UniVerse > comes back with an error message indicating... > > "Verb MAIN.MENU is not in your VOC". We are on a newer > version of HP-Ux. > > Suggestions would be appreciated. > > --Bill > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
Did you copy VOCLIB ? I think that's where menus are kept, but then again the pointer is in the VOC. Can you do an ED VOC MAIN.MENU ? If not, but you can do this in the source account then it would appear that the files didn't copy.Maybe when you LOGTO SANDBOX you arent where you think you are. Maybe uppercase/lowercase issue ? Just some thoughts. Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brutzman, Bill Sent: Monday, August 08, 2005 10:19 AM To: 'u2-users@listserver.u2ug.org' Subject: [U2] New UV Accout VOC We need to setup a "Sand-Box" account for piloting. I created an account with UV Admin. I copied the data files (including VOC) over. The command >LOGTO SANDBOX seems to work ok. Upon issuing further commands from a TCL prompt, UniVerse comes back with an error message indicating... "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
I would think that if you setup the account first, then created a Q pointer in the source account to the destination account's VOC that you could then copy from VOC to DESTQVOC all, and anything that is account specific should already exist on the DEST side, and not get copied, as long as you don't give the overwriting flag. I've never tried it either way, but the above just makes sense. but, I'd guess that maybe one of the VOC commands runs a Paragraph or cataloged program, which doesn't exist (or hasn't been cataloged to the new account name). George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, August 08, 2005 10:51 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] New UV Accout VOC RED FLAG!!! Don't ever copy a VOC file from one account to another. There's specific information in each account's VOC file that makes them NON-TRANFERRABLE. Anyone else experience the nightmares of corrupt data because of a copies VOC file? Karl > We need to setup a "Sand-Box" account for piloting. > > I created an account with UV Admin. I copied the data files (including > VOC) > over. > > The command >LOGTO SANDBOX seems to work ok. > > Upon issuing further commands from a TCL prompt, UniVerse comes back with > an > error message indicating... > > "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. > > Suggestions would be appreciated. > > --Bill > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > -- Karl L. Pearson Director of IT, ATS Industrial Supply Direct: 801-978-4429 Toll-free: 800-789-9300 1,29 Fax: 801-972-3888 http://www.atsindustrial.com [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please delete it and notify the sender immediately. Please note that there is no guarantee that this email or any attachment is virus free or has not been intercepted or amended. You could also just do an UPDATE.ACCOUNT to refresh to VOC. Philip -Original Message- From: Dan Fitzgerald [mailto:[EMAIL PROTECTED] Sent: 08 August 2005 15:35 To: u2-users@listserver.u2ug.org Subject: RE: [U2] New UV Accout VOC >From where did you copy the VOC? See if you can copy the VOC item for the old account to VOC SANDBOX. "Our greatest duty in this life is to help others. And please, if you can't help them, could you at least not hurt them?" - H.H. the Dalai Lama "When buying & selling are controlled by legislation, the first thing to be bought & sold are the legislators" - P.J. O'Rourke Dan Fitzgerald >From: "Brutzman, Bill" <[EMAIL PROTECTED]> >Reply-To: u2-users@listserver.u2ug.org >To: "'u2-users@listserver.u2ug.org'" >Subject: [U2] New UV Accout VOC >Date: Mon, 8 Aug 2005 10:19:07 -0400 > >We need to setup a "Sand-Box" account for piloting. > >I created an account with UV Admin. I copied the data files (including >VOC) >over. > >The command >LOGTO SANDBOX seems to work ok. > >Upon issuing further commands from a TCL prompt, UniVerse comes back with >an >error message indicating... > >"Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. > >Suggestions would be appreciated. > >--Bill >--- >u2-users mailing list >u2-users@listserver.u2ug.org >To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
Copy the VOC in from an existign accounts Its set you up a new one without all your programs in -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brutzman, Bill Sent: 08 August 2005 15:19 To: 'u2-users@listserver.u2ug.org' Subject: [U2] New UV Accout VOC We need to setup a "Sand-Box" account for piloting. I created an account with UV Admin. I copied the data files (including VOC) over. The command >LOGTO SANDBOX seems to work ok. Upon issuing further commands from a TCL prompt, UniVerse comes back with an error message indicating... "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] New UV Accout VOC
RED FLAG!!! Don't ever copy a VOC file from one account to another. There's specific information in each account's VOC file that makes them NON-TRANFERRABLE. Anyone else experience the nightmares of corrupt data because of a copies VOC file? Karl > We need to setup a "Sand-Box" account for piloting. > > I created an account with UV Admin. I copied the data files (including > VOC) > over. > > The command >LOGTO SANDBOX seems to work ok. > > Upon issuing further commands from a TCL prompt, UniVerse comes back with > an > error message indicating... > > "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. > > Suggestions would be appreciated. > > --Bill > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > -- Karl L. Pearson Director of IT, ATS Industrial Supply Direct: 801-978-4429 Toll-free: 800-789-9300 1,29 Fax: 801-972-3888 http://www.atsindustrial.com [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] New UV Accout VOC
From where did you copy the VOC? See if you can copy the VOC item for the old account to VOC SANDBOX. "Our greatest duty in this life is to help others. And please, if you can't help them, could you at least not hurt them?" - H.H. the Dalai Lama "When buying & selling are controlled by legislation, the first thing to be bought & sold are the legislators" - P.J. O'Rourke Dan Fitzgerald From: "Brutzman, Bill" <[EMAIL PROTECTED]> Reply-To: u2-users@listserver.u2ug.org To: "'u2-users@listserver.u2ug.org'" Subject: [U2] New UV Accout VOC Date: Mon, 8 Aug 2005 10:19:07 -0400 We need to setup a "Sand-Box" account for piloting. I created an account with UV Admin. I copied the data files (including VOC) over. The command >LOGTO SANDBOX seems to work ok. Upon issuing further commands from a TCL prompt, UniVerse comes back with an error message indicating... "Verb MAIN.MENU is not in your VOC". We are on a newer version of HP-Ux. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
