Re: [U2] _PH_ ID

[john reid]

Looks like it.
j

1 PHANTOM SQUAWK HI
R.MIPAHC>.X

PHANTOM SQUAWK HI
HI_29256_14421 record has been created in the '&PH&' file.
Phantom process started with process ID 27052.
R.MIPAHC>


On 6/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

If the "HI" program has been cataloged, though, you can do

PHANTOM HI

And the first "_" field of the id would then be HI instead of RUN.

You can then use the program name to find the ID in the &PH& file.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of john reid
Sent: Thursday, June 21, 2007 9:01 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] _PH_ ID

Universe 10.x

>PHANTOM SQUAWK RUN JMRBP HI
RUN_36022_14417 record has been created in the '&PH&' file.
Phantom process started with process ID 7408.


On 6/21/07, Kevin King <[EMAIL PROTECTED]> wrote:
> Is there a way for a phantom to know the _PH_ item that it's output is
> being redirected to?
>
> -Kevin
> [EMAIL PROTECTED]
> http://www.PrecisOnline.com 
>
> ** Check out our FREE support forum at
> 
> http://www.PrecisOnline.com/forum/.
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
>


--
john
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _

The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material not 
intended for Public use.
Any review, retransmission, dissemination or other use of, or taking of any 
action in reliance upon, this information by persons or entities other than the 
intended recipient is
strictly prohibited. If you received this communication in error, please notify 
the sender and delete the material from any and all computers or devices.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/




--
john
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

[U2] [AD] Employment Opportunity - Midland, Texas

[Bruce McAdoo]

 Programmer/Analyst

Oil & Gas company is currently seeking a programmer with 5+ years
experience.  Multivalue (preferably unidata) skills are desired.
Knowledge of oil & gas accounting a plus.  Understanding of web design,
Visual Basic, and other Microsoft products would be helpful. Excellent
benefits and competitive salary.  Please forward confidential resume and
salary history to:

Wagner & Brown, Ltd.
Attn: Human Resources Manager
P.O. Box 1714
Midland, Texas 79702
432-686-5906
432-686-1503 (fax)

Bruce W. McAdoo
Wagner & Brown, Ltd.
[EMAIL PROTECTED] 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] [UV] Trigger(s) on distributed file

[Jerry Banker]

No, the DEFINE.DF command creates a data file and a dictionary. They are
actual files on the disk. However you cannot access the type 27 data
file. You can only list or add records if you have at least one part
file added. The type 27 file has a modulus of 1.

-Original Message-
From: Anthony W. Youngman [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 23, 2007 4:32 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV] Trigger(s) on distributed file

In message 
<[EMAIL PROTECTED]>, 
Jerry Banker <[EMAIL PROTECTED]> writes
>We use distributed files and yes a master file is created. The
DEFINE.DF
>command creates a type 27 file and a dictionary file is created that is
>a type 30 file.
>As a matter of fact we use the one dictionary for all of the part
files.
>
Ah. This gives me an idea.

Did you explicitly create a master distributed file?

I used to create them with the following sequence:

CREATE.FILE DICT MASTER.
CREATE.FILE DATA MASTER.1
DEFINE.DF MASTER. ADDING MASTER.1 PART 1

(or whatever the correct syntax is). I'm guessing that because I 
explicitly didn't create the data portion, it didn't get created ... :-)

It still worked fine...

Cheers,
Wol
-- 
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The
man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site -  Open Source
Pick
---
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] RE: [UD] BSELECT @SYSTEM.RETURN.CODE anomaly

[Dean.Armbruster]

My apologies for the poor job I did posting this.  I sent it before I
had completed the subscribe procedures.  I blame it on my vacation.  :-)

Because of my mistake, I didn't get the replies.  I had to get them from
the list archive.  Here are my replies to the replies:


To Dave Davis, who said, "If you were curious about the number of
customers queried couldn't you just do a SELECT CUSTOMER first?"

I agree.  Or, if you had done a previous select to whittle down the
list, you'd already know how many records would be queried for the
BSELECT.


To David A. Green, who said, "SYSTEM(11) returns number of items in the
active select list.  I think we should leave the @SYSTEM.RETURN.CODE as
the number of records
selected."

@SYSTEM.RETURN.CODE is NOT the number of records selected.  That is the
problem.  It is the number of records queried/polled, not the number of
items returned in the select list.  Those numbers will not be the same
for a multivalued attribute or if the attribute is null and UDT.OPTION
59 is ON.

Try this and see if you feel the same way about @SYSTEM.RETURN.CODE:

EXECUTE 'UDT.OPTIONS 59 ON'
CMD1 = 'BSELECT CUSTOMER WITH @ID GE "200" TAPES_RENTED'
CRT CMD1
EXECUTE CMD1
IF @SYSTEM.RETURN.CODE GT 0 THEN
  CMD2 = 'DELETE TAPES'
  CRT ; CRT CMD2
  EXECUTE CMD2
END

SYSTEM(11) is our workaround.  But it is a pain because:
A) It is non-standard, i.e. not necessary for other SELECTs.
B) It is not what the documentation says.  BASR.pdf states that
@SYSTEM.RETURN.CODE will contain the number of items in the select list.
C) If the program reports errors, it must first check
@SYSTEM.RETURN.CODE, and if okay then check SYSTEM(11).



> -Original Message-
> From: Moderator [mailto:[EMAIL PROTECTED] 
> Sent: Friday, June 22, 2007 6:15 PM
> To: u2-users@listserver.u2ug.org; Dean Armbruster - 0018 HQ
> Subject: [UD] BSELECT @SYSTEM.RETURN.CODE anomaly
> 
> REPOSTED FOR NON-MEMBER ADDRESS: <[EMAIL PROTECTED]>
> 
> I'd looking for feedback on @SYSTEM.RETURN.CODE as returned 
> from BSELECT of a multivalue attribute.
> 
> Run the following basic code in the UniData demo account:
> 
> CMD = 'BSELECT CUSTOMER TAPES_RENTED'
> CRT CMD
> EXECUTE CMD
> CRT '@SYSTEM.RETURN.CODE = ':@SYSTEM.RETURN.CODE CLEARSELECT
> 
> When I run it, I get:
> 
> BSELECT CUSTOMER TAPES_RENTED
> 
> 36 records selected to list 0.
> 
> @SYSTEM.RETURN.CODE = 29
> 
> 
> Note that 29 is the number of records in CUSTOMER; 36 is then 
> number of items in the returned active select list.
> 
> 
> The questions:  Is there any way a program could depend on 
> @SYSTEM.RETURN.CODE being incorrect some of the time?  Would 
> anyone want @SYSTEM.RETURN.CODE to be the number records 
> polled and not number of items in the returned list, even if 
> the number of items returned is 0?
> 
> 
> IBM case #423086*USA
> 
> UniData 6.1.18
> HP-UX 11.11
> ECLTYPE P
> UDT.OPTIONS 59 ON
> 
> 
> Dean Armbruster
> System Analyst
> Wolseley North American Division * 12500 Jefferson Avenue * 
> Newport News
> * VA * 23602-4314
> T: +1(757) 989-2839 * F: +1(757)989-2801
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] [UV] Trigger(s) on distributed file

[Boydell, Stuart]

So, in the case where a part file belongs to several master files, and a
record is added through one of the master files; and the part file has a
trigger; how can you determine which master file the record was entered
through?

MASTER1, MASTER2
   \  /
   PARTA   - fires triggerA
   PARTB   - fires triggerB

>ED MASTER2 FRED
   [trigger fires :: tableName = PARTA]

FILEINFO has no info on an open part file and STATUS only tells you that
the current file is a part. No @filename or @stdfil info, can't do
PORT.STATUS MAPFILES ...

>-Original Message-
>A part file can belong to multiple distributed files. You might, for
>example, split your sales into monthly files and have distributed files
to
>represent quarters, years, the whole of history, etc.

 
**
This email message and any files transmitted with it are confidential and 
intended solely for the use of addressed recipient(s). If you have received 
this communication in error, please reply to this e-mail to notify the sender 
of its incorrect delivery and then delete it and your reply.  It is your 
responsibility to check this email and any attachments for viruses and defects 
before opening or sending them on. Spotless collects information about you to 
provide and market our services. For information about use, disclosure and 
access, see our privacy policy at http://www.spotless.com.au 
Please consider our environment before printing this email. 
** 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] [UV] Trigger(s) on distributed file

[Boydell, Stuart]

That should have said: FILEINFO has no info on the master of an open
part file that it's associated with and STATUS only tells you that the
current part file is a part file - again, no master info.

>-Original Message-
>FILEINFO has no info on an open part file and STATUS only tells you
that
>the current file is a part. No @filename or @stdfil info, can't do
>PORT.STATUS MAPFILES ...

 
**
This email message and any files transmitted with it are confidential and 
intended solely for the use of addressed recipient(s). If you have received 
this communication in error, please reply to this e-mail to notify the sender 
of its incorrect delivery and then delete it and your reply.  It is your 
responsibility to check this email and any attachments for viruses and defects 
before opening or sending them on. Spotless collects information about you to 
provide and market our services. For information about use, disclosure and 
access, see our privacy policy at http://www.spotless.com.au 
Please consider our environment before printing this email. 
** 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/