More explicitly, the JCL reference manual states:
"Use comparison operators in a relational-expression to compare a
keyword with a numeric value."
This doesn't directly address the special case where two numeric values
(after substitution) are being compared - in fact nowhere is it stated
that co
http://www.stuff.co.nz/business/industries/3042830/Air-NZ-report-to-stay-secret
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the
Sounds like an opportunity for IBM to make some changes. I understand 71
for HLASM.. but 98 seems a bit arbitrary. Seems like some sort of
utilization option for HLASM for Metal C might be in order.
IBM Mainframe Discussion List wrote on 11/08/2009
05:46:10 PM:
> [image removed]
>
> MET
Just curious what source line width most people are using for METAL C programs.
The C compiler supports wider than 80 columns, which is liberating. However, the
area on the compiler listing data set (SYSCPRT) is only 98 columns, meaning
long source lines will wrap, which is ugly. And, the C sou
>Does anyone know which address space the TSO Logon exits run in. We are
>considering adding a system specific lookup to the logon process and I need
>to allocate the database somewhere and would probably prefer to use JCL
>rather than dynamic allocation (a little less coding for my successors to
In ,
on 05/19/2009
at 06:03 PM, Timothy Sipples said:
>The new Apache-based IBM HTTP Server for z/OS (i.e. IBM HTTP Server V7.0
>for z/OS) is available at no additional charge to every z/OS customer.
>FMID is HHAP700. The http://www.oss4zos.org site has a good write-up on
>the front page: clic
6 matches
Mail list logo
