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 [ 26 | May | 2001 ]

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


Date: Sat, 26 May 2001 12:40:22 PDT
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: errorlevel when piping ?

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 Levine wrote:
>
> the returned errorlevel is the errorlevel
> returned by the last command in the pipe.
...
> If you really need to check failure you are
> going to have to rewrite as:
>
> cmd1 >tmpfile1
> if errorlevel
> cmd2

Thanks, Steven, I was afraid of this. The problem is that I need TEE so
I can see the XCOPY status while it's running (I need to see what files
XCOPY is "currently copying"). If XCOPY was open source GPL, I could
add a command line /TEE:filename (-TEE:filename) option so a pipe
wouldn't be necessary.

> FWIW, cmdref.inf one of the worst of the IBM documents.
> Try finding a definition of what >& or & does.

It's in there, I look at it from time to time. Search on "&" and click
on the two hits titled "Command Operators and Redirecting ...". Don't
try searching on "Command Operators and Redirecting", though -- for some
stupid reason that won't work.

If there was a way to disassemble the .inf files they could be converted
to HTML documents or plain text for "a better viewing experience". I've
never created .inf files but I'm told they're HTML/SGML based. My own
articles are all SGML tagged and I then run them through some of my own
code to create HTML.

Thanks again,

- Peter

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

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 [ 26 | May | 2001 ]



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.