SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 03 | September | 2002 ]

<< Previous Message << >> Next Message >>


Date: Tue, 3 Sep 2002 18:25:31 PST7
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: REXX SYSFILESYSTEMTYPE command

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven:

> Because some other REXX script registered it and left it registered.

NO! NO! That's not happening here. Here's the sequence:

1. I make SURE that the REXX Utility functions are NOT registered. I use
another REXX script (which I have) to do this. Using that script I can:
a.) register the utility functions; or b.) deregister them; or c.)
query their registration status

2. Therefore, I use this script to make SURE the REXX Utility functions
are NOT registered. That is, I query their status. If needed I then
deregister them. Finally, I query the status again to make SURE they are
NOW not registered

3. Immediately folowing that, I run the REXX script with the
SysDriveMap() and SysFileSystemType() commands in them. This script does
not at any time register the REXX Utility functions (I later fixed that)

4. After running the second script (step 3, directly above) I query the
status of the REXX Utility functions. Now they are registered?????

Got it?

In the long scheme of things, this inconsistency is probably not
important. However, I would like to know if it does the same on your
system (on everyone's system).
HCM

______________________________________________________________________________

Steven Levine wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <3D755FF9.C04E7551@attglobal.net>, on 09/03/02
> at 05:21 PM, Harry Chris Motin said:
>
> >I forgot all about that. However, something very curious is happening on
> >my system. I would like your input. Apparently, I can run my REXX script
> >without out first registering the REXX Utility functions???? Why????
>
> Because some other REXX script registered it and left it registered.
>
> While it is a good idea to deregister private REXX libraries when you are
> done with them, the use of REXXUtil is so pervaisive, there's not much
> benefit to doing this. I already register it, just in case, and leave it
> registered on exit. The next script that needs it runs a bit faster. :-)
>
> >I find that the REXX Utility functions are now registered, directly and
> >right after I ran the script fro step #2, above
>
> >Do you have any thoughts on this?
>
> I suspect something changed and nothing gets unloaded until every session
> unloads the library. Try this which is even simpler than your test case:
>
> /* REXX */
> say 'rxfuncquery sysloadfuncs' RXFUNCQUERY("SYSLOADFUNCS")
> say 'rxfuncquery sysdropfuncs' RXFUNCQUERY("SYSDROPFUNCS")
> say 'rxfuncquery sysdrivemap' RXFUNCQUERY("SYSDRIVEMAP")
> CALL SysDropFuncs
> say 'rxfuncquery sysloadfuncs' RXFUNCQUERY("SYSLOADFUNCS")
> say 'rxfuncquery sysdropfuncs' RXFUNCQUERY("SYSDROPFUNCS")
> say 'rxfuncquery sysdrivemap' RXFUNCQUERY("SYSDRIVEMAP")
> Map = SYSDRIVEMAP()
>
> The behavior does not match the documenation.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ---------------------------------------------------------------------
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 03 | September | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.