PDSE and HLASM together in z/OS 2.1

2014-02-26 Thread Miklos Szigetvari

Hi

Not so serious problem, in z/OS 1.13 we wrote our SYSADATA to PDSE and
using 0M region size.
In z/OS 2.1 all this jobs ended with an S0F4 reason x'24' and i/O error
with SYSADATA
After a PMR it turned out that the PDSE has not enough storage.
We are using the default assembler OPTION SIZE(MAX) . In this case ,
according the book , the assembler gives back 128 K byte storage, but it
is not big enough for PDSE.
I will change the default SIZE, but maybe the assembler would gives back
something more as 128K ?

--
Kind regards, / Mit freundlichen Grüßen
Miklos Szigetvari

Research  Development
ISIS Papyrus Europe AG
Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria
T: +43(2236) 27551 333, F: +43(2236)21081
E-mail: miklos.szigetv...@isis-papyrus.com
Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111
Visit our brand new extended Website at www.isis-papyrus.com
---
This e-mail is only intended for the recipient and not legally
binding. Unauthorised use, publication, reproduction or
disclosure of the content of this e-mail is not permitted.
This email has been checked for known viruses, but ISIS Papyrus accepts
no responsibility for malicious or inappropriate content.
---


What's the difference between...

2014-02-26 Thread Robert Ngan
I want to define a large field e.g.

Long1DSBL1504What I want

but you can't defined fields longer than 256 bytes, so instead I did:

Long2EQU   *,1504,C'B'   What I need to code
 DS(L'Long2)B...

Is there any real difference between Long1 and Long2, if not then why can't
I use the simpler Long1 syntax?

Robert Ngan
CSC Financial Services Group

Re: What's the difference between...

2014-02-26 Thread Mark Hammack
Not really the answer you are looking for, but why not:

Long1  DS  CL1504  binary data (1 field of 1504 characters)

The assembler should take that and doesn't really care what data you put in
the field.

Or you could try:

Long1 DS 1504B (1504 1 byte values treated as one field)

The first option is a 1504 character long value.  The second is 1504 1 byte
values treated as one field.  I think the only real difference is the
length value.  In the first case L'Long1 gives you 1504, in the second I
believe L'Long1 returns 1 but don't quote me on that (someone else will
point out the error of my ways).


Mark




On Wed, Feb 26, 2014 at 2:08 PM, Robert Ngan rn...@csc.com wrote:

 I want to define a large field e.g.

 Long1DSBL1504What I want

 but you can't defined fields longer than 256 bytes, so instead I did:

 Long2EQU   *,1504,C'B'   What I need to code
  DS(L'Long2)B...

 Is there any real difference between Long1 and Long2, if not then why can't
 I use the simpler Long1 syntax?

 Robert Ngan
 CSC Financial Services Group


Re: What's the difference between...

2014-02-26 Thread John Gilmore
I think it would be worthwhile to propose to John Ehrman that the
maximum for BL fields be upped to 64 kibibytes - 1 (65535).  This is
already the [DS-only] limit for C and X data.  (For DBCS G data it is
64 kibibytes - 2 (65534) for obvious reasons. )

John Gilmore, Ashland, MA 01721 - USA