Problem with TSO RECEIVE command
Hi colleagues, I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Thank you very much Fran -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
I don't know if it would work, but I'd try to preallocate the PDS with the correct RECFM / LRECL / BLKSIZE and then do a receive into the existing PDS instead of allowing RECEIVE to create the DSN itself. That may work. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Fran Hernandez Sent: Tuesday, December 14, 2010 7:42 AM To: IBM-MAIN@bama.ua.edu Subject: Problem with TSO RECEIVE command Hi colleagues, I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Thank you very much Fran -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
On Tue, 14 Dec 2010 07:41:42 -0600, Fran Hernandez wrote: I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Need more information. What access method on what device type supports BLKSIZE=51414? Tape? How did you transmit it? by DDNAME? TMP in batch? Or interactive? Can you TRANSMIT to a data set, then RECEIVE from that data set on the same system? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
From the FM: While reading the member from the data set, a record longer than the data set block size was read. Simplest possibility may be that the transfer to the MF did not really work correctly. Perhaps the transferred file is LRECL 80, BLKSIZE 80. What did you use to transfer the file to z/os? -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Fran Hernandez Sent: Tuesday, December 14, 2010 7:42 AM To: IBM-MAIN@bama.ua.edu Subject: Problem with TSO RECEIVE command Hi colleagues, I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Thank you very much Fran -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
On Tue, 14 Dec 2010 09:21:05 -0600, Hal Merritt wrote: From the FM: While reading the member from the data set, a record longer than the data set block size was read. Of course, this is legal if RECFM=VBS, and can not occur if RECFM=FB. (Well, I suppose if you had LRECLBLKSIZE in your DCB. But I believe this causes an ABEND on OPEN.) Simplest possibility may be that the transfer to the MF did not really work correctly. Perhaps the transferred file is LRECL 80, BLKSIZE 80. Open it with ISPF Browse or View and see what happens. And, as I suggested earlier, attempt the RECEIVE on the file before the transfer. In addition, extract a checksum before the transfer, and compare it to a checksum extracted after the transfer. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
Hi colleagues, I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Thank you very much When I do an XMIT/REC typically the outdsn is at 80/3120 or 80/6160. If I try to upload the file outside the 80/6160 it does not receive well. Check the LRECL/BLKSIZE where the Dsn was XMIT'd with OUTDSN and see what it has. I would match the DCB exactly on the upload. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with TSO RECEIVE command
51414 is X'C8D6' which is EBCDIC HO. Perhaps this is really a short Christmas greeting rather than a valid XMIT file? :-) On Tue, Dec 14, 2010 at 7:41 AM, Fran Hernandez frcoh...@gmail.com wrote: Hi colleagues, I have a file in XMIT I try to load on the mainframe. The process of sending the file in binary format of 80 characters work correctly, but when I do the RECEIVE command, I get the following error message: The destination BLKSIZE is 32760 and apparently the source BLKSIZE is 51414: IEB188I MEMBER IN DATA SET REFERENCED BY RECORDS HAS GREATER SYS00130 Than BLKSIZE. LENGTH = 51414 TTR = BLKSIZE = 23200 X'EB85C7 'MBBCCHHR = X'00C7' IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE Any recommendations to solve the problem. The maximum size of all the installation disks BLKSIZE is 32760. Thank you very much Fran -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: problem with TSO receive
sorry for answering so late, but I haven't seen that my response was rejected because of too many appended mails and afterwards I was on a holiday trip. So now again thanks to all for your answers, next time when I'm at the customer site I will try it again with your suggestions. kind regards Franz Josef Pohlen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
problem with TSO receive
Hi listers,
I have a problem with the tso receive command. I enter receive
indataset('BCSYS.JCL.CBT701.XMI') nolog pds. I get the message
INMR152I RECEIVE failed. Your node ID not recognized.
The message explanation says this:
INMR152I RECEIVE failed. Your node ID not recognized.
Explanation: The RECEIVE command failed because the CSECT INMXPARM does
not contain the node ID of the receiving system.
Your installation might not have replaced the IBM-supplied default
CSECT, the node ID might be misspelled or omitted, or INMXPARM might not
be installed correctly.
System Action: The RECEIVE command processor terminates.
User Response: Check the node ID. If it is correct and the problem
persists, notify your system programmer.
Audience: RECEIVE user
Detected by: INMRM
Which node id is meant and where do I have to define it?
Can anybody give me a hint?
Thanks in advance
--
kind regards
Franz Josef Pohlen
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: problem with TSO receive
In a message dated 6/20/2007 8:41:20 A.M. Central Daylight Time,
[EMAIL PROTECTED] writes:
Which node id is meant and where do I have to define it?
Can anybody give me a hint?
Talk to your system's programmer or service provider. It's defined in
IKJTSOxx.
If you have authority you can issue PARMLIB commands to list and update the
values.
The keyword of interest is TRANSREC:
TRANSREC
TRANSREC allows you to specify the characteristics for the RECEIVE and
TRANSMIT commands.
NODESMF{((nodename1,smfid1),(nodename2,smfid2),...)
} {((*,*))}
NODESMF specifies the correspondence between the system identifiers and the
network node names.
nodename
specifies the name of the network node. nodename must be the name of a node
defined on the NJERMT JES3 initialization statement or on the NODE()
JES2 initialization statement.
smfid specifies the system identifier for a particular processor, paired
with a node-name. smfid must be specified for each nodename. smfid must match
the system identifier defined for the processor on the SID parameter of the
SMFPRMxx member.
*,* specifies that the nodename is to be retrieved dynamically from JES
(JES2 Release 4.3.0 or higher, or JES3 Release 5.1.1 or higher). This
specification is recommended because it eliminates the need to specify static
values for
nodename and smfid.
Default: (NODENAME, SMF)
Note: If you omit the smfid for the host node, TSO/E uses a value of eight
question marks () for the nodename associated with the transmitted
data.
SPOOLCL(spoolclass
)
** See what's free at http://www.aol.com.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: problem with TSO receive
It appears you are mixing TRANSMIT operands with the RECEIVE command,
but I don't believe omitting the operands will change your outcome.
Based on your error message does the output from the MVS Command D
IKJTSO,TRANSREC and JES2 Command D MASDEF,XCFGRPNM agree?
Regards,
Kevin
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 6:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: problem with TSO receive
Hi listers,
I have a problem with the tso receive command. I enter receive
indataset('BCSYS.JCL.CBT701.XMI') nolog pds. I get the message
INMR152I RECEIVE failed. Your node ID not recognized.
The message explanation says this:
INMR152I RECEIVE failed. Your node ID not recognized.
Explanation: The RECEIVE command failed because the CSECT INMXPARM does
not contain the node ID of the receiving system.
Your installation might not have replaced the IBM-supplied default
CSECT, the node ID might be misspelled or omitted, or INMXPARM might not
be installed correctly.
System Action: The RECEIVE command processor terminates.
User Response: Check the node ID. If it is correct and the problem
persists, notify your system programmer.
Audience: RECEIVE user
Detected by: INMRM
Which node id is meant and where do I have to define it?
Can anybody give me a hint?
Thanks in advance
--
kind regards
Franz Josef Pohlen
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: problem with TSO receive
Kevin, I think you meant to stated the JES2 command is $DMASDEF,XCFGRPNM, rather than making it look like a D MASDEF,XCFGRPNM Lizette It appears you are mixing TRANSMIT operands with the RECEIVE command, but I don't believe omitting the operands will change your outcome. Based on your error message does the output from the MVS Command D IKJTSO,TRANSREC and JES2 Command D MASDEF,XCFGRPNM agree? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: problem with TSO receive
I apologize for any confusion. I didn't want to assume the CONCHAR so I prefaced it with JES2 Command instead. Regards, Kevin -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Lizette Koehler Sent: Wednesday, June 20, 2007 9:02 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: problem with TSO receive Kevin, I think you meant to stated the JES2 command is $DMASDEF,XCFGRPNM, rather than making it look like a D MASDEF,XCFGRPNM Lizette It appears you are mixing TRANSMIT operands with the RECEIVE command, but I don't believe omitting the operands will change your outcome. Based on your error message does the output from the MVS Command D IKJTSO,TRANSREC and JES2 Command D MASDEF,XCFGRPNM agree? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
