Susan,
Better & Better, the U2UG committee tasked with bringing good ideas to
IBM will be holding a Birds of a Feather session at the IOD. Since
you'll be speaking (twice!) at the IOD Conference, stop by and raise
the issue. IBM has assured us that if B&B brings something up, it will
be considered.
--
Charles Barouch
[EMAIL PROTECTED] - Consulting
[EMAIL PROTECTED] - ETL/Migration/Integration
(718) 762-3884x1
Susan Joslyn wrote:
| Dave, Brian, all,
|
| I get around the problem of the SELECT and COPY syntax differences by
| making
| a copy of the pick-flavored verbs (some platforms already have them) and I
| always execute COPYP and SELECTP and SSELECTP in my BASIC EXECUTE
| statements. Likewise you could create COPYI that is always the prime
| flavored even in a "pick-flavored-account" and then your hard-code can
| execute prime copy syntax -- which, granted, is easier to execute from
| within a basic program because its all on one command line rather than
| hitting return and responding to a prompt...
|
| I have to get even trickier in SB+ -- which will not "officially" run in
| Prime and Reality flavored accounts. I can't get to their source code to
| control the verb, so I continuously swap-out the verb in before-and-after
| routines. And of course I avoid using SB+ for selections when I can. But
| F3 lookups are so fantastic and I'm loathe to reinvent them. So I swap
| out
| the verb when I have to. Yes, it's risky -- there could be a failure by
| another process executing SELECT at the same moment. But -- I minimize
| when
| I use it and I've been lucky.
|
| I've proposed (for years) to IBM that SB+ create the "P" verbs as part of
| the SB-enablement of an account and then change all the source code to
| execute those P-verbs at all times. It's a simple fix, has no downside
| and
| then voila! SB+ runs in all flavors. But I digress. (and fantasize that
| if
| anyone else thinks this is an issue perhaps they'll put their own weight
| behind my request.) :)
|
| Susan
|
|
| ----------------------------------------------------------------------
|
| Date: Mon, 10 Jul 2006 10:52:28 +0100
| From: "Brian Leach" <[EMAIL PROTECTED]>
| Subject: RE: [U2] Universe/NT Rel. 10.0.10: How to run a program written
| and
| compiled in one flavor in another flavor?
|
| Dave
|
| The program flavor and $OPTIONS statement dictate the way the program is
| compiled: determining the specific object code generated. Which means that
| the BASIC code itself will run the same, regardless of the flavor of the
| account in which is runs. What won't work the same, of course, are
| flavor-dependent differences in any commands that you execute.
|
| For some commands, the simplest option is to create and execute your own
| synonyms by copying them from the appropriate flavor VOC. So for HUSH you
| might substitute the PICK flavor HUSH and call it PICK.HUSH. In a couple
| of
| places these are already provided: the COPY command has COPYI and COPYP
| versions in the VOC. Some aren't, e.g. CREATE.FILE has totally different
| syntax depending on flavor.
|
| It's the words 'any other flavor' that stand out. The main thing to catch
| you out is the differences in the enquiry syntax between PICK-like and
| INFORMATION-like flavors. Avoid using metacharacters on selections
| (SURNAME
| = "SMITH]") and use LIKE instead (works across flavors), and ensure that
| you
| use double quotation marks around literals.
|
| Brian
| -------
| 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/
