Hello list,
I have an application that may have to write DASD files very variable in size.
These files are dynamically allocated as SMS managed files (using DALSTCL,
DALMGCL and DALDACL) and with text unit DALRLSE (equivalent of the RLSE JCL
keyword) so that unused space is released from the
Ah, 878's in DFHSM takes me back to about 1988. Fun times - for ME but
probably not for the customer or DFHSM Development. :-)
The debacle at a well-known UK customer got the Virtual Storage estimates
in the manual fixed and helped spur Development on to move stuff above the
line.
Cheers,
We are having a very busy system as well (for example 15 volume migration
tasks, 13 recycle tasks, and 10 recall tasks running) hence couple of things
being discussed are :
Time to run HSM's major functions(recycle/migration etc) to
ensure you have them spread out as much as possible.
consider
It sounds like you are not using Dynamic Volume Count or Partial Space release.
Dynamic volume count allocates the 1st extent on the 1st volume and dynamically
adds volumes to the list, up to the architectural max of 59. It is not
necessary to specify (for example) 10 volumes in JCL. It is
Good day !!!
I'm looking on how to implement DB2 and its large page support.
One question ...
Suppose I allocate an LFAREA of 4.5 GB based on the fact that the fixed DB2
bufferpools use 4GB.
Then my DBA requests to dynamically ALTER the bufferpool to 5GB. What's happen
then?
a - Is it
My current employer only has one shared ID for IBM electronic support, used by
all platforms. The last few years, it's just become too painful to use the
online facility, so I'm back to using the 800 number exclusively. Welcome to
the 1980's! Once a pmr has been opened, emails can be used
We are a z/OS 1.13 shop and encountered an S878 as well. There is an APAR
OA39358 with fix # UA65499.
I have applied this fix to my system and have not had a re-occurrence.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ravi
W dniu 2012-10-18 13:42, Peter Relson pisze:
The general rule of system commands is:
If you enter something that is documented as valid, it will work or we
will fix the code or the documentation.
If you enter something that is not documented as valid, no assumption
about what you will get is
On Thu, 18 Oct 2012 07:53:52 -0500, Mauri Kanter itzuv...@013.net.il wrote:
Good day !!!
I'm looking on how to implement DB2 and its large page support.
One question ...
Suppose I allocate an LFAREA of 4.5 GB based on the fact that the fixed DB2
bufferpools use 4GB.
Then my DBA requests to
Hi Mauri,
We have done this in all but our largest data sharing Sysplex which is
scheduled next month.
Currently there is an open interesting APAR OA39941.
If you exceed 80% of Large Pages you will get an exciting red hi-lite message
from SRM.
Nothing bad may happen but some ISV products may
I have a program written in LE C++ that is among other usages designed to be
callable from a COBOL (or potentially other LE) program. I recently changed
the program to run POSIX(ON) because it is now sometimes calling the GSK
crypto routines.
Now, when I call it from a COBOL program I get the
Mark, Sam,
Thank you for your prompt answers !
Mauri.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Sam,
I am curious was your CEEPIPI and assembler driver to call and establish
separate tasks?
Scott ford
www.identityforge.com
Tell me and I'll forget; show me and I may remember; involve me and I'll
understand. - Chinese Proverb
On Oct 18, 2012, at 10:50 AM, Sam Siegel s...@pscsi.net
Did you verify that the entry point address in the D
PROG,EXIT,EN=SYS.IEFU83,DIAG was valid and pointed to the correct address in
storage?
Was the first bit set correctly in the EPADDR to reflect 31-bit addressing?
Rob Scott
Lead Developer
Rocket Software
77 Fourth Avenue . Suite 100 .
Doesn't have to be guaranteed space - can get the same effect with an
Extended Sequential SMS dataset with Storage Constraint Relief enabled if your
primary allocation exceeds the space available on one volume.
Agreed. However, it seems like that might be influencing the initial
the C/C++ needed to be callable from non-POSIX COBOL.
It's worse than that. POSIX anything is not even callable from POSIX COBOL.
That's how the message reads, and I just verified by running the COBOL
program //CEEOPTS DD * POSIX(ON)
What a PITA!
LE. G.
Am I reading what you say to
On Thu, Oct 18, 2012 at 9:28 AM, Charles Mills charl...@mcn.org wrote:
the C/C++ needed to be callable from non-POSIX COBOL.
It's worse than that. POSIX anything is not even callable from POSIX COBOL.
That's how the message reads, and I just verified by running the COBOL
program //CEEOPTS
On Thu, Oct 18, 2012 at 7:58 AM, Scott Ford scott_j_f...@yahoo.com wrote:
Sam,
I am curious was your CEEPIPI and assembler driver to call and establish
separate tasks?
Yes - From my reading of the DOC, each TCB can have
a separate and independent LE ENCLAVE. This has proven to be true and
Don't have C/C++ compiler, so cannot test this, but could a new pthread be used
instead of an intermediate ASM program in order to get a new LE enclave on the
new thread (TCB)?
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N.
How about Resource Action. Laid off. Fired. Downsized. Rightsized. All mean
pretty much the same thing.
Tom Chicklon
---
RA? I suspect resource allocation or thereabouts, but??
Deep cost cutting and USA staff that has been
RA'ed to the max, leaving sketchy support
Do anyone know that ? :
http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.bpxb100/sdd.htm
This change the behaviour of your current address space, making each ATTACH
to create a new Unix process (Dubbing), each one having its own enclave
and then maybe their own
I really appreciate the flexibility IBM demonstrates in the last sentence:
Be running with POSIX(ON) and have set the environment variables to signal
that you want to establish a nested enclave. You can use the __POSIX_SYSTEM
environment variable to cause a system() to establish a nested enclave
On Thu, Oct 18, 2012 at 10:34 AM, Charles Mills charl...@mcn.org wrote:
I really appreciate the flexibility IBM demonstrates in the last sentence:
Be running with POSIX(ON) and have set the environment variables to signal
that you want to establish a nested enclave. You can use the
Hello
I have a requirement where the input file is comming from a thrid party system
and each of the files is having different logical record lengths. Once the file
cam i have to use the file and encrypt the customer number that is there.
Please let me know how in a single cobol program we
Ah. Sure. It seems so obvious now...
On Thu, Oct 18, 2012 at 1:05 PM, Gross, Randall [Primerica]
randy.gr...@primerica.com wrote:
IIRC, it was resource action, but it was seven years ago when it
happened to me.
-Original Message-
From: IBM Mainframe Discussion List
How are your jobs submitted when the files arrive? Do you use a scheduling
software that can monitor for the dataset names? Or is it a manual submission?
Are you going to use hard coded dataset names in the JCL or are you going to
use symbolics?
Are all files being read at the same time by
I disagree. If 'NO', 'No', and 'no' are acceptable, 'nO' should be
too. The obvious ways to make the first three interchangeable---using
one of the HLASM macro-language LOWER or UPPER BIFs or the
like---would indeed make 'nO' admissible too. A line or two of ad hoc
code would be re
On
Two problems here, right?
1. How can a COBOL program handle an input file with a variety of fixed (?)
record lengths.
2. How can a COBOL program encrypt a field?
Answers:
1. I'm not much of a COBOL guy but I am going to guess you need three different
FD's and a PARM= that tells it which one
First option: use DFSORT (one step per DSN) to copy your input data. You can
use the OUTREC control card to force the data to be of a standard length,
padding with blanks or x'00' or whatever. Then process the new, padded, data
sets using normal COBOL.
===
Now, if you could make the file
1. How can a COBOL program handle an input file with a variety of fixed
(?) record lengths.
- Write small Hlasm program that returns record pointer and length. It
can handle all RECFM.
- Multiple file definitions, each defined as OPTIONAL. Open each and look
at file status to see which one
Not much to disagree with, is there? (My really appreciate was sarcastic;
did I fail to make that clear?) My sarcasm referred to their lack of
flexibility with regard to enclaves and POSIX; not to their flexibility or
lack thereof with regard to specifying the option.
I have not run a test; I
The manual writer was being silly. The point he or she should have
made was that the value was not case-sensitive. For 'no', there are
only 2^2 = 4 possible case variants; but for 'yes' there are 2^3 = 8;
and for 'maybe' there are 2^5 = 32. Enumeration breaks down very
quickly.
I doubt that
On Thu, 18 Oct 2012 11:14:30 -0700, Charles Mills wrote:
You're right: it would arguably be harder to write code that accepted NO,
No, and no but not nO.
Not necessarily; the programmer could easily have coded 3 switch/case/SELECT
labels for the branches considered plausible. Easier to code
On Thu, 18 Oct 2012 12:43:00 -0500, Ron Thomas wrote:
I have a requirement where the input file is comming from a thrid party
system and each of the files is having different logical record lengths. Once
the file cam i have to use the file and encrypt the customer number that is
there.
For all I know it might be one of the new z/EC12 instructions.
Might be hard to do in hardware. You need locale information. What is the
upper-case of 汉字/漢字?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Dragging this thread kicking and screaming back to the OP, yup, it works. I
had generic C-callable ATTACH, WAIT, and DETACH functions in assembler. I
wrapped some minimal C around them and voila! Only about 3 or 4 hours wasted
on this stupid, stupid bit of design idiocy.
Charles
-Original
Yes, sorry to the non-ex-IBMers. RA is resource action. Their term for the
quarterly layoffs.
Dana
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
My point was of course that case independence makes all of 'no', 'nO',
'No', 'NO' interchangeable in use. In PL/I one writes, say,
arg = lower(argument) ;
match = (arg = 'no') ;
or, indifferently,
arg = upper(argument) ;
match = (arg = 'NO') ;
The same thing can be done in C, using all but
On Thu, 18 Oct 2012 18:03:46 -0400, John Gilmore wrote:
arg = upper(argument) ;
match = (arg = 'NO') ;
The same thing can be done in C, using all but identical assignment
statements (although the variable declarations for them must be
But why bother when you can use the standard library
It is difficult for me to avoid the conclusion that Paul Gilmartin's
latest post in this thread was disingenuous. He is not, moreover, the
only or, certainly, the most egregious offender. There is much
anecdotal evidence that secondary-school debating-society posts all
but empty of substantive
I don't get letting well educated and highly experience professionals go.
Who do companies think will handle these systems ? Outsourcing , not
Scott ford
www.identityforge.com
Tell me and I'll forget; show me and I may remember; involve me and I'll
understand. - Chinese Proverb
On Oct 18,
Staller, Allan wrote:
snip
It sounds like you are not using Dynamic Volume Count or Partial Space release.
Dynamic volume count allocates the 1st extent on the 1st volume and dynamically
adds volumes to the list, up to the architectural max of 59. It is not
necessary to specify (for example) 10
42 matches
Mail list logo
