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:
Ronald R Horner <[log in to unmask]>
Reply To:
Ronald R Horner <[log in to unmask]>
Date:
Tue, 5 Dec 2000 15:50:52 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Actually, the stream A command would run.  The reason is that the variable FLAG is
set to "Y".  The first IF tests for "Y" in the FLAG var.  Since the FLAG is not
changed at all, B is not streamed.

Later

By the way, it may not run at all because the variables are not covered with {}.

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)

ATOM RSS1 RSS2