Re: [U2] UD - Triggers
Martin: Thanks. I guess the problem must be with the subroutine that's called by the trigger. I'll look into that. Thanks again, Bill Martin Braid wrote: No, CUSTOMER and CUSTOMER,CUSTOMER act the same as long as you have the trigger on CUSTOMER. LIST.TRIGGER CUSTOMER and LIST.TRIGGER CUSTOMER,CUSTOMER are the same. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 16 August 2011 20:25 To: U2 Users List Subject: Re: [U2] UD - Triggers So, are you saying if I have a trigger for CUSTOMER but not for CUSTOMER,CUSTOMER then the trigger won't work if some code looks like: "TCL.CMD = \SELECT CUSTOMER WITH CLIENTNO = "6500" : @AM : \DELETE CUSTOMER,CUSTOMER\ ; EXECUTE TCL.CMD CAPTURING OUTPUT"? H... Bill - Original Message - *From:* mbr...@epicor.com *To:* U2 Users List *Date:* 8/16/2011 1:53 AM *Subject:* Re: [U2] UD - Triggers I have no problem with this on UD 7.2. You do need to create the triggers e.g. DELETE on all partitions CUSTOMER and CUSTOMER,NEWCUST and CUSTOMER,PREVCUST CUSTOMER,CUSTOMER will also then be hit. Similarly, if you put e.g. a DELETE trigger on CUSTOMER and CUSTOMER,PREVCUST but not on CUSTOMER,NEWCUST and then create and delete a record in CUSTOMER,NEWCUST it will not trigger - because there isn't one set up at the partition level. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 15 August 2011 19:37 To: U2 Mail List Subject: [U2] UD - Triggers Did anyone know that when one creates a trigger for a multi-level file, and references the full file to delete or update a record, the triggers _DON'T_ work. e.g. CUSTOMERFILE + NEWCUST + PREVCUST If I delete the "CUSTOMERFILE,CUSTOMERFILE" triggers don't work but they do if I delete the "CUSTOMERFILE". So, I can't use multi-level files for any file that contains triggers and whose DATA file name is different than the file name. Therefore, beware on conversions. I'm wondering if this is a bug or a feature? :-) Bill Epicor Software (UK) is a limited company registered in England& Wales. Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. This message has been scanned for malware by Websense. www.websense.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Click https://www.mailcontrol.com/sr/JvWqoNuHqhDTndxI!oX7UsdpzMR7Bo2K5w7dzs4ny +jSAn+EA2MfMQw3rzaN3YBrj4fdSEfZti1EcZNy6HxKug== to report this email as spam. Epicor Software (UK) is a limited company registered in England& Wales. Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/m
Re: [U2] UD - Triggers
No, CUSTOMER and CUSTOMER,CUSTOMER act the same as long as you have the trigger on CUSTOMER. LIST.TRIGGER CUSTOMER and LIST.TRIGGER CUSTOMER,CUSTOMER are the same. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 16 August 2011 20:25 To: U2 Users List Subject: Re: [U2] UD - Triggers So, are you saying if I have a trigger for CUSTOMER but not for CUSTOMER,CUSTOMER then the trigger won't work if some code looks like: "TCL.CMD = \SELECT CUSTOMER WITH CLIENTNO = "6500" : @AM : \DELETE CUSTOMER,CUSTOMER\ ; EXECUTE TCL.CMD CAPTURING OUTPUT"? H... Bill - Original Message - *From:* mbr...@epicor.com *To:* U2 Users List *Date:* 8/16/2011 1:53 AM *Subject:* Re: [U2] UD - Triggers > I have no problem with this on UD 7.2. > You do need to create the triggers e.g. DELETE on all partitions > CUSTOMER and CUSTOMER,NEWCUST and CUSTOMER,PREVCUST > CUSTOMER,CUSTOMER will also then be hit. > Similarly, if you put e.g. a DELETE trigger on CUSTOMER and > CUSTOMER,PREVCUST but not on CUSTOMER,NEWCUST and then create and delete > a record in CUSTOMER,NEWCUST it will not trigger - because there isn't > one set up at the partition level. > > -Original Message- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett > Sent: 15 August 2011 19:37 > To: U2 Mail List > Subject: [U2] UD - Triggers > Did anyone know that when one creates a trigger for a multi-level file, > and references the full file to delete or update a record, the triggers > _DON'T_ work. e.g. > CUSTOMERFILE >+ NEWCUST >+ PREVCUST > If I delete the "CUSTOMERFILE,CUSTOMERFILE" triggers don't work but they > do if I delete the "CUSTOMERFILE". So, I can't use multi-level files > for any file that contains triggers and whose DATA file name is > different than the file name. Therefore, beware on conversions. > I'm wondering if this is a bug or a feature? :-) > Bill > > > Epicor Software (UK) is a limited company registered in England& Wales. > Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB > This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. > > > This message has been scanned for malware by Websense. www.websense.com > ___ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Click https://www.mailcontrol.com/sr/JvWqoNuHqhDTndxI!oX7UsdpzMR7Bo2K5w7dzs4ny +jSAn+EA2MfMQw3rzaN3YBrj4fdSEfZti1EcZNy6HxKug== to report this email as spam. Epicor Software (UK) is a limited company registered in England & Wales. Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Triggers
So, are you saying if I have a trigger for CUSTOMER but not for CUSTOMER,CUSTOMER then the trigger won't work if some code looks like: "TCL.CMD = \SELECT CUSTOMER WITH CLIENTNO = "6500" : @AM : \DELETE CUSTOMER,CUSTOMER\ ; EXECUTE TCL.CMD CAPTURING OUTPUT"? H... Bill - Original Message - *From:* mbr...@epicor.com *To:* U2 Users List *Date:* 8/16/2011 1:53 AM *Subject:* Re: [U2] UD - Triggers I have no problem with this on UD 7.2. You do need to create the triggers e.g. DELETE on all partitions CUSTOMER and CUSTOMER,NEWCUST and CUSTOMER,PREVCUST CUSTOMER,CUSTOMER will also then be hit. Similarly, if you put e.g. a DELETE trigger on CUSTOMER and CUSTOMER,PREVCUST but not on CUSTOMER,NEWCUST and then create and delete a record in CUSTOMER,NEWCUST it will not trigger - because there isn't one set up at the partition level. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 15 August 2011 19:37 To: U2 Mail List Subject: [U2] UD - Triggers Did anyone know that when one creates a trigger for a multi-level file, and references the full file to delete or update a record, the triggers _DON'T_ work. e.g. CUSTOMERFILE + NEWCUST + PREVCUST If I delete the "CUSTOMERFILE,CUSTOMERFILE" triggers don't work but they do if I delete the "CUSTOMERFILE". So, I can't use multi-level files for any file that contains triggers and whose DATA file name is different than the file name. Therefore, beware on conversions. I'm wondering if this is a bug or a feature? :-) Bill Epicor Software (UK) is a limited company registered in England& Wales. Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. This message has been scanned for malware by Websense. www.websense.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Triggers
I have no problem with this on UD 7.2. You do need to create the triggers e.g. DELETE on all partitions CUSTOMER and CUSTOMER,NEWCUST and CUSTOMER,PREVCUST CUSTOMER,CUSTOMER will also then be hit. Similarly, if you put e.g. a DELETE trigger on CUSTOMER and CUSTOMER,PREVCUST but not on CUSTOMER,NEWCUST and then create and delete a record in CUSTOMER,NEWCUST it will not trigger - because there isn't one set up at the partition level. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 15 August 2011 19:37 To: U2 Mail List Subject: [U2] UD - Triggers Did anyone know that when one creates a trigger for a multi-level file, and references the full file to delete or update a record, the triggers _DON'T_ work. e.g. CUSTOMERFILE + NEWCUST + PREVCUST If I delete the "CUSTOMERFILE,CUSTOMERFILE" triggers don't work but they do if I delete the "CUSTOMERFILE". So, I can't use multi-level files for any file that contains triggers and whose DATA file name is different than the file name. Therefore, beware on conversions. I'm wondering if this is a bug or a feature? :-) Bill Epicor Software (UK) is a limited company registered in England & Wales. Registration Number: 2338274. Registered Office: Osborne Clarke OWA, One London Wall, London EC2Y 5EB This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software (UK) Limited or any other company within its group. This message has been scanned for malware by Websense. www.websense.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] UD - Triggers
Did anyone know that when one creates a trigger for a multi-level file, and references the full file to delete or update a record, the triggers _DON'T_ work. e.g. CUSTOMERFILE + NEWCUST + PREVCUST If I delete the "CUSTOMERFILE,CUSTOMERFILE" triggers don't work but they do if I delete the "CUSTOMERFILE". So, I can't use multi-level files for any file that contains triggers and whose DATA file name is different than the file name. Therefore, beware on conversions. I'm wondering if this is a bug or a feature? :-) Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
RE: [U2] UD Triggers
Kevin: This was my fault. I should have realized that since there can only be one update and one delete trigger I shouldn't reference the trigger name in the DELETE.TRIGGER command. :-0ops Thanks again. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin King Sent: Sunday, October 29, 2006 3:09 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Triggers What about DELETE.TRIGGER file BEFORE UPDATE? -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. --- 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] UD Triggers
What about DELETE.TRIGGER file BEFORE UPDATE? -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Triggers
Larry: Thanks! :DELETE.TRIGGER APVENDOR --^ syntax error :DELETE.TRIGGER APVENDOR BEFORE UPDATE :LIST-TRIGGER APVENDOR BEFORE UPDATE TRIGGER: not defined BEFORE DELETE TRIGGER: U2.NAMES.BRIDGE.D :-) Bill Hmmm...too much like Unix, not enough like MV! [sigh] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Hiscock Sent: Saturday, October 28, 2006 12:30 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Triggers Try either: DELETE.TRIGGER APVENDOR UPDATE Or DELETE.TRIGGER APVENDOR BEFORE UPDATE Larry Hiscock Western Computer Services -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Saturday, October 28, 2006 11:56 AM To: u2-users@listserver.u2ug.org Subject: [U2] UD Triggers Does anyone know why I can't delete a trigger on a file in UniData (v7.1 on NT)? Here's what I get: :LIST.TRIGGER APVENDOR BEFORE UPDATE TRIGGER: U2.NAMES.BRIDGE.U BEFORE DELETE TRIGGER: U2.NAMES.BRIDGE.D :DELETE.TRIGGER APVENDOR U2.NAMES.BRIDGE.U UPDATE -^ Syntax error. :CREATE.TRIGGER APVENDOR U2T.APVENDOR.U UPDATE The specified trigger already exists. :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE U :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE P :DELETE.TRIGGER APVENDOR --^ syntax error The UniData documentation gives the following example: :CREATE.TRIGGER ORDERS DEMO_RTN BEFORE UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: DEMO_RTN BEFORE DELETE TRIGGER: not defined :DELETE.TRIGGER ORDERS UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: not defined BEFORE DELETE TRIGGER: not defined Any help 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] UD Triggers
Kevin: Thanks, but :LIST-TRIGGER APVENDOR BEFORE UPDATE TRIGGER: U2.NAMES.BRIDGE.U BEFORE DELETE TRIGGER: U2.NAMES.BRIDGE.D :DELETE.TRIGGER APVENDOR U2.NAMES.BRIDGE.U BEFORE UPDATE -^ Syntax error. :CT VOC U2.NAMES.BRIDGE.U VOC: U2.NAMES.BRIDGE.U is not a record in VOC. I'm wondering if it might have been created, then the program was decataloged and now it won't delete (just a stab in the dark). :-( Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin King Sent: Saturday, October 28, 2006 12:25 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Triggers >Does anyone know why I can't delete a trigger on a file in UniData (v7.1 on NT)? DELETE.TRIGGER file trigger BEFORE UPDATE ??? From your samples it looks like you're missing the "BEFORE", despite what the help says. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. --- 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] UD Triggers
Try either: DELETE.TRIGGER APVENDOR UPDATE Or DELETE.TRIGGER APVENDOR BEFORE UPDATE Larry Hiscock Western Computer Services -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Saturday, October 28, 2006 11:56 AM To: u2-users@listserver.u2ug.org Subject: [U2] UD Triggers Does anyone know why I can't delete a trigger on a file in UniData (v7.1 on NT)? Here's what I get: :LIST.TRIGGER APVENDOR BEFORE UPDATE TRIGGER: U2.NAMES.BRIDGE.U BEFORE DELETE TRIGGER: U2.NAMES.BRIDGE.D :DELETE.TRIGGER APVENDOR U2.NAMES.BRIDGE.U UPDATE -^ Syntax error. :CREATE.TRIGGER APVENDOR U2T.APVENDOR.U UPDATE The specified trigger already exists. :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE U :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE P :DELETE.TRIGGER APVENDOR --^ syntax error The UniData documentation gives the following example: :CREATE.TRIGGER ORDERS DEMO_RTN BEFORE UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: DEMO_RTN BEFORE DELETE TRIGGER: not defined :DELETE.TRIGGER ORDERS UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: not defined BEFORE DELETE TRIGGER: not defined Any help 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] UD Triggers
>Does anyone know why I can't delete a trigger on a file in UniData (v7.1 on NT)? DELETE.TRIGGER file trigger BEFORE UPDATE ??? From your samples it looks like you're missing the "BEFORE", despite what the help says. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] UD Triggers
Does anyone know why I can't delete a trigger on a file in UniData (v7.1 on NT)? Here's what I get: :LIST.TRIGGER APVENDOR BEFORE UPDATE TRIGGER: U2.NAMES.BRIDGE.U BEFORE DELETE TRIGGER: U2.NAMES.BRIDGE.D :DELETE.TRIGGER APVENDOR U2.NAMES.BRIDGE.U UPDATE -^ Syntax error. :CREATE.TRIGGER APVENDOR U2T.APVENDOR.U UPDATE The specified trigger already exists. :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE U :DELETE.TRIGGER APVENDOR --^ syntax error :ECLTYPE P :DELETE.TRIGGER APVENDOR --^ syntax error The UniData documentation gives the following example: :CREATE.TRIGGER ORDERS DEMO_RTN BEFORE UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: DEMO_RTN BEFORE DELETE TRIGGER: not defined :DELETE.TRIGGER ORDERS UPDATE :LIST.TRIGGER ORDERS BEFORE UPDATE TRIGGER: not defined BEFORE DELETE TRIGGER: not defined Any help would be appreciated. Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Triggers
I agree with his assessment for the most part but had some comments to add as well. At 04:46 PM 3/20/2006, Dave Taylor wrote: We were under the impression IBM had "conversion" utilities available that would mostly convert D3 style dictionaries to UD style dictionaries; thus mitigating the one advantage UV had over UD. There were utilities that were provided, documented and supported by "UniData" (when they were UniData the company) at one time. They are no longer ever mentioned and most people do not even know they ever existed. They are extremely valuable for converting the dictionaries. I played with UV for about three months and pretty much validated that D3 doesn't run like D3 on UV. Our application needed a lot of work to make it run. What this means is that any (and I mean ANY) use of newer D3 functionality makes conversion more difficult. The application we're converting does have some of this functionality. Often true. Straight Pick code converts over nicely. When you get into trouble is when you start using the new functionality offered by databases (was not part of original Pick) or you hired those clever consultants who knew how to get Pick to do things that are not documented. :^) 1) Backup utility. UD has no backup utility. As a result it could not restore data reliably. That is true. You must use native OS or 3rd party backup software. Often not an issue. Just make sure files are not being updated while backing them up. Most sites are using mirrorred snapshots to make a static backup nowadays. Because the backups are done at file level and not the record level, they will go much faster as well. 2) Limited U2 resources. The VAR we worked with has limited technical resources for UniData. We've had to pretty much do this ourselves. IBM has no interest in our conversion from D3 and there seems to be very limited resources available for assistance. There are other VAR's with the experience to do migrations as well as provide on going support behind them. I can think of at least one. :-) 3) Q-File facility. UniData doesn't have a comparable function. Users of UD, and the engineers, don't seem to have a clue of it's benefits and have not incorporated this into UD. Someone already posted to this. UD has the ability to emulate QPointers in a general sense. 4) Pick compatibility. UniData doesn't seem to have moved forward in 20 years with their Pick syntax. They have, however, incorporated the '-' in the usual verbs (CREATE-FILE works as well as CREATE.FILE). Many commands just fail instead of working in a default state. That is true to some extent. Most of the Pick compatibility issues have been added years ago. Now the product focus is not in conversions but in bringing current (and new) customers into newer technology and making the data more open to other products. For the most part, in UD, the major hurdle will be the dictionary conversion. But once that is done, its done. You just then have the training issue to create new dicts going forward. Hope this is at all interesting. Yes it was. Keep in mind though that every site is going to be different. Most of the issues encountered are going to be strictly unique to the applications. Once worked around though you never have to really deal with it again. (Unless you decided to migrate to another database) Doug Miller [EMAIL PROTECTED] Manager of Technical Services Strategy 7Dallas TX --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Triggers
Interesting. I never realized that the Q pointer capability on the Manage-2000 system was NOT a part of Unidata. Here is how they get around it: CT Copy an ItemPage 1 File Name VOC Item Name Q.0210 File Resides in account MANAGE-2000.7.0 -- Item 1 "Q.0210" has 3 lines -- 0001: F 0002: ../MMC.MAIN/SOH 0003: ../DICTS.7.0/D_SOH They just create a file pointer! hth, Allen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Taylor Sent: Monday, March 20, 2006 14:47 To: David Wolverton; u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Triggers David, I asked Bill Haskett recently why he chose to move this customer's software from D3 to Unidata rather than to Universe, and he responded to me in considerable detail. Since I thought this might be of interest to you and others on the list, I have reproduced his comments with his permission. It was reported to us, at the time, that UniVerse only had SQL triggers, their indexing scheme was sub-standard, and their data input capabilities had no timing functionality. The rest of the issues, we brought to a U2 VAR to review, were reported to be similar between both UniVerse and UniData. So, the analysis indicated there would be less work with UniData than with UniVerse. These were some of the other issues: 1) DBMS security (there is virtually none at the U2 level) 2) Backups (reported that both U2 products had it) 3) O/S integration (UD was supposed to be better) 4) BASIC language differences (both were about the same) 5) Login processing (both have LOGIN/LOGOUT paragraphs) 6) Case insensitivity (neither U2 product functionally has this) 7) terminal management Our client has four critical needs: 1) dictionaries, 2) indexes, 3) data input with timing, and 4) triggers. Their application uses these functionalities extensively. The conversion was very simple with respect to needs 2, 3, and 4. :-) We were under the impression IBM had "conversion" utilities available that would mostly convert D3 style dictionaries to UD style dictionaries; thus mitigating the one advantage UV had over UD. I played with UV for about three months and pretty much validated that D3 doesn't run like D3 on UV. Our application needed a lot of work to make it run. What this means is that any (and I mean ANY) use of newer D3 functionality makes conversion more difficult. The application we're converting does have some of this functionality. Our client's application was very clean; didn't use PROCs, dictionaries were clean, BASIC code was clean, and accounts were clean and properly segregated. I actually used D3RESTORE, which worked fine to UV. I've been told that "ACCOUNT.RESTORE" works fine in UniData. This application has their own spooler functionality. They weren't concerned about this too much because their new application will be using "SQL Reporting Services" and the "spooler" will be unnecessary. But now with things working well enough they want to hire us to (In response to our comment that Universe is not comfortable comparing the numeric value of an alpha string with that of another alpha string - eg. IF "ABC" > "XYZ" THEN etc (I can't understand why :)!).) We've found this not to be of too much significance, but there's a lot more than what you're suggesting: like TCLREAD, casing, ACCESS() vs @ & SYSTEM() functions, Indexes, ASSIGNED (or UNASSIGNED), FOLD, IN vs KEYIN, dimensioned arrays, FILEINFO vs NOT(ASSIGNED), subroutine names inside the program, HEADING options, OCONVs, LIST mgmt, CONVERT, SWAP, CHANGE, COMMON names, etc, etc, etc. This is not to suggest that an basic R83 application can't convert to UniVerse easily, just that a D3 application can, and probably will, have more difficulties. There were some "SURPRISES" we ran into: 1) Backup utility. UD has no backup utility. As a result it could not restore data reliably. We had to jury-rig a transfer between D3 and U2; which worked ok; others have been more successful with the UD "ACCOUNT.RESTORE". We eventually got the data restored. When an mvDbms person speaks of a "backup" that's what they mean. Like a "tar" or an "ntbackup" file. We never thought UD has no internal backup utility. 2) Limited U2 resources. The VAR we worked with has limited technical resources for UniData. We've had to pretty much do this ourselves. IBM has no interest in our conversion from D3 and there seems to be very limited resources available for assistance. 3) Q-File facility. UniData doesn't have a comparable function. Users of UD, and the engineers, don't seem to have a clue of it's benefits and have not incorporated this into UD. 4) Pick compatibility. UniData doesn't seem to have moved forwar
Re: [U2] [UD] Triggers
David, I asked Bill Haskett recently why he chose to move this customer's software from D3 to Unidata rather than to Universe, and he responded to me in considerable detail. Since I thought this might be of interest to you and others on the list, I have reproduced his comments with his permission. It was reported to us, at the time, that UniVerse only had SQL triggers, their indexing scheme was sub-standard, and their data input capabilities had no timing functionality. The rest of the issues, we brought to a U2 VAR to review, were reported to be similar between both UniVerse and UniData. So, the analysis indicated there would be less work with UniData than with UniVerse. These were some of the other issues: 1) DBMS security (there is virtually none at the U2 level) 2) Backups (reported that both U2 products had it) 3) O/S integration (UD was supposed to be better) 4) BASIC language differences (both were about the same) 5) Login processing (both have LOGIN/LOGOUT paragraphs) 6) Case insensitivity (neither U2 product functionally has this) 7) terminal management Our client has four critical needs: 1) dictionaries, 2) indexes, 3) data input with timing, and 4) triggers. Their application uses these functionalities extensively. The conversion was very simple with respect to needs 2, 3, and 4. :-) We were under the impression IBM had "conversion" utilities available that would mostly convert D3 style dictionaries to UD style dictionaries; thus mitigating the one advantage UV had over UD. I played with UV for about three months and pretty much validated that D3 doesn't run like D3 on UV. Our application needed a lot of work to make it run. What this means is that any (and I mean ANY) use of newer D3 functionality makes conversion more difficult. The application we're converting does have some of this functionality. Our client's application was very clean; didn't use PROCs, dictionaries were clean, BASIC code was clean, and accounts were clean and properly segregated. I actually used D3RESTORE, which worked fine to UV. I've been told that "ACCOUNT.RESTORE" works fine in UniData. This application has their own spooler functionality. They weren't concerned about this too much because their new application will be using "SQL Reporting Services" and the "spooler" will be unnecessary. But now with things working well enough they want to hire us to (In response to our comment that Universe is not comfortable comparing the numeric value of an alpha string with that of another alpha string - eg. IF "ABC" > "XYZ" THEN etc (I can't understand why :)!).) We've found this not to be of too much significance, but there's a lot more than what you're suggesting: like TCLREAD, casing, ACCESS() vs @ & SYSTEM() functions, Indexes, ASSIGNED (or UNASSIGNED), FOLD, IN vs KEYIN, dimensioned arrays, FILEINFO vs NOT(ASSIGNED), subroutine names inside the program, HEADING options, OCONVs, LIST mgmt, CONVERT, SWAP, CHANGE, COMMON names, etc, etc, etc. This is not to suggest that an basic R83 application can't convert to UniVerse easily, just that a D3 application can, and probably will, have more difficulties. There were some "SURPRISES" we ran into: 1) Backup utility. UD has no backup utility. As a result it could not restore data reliably. We had to jury-rig a transfer between D3 and U2; which worked ok; others have been more successful with the UD "ACCOUNT.RESTORE". We eventually got the data restored. When an mvDbms person speaks of a "backup" that's what they mean. Like a "tar" or an "ntbackup" file. We never thought UD has no internal backup utility. 2) Limited U2 resources. The VAR we worked with has limited technical resources for UniData. We've had to pretty much do this ourselves. IBM has no interest in our conversion from D3 and there seems to be very limited resources available for assistance. 3) Q-File facility. UniData doesn't have a comparable function. Users of UD, and the engineers, don't seem to have a clue of it's benefits and have not incorporated this into UD. 4) Pick compatibility. UniData doesn't seem to have moved forward in 20 years with their Pick syntax. They have, however, incorporated the '-' in the usual verbs (CREATE-FILE works as well as CREATE.FILE). Many commands just fail instead of working in a default state. Hope this is at all interesting. Bill Bill, thanks again for your review of UD vs. UV. Dave Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (C) 310-561-5200 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated EDI Translation and DataSync Integration www.sysmarkinfo.com - Original Message - From: "David Wolverton" <[EMAIL PROTECTED]> To: Sent: Friday, March 17, 2006 6:13 AM Subject: RE: [U2] [UD] Triggers --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Triggers
Ken: ...Original Message... from Ken Wallis > It sounds like you feel exactly the same about UniData as I > did about D3 when I spent a few months contracting at a D3 > shop - antiquated stuff, how can anybody work with this when > xxx is so much better? Yea. There's a lot about D3 that wears on anyone; this explains why a lot of people want to convert. :-) > I'm not sure which MV enhancements you mean, but I suspect > the issue is really one of adapting to looking at things from > a different perspective. I would like to think our "perspective" differences is a basis for product improvement. :-) You should see what Microsoft has done with SQL Server 2005 and their admin tools; an impressive improvement from SQL Server 2000. Raining Data doesn't have the resources to achieve anywhere near this kind of improvement to D3. With IBM, however, one would think they would understand U2 can be improved (mostly to assist conversions and new users). I can only hope IBM will take the attitude that U2 can, and should, be improved to bring in other MV applications and encourage new application development. As always, thanks for your help and kind comments. :-) Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Triggers
Agreed -- we have D3 users and UniData users and UniVerse users ... I'm not sure that part of UniData is 'Time Warped' -- we've seen a ton of new features built in during the last few years, while D3 chugs along, they've only produced 3rd level point revisions in the last 2 years! Wow. It does make their maintenance seem high! I'm getting the same feedback from my customers. The only thing D3 has that I miss in UniData is Case Insensitivity everywhere. Gosh that was nice. Gosh that was a nightmare. Gosh that was nice. And while UniVerse may be slightly more compatible with D3, UniVerse is slightly more complex to administrer than UniData in my experience. Not as much once you know all the edges, but there are more edges in UniVerse for sure! (No flame wars needed or intended!) Bill - Welcome your customer to U2 land!! DW Bill Haskett wrote: > > How difficult was the move - was it all green screen with source > > code or more difficult? > > It wasn't that difficult. The biggest problems were UniData is like > interfacing with Microdata in 1982...it's a time warp! The UniData > environment is excruciatingly tedious and the lack of MV enhancements > is what I'd expect from mvBASE (an end-of-line product). Ken wrote: >It sounds like you feel exactly the same about UniData as I did about D3 when I spent a few months contracting at a D3 shop - antiquated stuff, how can anybody work with this when xxx is so much better? >I'm not sure which MV enhancements you mean, but I suspect the issue is really one of adapting to looking at things from a different perspective. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Triggers
Bill Haskett wrote: > > How difficult was the move - was it all green screen with > > source code or more difficult? > > It wasn't that difficult. The biggest problems were UniData is like > interfacing with Microdata in 1982...it's a time warp! The UniData > environment is excruciatingly tedious and the lack of MV > enhancements is what I'd expect from mvBASE (an end-of-line product). It sounds like you feel exactly the same about UniData as I did about D3 when I spent a few months contracting at a D3 shop - antiquated stuff, how can anybody work with this when xxx is so much better? I'm not sure which MV enhancements you mean, but I suspect the issue is really one of adapting to looking at things from a different perspective. Cheers, Ken --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Triggers
Bill, Why didn't you stop at Universe? Why go to Unidata? Universe has a "Pick" flavor that runs D3 almost just like D3 runs D3. Out TAPE.DUMP and TAPE.LOAD programs move all the files in an account directly from D3 to Universe in two simple steps. Our UvSpoolerPlus provides a generic Pick spooler for generic Pick software like D3 software running on Universe. The only conversion issues we faced recently in converting software from R91 to Universe were related to the syntax of the CONVERT statement and the fact that Universe is not comfortable comparing the numeric value of an alpha string with that of another alpha string - eg. IF "ABC" > "XYZ" THEN etc. ( I can't understand why :)!). We're in the process of porting UvSpooler Plus to Unidata, as UdSpoolerPlus. Would UdSpoolerPlus help your D3 software feel more at home with a D3-like spooler and D3-like spooler commands? Would UdSpoolerPlus eliminate your need to re-program all of the print programs and procs in the D3 software? Please call me if we can be of assistance. Rgds, Dave Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (C) 310-561-5200 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated EDI Translation and DataSync Integration www.sysmarkinfo.com - Original Message - From: "Bill Haskett" <[EMAIL PROTECTED]> To: Sent: Thursday, March 16, 2006 7:39 PM Subject: RE: [U2] [UD] Triggers > David: > > Answers below. > > > -Original Message- > > From: David Wolverton > > Sent: Thursday, March 16, 2006 11:36 AM > > To: 'Bill Haskett'; u2-users@listserver.u2ug.org > > Subject: RE: [U2] [UD] Triggers > > > > What was the driving force to move from D3 to UniData? > > According to our client: > > 1) They want the IBM name, > 2) D3 costs too much, > 3) Support isn't what it should be, > 4) D3 is less than stable, > 5) Raining Data is treading water. > > > How difficult was the move - was it all green screen with > > source code or more difficult? > > It wasn't that difficult. The biggest problems were UniData is like > interfacing with Microdata in 1982...it's a time warp! The UniData > environment is excruciatingly tedious and the lack of MV enhancements is > what I'd expect from mvBASE (an end-of-line product). These issues cause > our conversion to extend from about 30 man-days to close to 150 man-days. > > Those who use UniData have no clue about the issues with conversion. Why > anyone involved with UniData wouldn't want it to be used by others is beyond > my comprehension. > > > How did you actually DO the move - it's not like D3 files > > will copy at any high level to UniData! > > They actually do. Colin has had success with "ACCOUNT.RESTORE" while I > copied to UniVerse then to UniData (of course this digression did take about > 10 man-days). > > > How long did it take to make the move (physically, once you > > worked out the kinks)? > > We have about 4 man-months into this. We estimate if UniData had taken > steps to update itself and provided a few utilities to assist in conversions > we would have only taken about one man-month (30 days isn't bad for an > enterprise application conversion). > > > Thanks -- I'm sure there are others here who would be > > interested in knowing more about your migration... > > > > David W. > > > > -Original Message- > > From: Bill Haskett > > Sent: Tuesday, March 14, 2006 7:44 PM > > To: u2-users@listserver.u2ug.org > > Subject: [U2] [UD] Triggers > > > > I've converted a client's system from D3 to UniData and > > everything mostly works fine. One of the last items I > > have to deal with are triggers. > > [snipped] > --- > 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] [UD] Triggers
David: Answers below. > -Original Message- > From: David Wolverton > Sent: Thursday, March 16, 2006 11:36 AM > To: 'Bill Haskett'; u2-users@listserver.u2ug.org > Subject: RE: [U2] [UD] Triggers > > What was the driving force to move from D3 to UniData? According to our client: 1) They want the IBM name, 2) D3 costs too much, 3) Support isn't what it should be, 4) D3 is less than stable, 5) Raining Data is treading water. > How difficult was the move - was it all green screen with > source code or more difficult? It wasn't that difficult. The biggest problems were UniData is like interfacing with Microdata in 1982...it's a time warp! The UniData environment is excruciatingly tedious and the lack of MV enhancements is what I'd expect from mvBASE (an end-of-line product). These issues cause our conversion to extend from about 30 man-days to close to 150 man-days. Those who use UniData have no clue about the issues with conversion. Why anyone involved with UniData wouldn't want it to be used by others is beyond my comprehension. > How did you actually DO the move - it's not like D3 files > will copy at any high level to UniData! They actually do. Colin has had success with "ACCOUNT.RESTORE" while I copied to UniVerse then to UniData (of course this digression did take about 10 man-days). > How long did it take to make the move (physically, once you > worked out the kinks)? We have about 4 man-months into this. We estimate if UniData had taken steps to update itself and provided a few utilities to assist in conversions we would have only taken about one man-month (30 days isn't bad for an enterprise application conversion). > Thanks -- I'm sure there are others here who would be > interested in knowing more about your migration... > > David W. > > -Original Message----- > From: Bill Haskett > Sent: Tuesday, March 14, 2006 7:44 PM > To: u2-users@listserver.u2ug.org > Subject: [U2] [UD] Triggers > > I've converted a client's system from D3 to UniData and > everything mostly works fine. One of the last items I > have to deal with are triggers. [snipped] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Triggers
Some questions (I have a few sites that have this as an open topic as well...) I meant to ask earlier, but couldn't figure out if I should Reply or Reply All (kidding!!) What was the driving force to move from D3 to UniData? How difficult was the move - was it all green screen with source code or more difficult? How did you actually DO the move - it's not like D3 files will copy at any high level to UniData! How long did it take to make the move (physically, once you worked out the kinks) Thanks -- I'm sure there are others here who would be interested in knowing more about your migration... David W. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Tuesday, March 14, 2006 7:44 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Triggers I've converted a client's system from D3 to UniData and everything mostly works fine. One of the last items I have to deal with are triggers. I've read the UniData documentation on triggers and am intimately familiar with D3 triggers, so it's no wonder I'm confused about UniData triggers. Questions: 1) Can I create both an update and delete trigger on a file using the same BASIC program or do I need to create two separate programs? In D3 there's an internal function that indicates if the action is an add or delete. This allows a single program to be used for both an update and a delete. 2) How can I tell if a record is being added or changed? 3) Where do the passed variables come from? SUBROUTINE U2.NAMES.BRIDGE.U (ExecStat, DictFlag, FileName, RecIdExpr, RecValue) What specifically is "RecIdExpr"? The record key being updated (documentation says it's the record to be updated)? Is FileName the file name or the "opened" file (file variable)? Do I have to set "DictFlag"? It seems UniData requires a trigger to be defined as either UPDATE or DELETE. Does this mean I have to create two BASIC programs; one for updating and one for deleting? Any assistance would be appreciated. :-) Bill Haskett Advantos Systems, Inc. www.advantos.net (760)944-5570 (CA) (360)923-4838 (WA) --- 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] [UD] Triggers
>Agreed - I never use the same code for both. The poster just asked if it was possible and it is. Just tweaking the idea, Jeff.. That's all. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Triggers
1) Can I create both an update and delete trigger on a file using the same BASIC program or do I need to create two separate programs? In D3 there's an internal function that indicates if the action is an add or delete. This allows a single program to be used for both an update and a delete. You can use the same function/subroutine to do both. 2) How can I tell if a record is being added or changed? There is no difference. Unidata has two triggers: UPDATE and DELETE. UPDATE would cover both newly added records and changed records. The only way to tell if a record was being newly added would be to read it from the trigger itself and see if it's empty. This would not be terribly efficient. 3) Where do the passed variables come from? SUBROUTINE U2.NAMES.BRIDGE.U (ExecStat, DictFlag, FileName, RecIdExpr, RecValue) Unidata does all this for you. What specifically is "RecIdExpr"? The record key being updated (documentation says it's the record to be updated)? RedIdExpr is the key to the file you're writing. Is FileName the file name or the "opened" file (file variable)? FileName is the filename (VOC entry). Do I have to set "DictFlag"? No, unidata does this for you. IF DictFlag = '' THEN You're updating a data record END ELSE You're updating a DICT record END It seems UniData requires a trigger to be defined as either UPDATE or DELETE. Does this mean I have to create two BASIC programs; one for updating and one for deleting? You can use the same subroutine or function for both if you like: CREATE.TRIGGER FILENAME TRIGGER.SUBROUTINE.NAME UPDATE CREATE.TRIGGER FILENAME TRIGGER.SUBROUTINE.NAME DELETE LIST.TRIGGER FILENAME This would use the same 'TRIGGER.SUBROUTINE.NAME' for both. Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 "We're not given the burdens we deserve, we're given the burdens we can bear." Several --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] [UD] Triggers
I've converted a client's system from D3 to UniData and everything mostly works fine. One of the last items I have to deal with are triggers. I've read the UniData documentation on triggers and am intimately familiar with D3 triggers, so it's no wonder I'm confused about UniData triggers. Questions: 1) Can I create both an update and delete trigger on a file using the same BASIC program or do I need to create two separate programs? In D3 there's an internal function that indicates if the action is an add or delete. This allows a single program to be used for both an update and a delete. 2) How can I tell if a record is being added or changed? 3) Where do the passed variables come from? SUBROUTINE U2.NAMES.BRIDGE.U (ExecStat, DictFlag, FileName, RecIdExpr, RecValue) What specifically is "RecIdExpr"? The record key being updated (documentation says it's the record to be updated)? Is FileName the file name or the "opened" file (file variable)? Do I have to set "DictFlag"? It seems UniData requires a trigger to be defined as either UPDATE or DELETE. Does this mean I have to create two BASIC programs; one for updating and one for deleting? Any assistance would be appreciated. :-) Bill Haskett Advantos Systems, Inc. www.advantos.net (760)944-5570 (CA) (360)923-4838 (WA) --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
