HP3000-L Archives

December 2000, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Barnes <[log in to unmask]>
Reply To:
Larry Barnes <[log in to unmask]>
Date:
Tue, 5 Dec 2000 14:56:06 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
Jeff,

I get the following results.  I tried both in a job stream and a command file run
with MPEX.  In both cases the results were the same.

print test.jcl
::assign flags = "Y"
::if flags = 'Y'
:: echo the flag is set to yes
::endif
::if flags = 'N'
:: echo the flag is set to no
::endif

%
%test.jcl
the flag is set to yes




Jeff Keepers wrote:

> Oh great wise ones,
>
> I am documenting a job for the HP3000 that has me confused.  This job has a
> mixture of pre-process mpex commands and JCL.  As I understand how things work,
> when the job is batched, the pre-process mpex commands are processed and then
> the JCL commands.  This particular job seems to do things different.  The
> following is an example:
>
> ::assign flag = 'Y'
> ::if flag = "Y" then
> ::   echo "flag = Y"
> !   STREAMX A
> ::endif
> ::if flag = "N" then
> ::   echo "flag = Y"
> !    STREAMX B
> ::endif
>
> When job is run, the pre-process code decides if A or B is run.  When I look at
> it I would say that it would do all of the pre-process commands and then run
> BOTH A and B.  Any insight on why the job does what it does would be
> appreciated.
>
> Sincerely,
> Jeff (AKA. Dazed and Confused)

--
Larry Barnes
Director of I.T.
Mitek Corp.
602-438-4545 x1366
Phoenix, AZ 85040

Check Us Out !
http://www.mitekcorp.com

ATOM RSS1 RSS2