On Sat, 8 Nov 2014 00:09:20 +, Mark Steely wrote:
> I have several STC that I need to setup a different RptClass for each one.
> These STC are in the same Workload class.
> What are the steps to get this setup in WLM.
I fail to see what we can add to the descriptions in the Planning WLM
On Fri, 7 Nov 2014 06:14:09 -0500, John Gilmore wrote:
>Unlike people of later generations, who had hexadecimal calculators
>available to them ab initio, I can do mental hexadecimal arithmetic
>and decimal<==>hexadecimal conversions quickly because I had to be
>able to do so.
I still have trouble
First, if you have not done so, there is a TSO REXX list that might be helpful
as well.
You can join at this URL (go to the bottom of the webpage) \
http://www2.marist.edu/htbin/wlvindex?TSO-REXX
Second check your route codes for your consoles. That may have some impact on
this.
Lizette
>
I have several STC that I need to setup a different RptClass for each one.
These STC are in the same Workload class.
What are the steps to get this setup in WLM.
Any help would be appreciated.
Thanks
*** CONFIDENTIALITY NOTICE ***
This e-mail message and all attachments transmit
I have a REXX exec that issues a WTO with routing and descriptor codes both
equal to 2. When I run it from my TSO userid, the message is written to the
console (highlighted), but when I run it from a batch job (either IKJEFT01 or
IRXJCL), the message appears in my joblog and in OPERLOG (highligh
I interpreted the original post as an attempt to recover from the classic
mistake writing to a PDS using IEBGENER.
I suspect the original PDS, before corruption, was VBA137. With BLKSIZE 27920.
The correct fix is to write a new member using IEBGNER and the correct DCB
specified on SYSUT2. Given
W dniu 2014-11-07 o 16:13, John Dawes pisze:
G'Day,
Just wondering if it is possible to copy a pds with the following attributes:
INPUT DSN:
RECFM=U
LRECL=137
BLKSIZE=32760
OUTPUT DSN:
REDFM=VBA
LRECL=137
BLKSIZE=27920
(appendix).
First, try to copy the PDS to another RECFM=U PDS, or simp
W dniu 2014-11-07 o 16:13, John Dawes pisze:
G'Day,
Just wondering if it is possible to copy a pds with the following attributes:
INPUT DSN:
RECFM=U
LRECL=137
BLKSIZE=32760
OUTPUT DSN:
REDFM=VBA
LRECL=137
BLKSIZE=27920
I think nobody pointed this: RECFM=U means there are no records. In th
At 06:14 -0500 on 11/07/2014, John Gilmore wrote about Re: System vs.
user ABEND codes:
At most four decimal digits are required to represent any 12-digit
binary value, and at most three hexadecimal digits are required to
represent one. Anciently, a useful display distinction betrween Sxxx,
sy
At 07:13 -0800 on 11/07/2014, John Dawes wrote about UNABLE TO COPY PDS.:
G'Day,
Just wondering if it is possible to copy a pds with the following attributes:
INPUT DSN:
RECFM=U
LRECL=137
BLKSIZE=32760
OUTPUT DSN:
REDFM=VBA
LRECL=137
BLKSIZE=27920
Below are the error messages:
IEB120I INDD
I apologize for not having read the whole thread. So I might be repeating
information
typically when someone uses a utility like IEBGENER with DCB attributes it will
cause this type of error.
If you have a backup of the file, bring it back down to dasd and look at the
attributes. Is it the sa
On Tue, 4 Nov 2014 14:30:54 -0800, Charles Mills wrote:
>I always wondered why did they put two more or less mutually-exclusive data
>in two different 12-bit fields? If they had devoted 11 bits to the ABEND
>code and one bit to system versus user, we could have had ABEND codes
>ranging up to S7FFF
I'm confused. The original message came from John Dawes. How (and why) did
you get access to his PDS?
In any event, I suggest you use IEBPTPCH to dump the directory treating it as a
sequential file with RECFM=U and BLKSIZE=32760. Verify that the TTRs for the
members look reasonable.
Repeat
I guess that the PDS directory has been corrupted. If so, try reading
the PDS as a sequential file to extract/dump the directory
(RECFM=VB,BLKSIZE=256) and check that.
If it fails try resetting the PDS directory by opening it for output and
then closing it, e.g. with something like this:
***
On Fri, 7 Nov 2014 07:13:11 -0800, John Dawes wrote:
>
>Just wondering if it is possible to copy a pds with the following attributes:
>
>INPUT DSN:
>
>RECFM=U
>LRECL=137
>BLKSIZE=32760
>
>OUTPUT DSN:
>REDFM=VBA
>LRECL=137
>BLKSIZE=27920
>
I have done this with some success with IDCAMS/TSO REPRO.
Is it possible the DCB was overwritten. Do you have a way to determine if the
recfm, lrecl & blksize has changed and that’s why the I/O's error are
occurring.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Willie Bunter
Sent: Frida
I browsed most of the members and I am getting the I/O errors.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Does the problem occur with only one member? Is the presumed corruption in the
member or is it in the directory?
Consider what would have happened if this had worked. An input record which
consists of
BDW-RDW-data-RDW-data...
would be treated as monolithic due to the RECFM=U. The resu
G'Day,
Just wondering if it is possible to copy a pds with the following attributes:
INPUT DSN:
RECFM=U
LRECL=137
BLKSIZE=32760
OUTPUT DSN:
REDFM=VBA
LRECL=137
BLKSIZE=27920
Below are the error messages:
IEB120I INDD VALIDATION ERROR
IEB127I RECFM INCOMPATIBL
That should be "the former often has the PIC in plain view." In the case
of S0C4, that's only true if the S0C4 is PIC 4.
On 2014-11-07 06:23, Martin Packer wrote:
And the former has the PIC in plain view in.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer
And the former has the PIC in plain view in.
Cheers, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/myde
At most four decimal digits are required to represent any 12-digit
binary value, and at most three hexadecimal digits are required to
represent one. Anciently, a useful display distinction betrween Sxxx,
system, and U, user, ABEND codes was usual and convenient.
It had about it an element of
22 matches
Mail list logo
