Page 3 of 3

Re: Problem with call > No active module found

PostPosted: Fri Dec 28, 2012 6:01 pm
by Dashimir
RECFM=FB,LRECL=150 where do i place those comands ? :S

Re: Problem with call > No active module found

PostPosted: Fri Dec 28, 2012 6:45 pm
by steve-myers
Dashimir wrote:RECFM=FB,LRECL=150 where do i place those comands ? :S
  • This is discussed in MVS JCL Reference and MVS JCL User's Guide for your z/OS release. Read the Fine Manual, or as we often say here, RTFM!
  • These are not "commands." They are parameters in a JCL statement. Use the correct terminology.
  • This is really a new topic. Start a new topic when you have a new question!

Re: Problem with call > No active module found

PostPosted: Fri Dec 28, 2012 6:56 pm
by Dashimir
Thank you for the help i will read those links. I fixed by copying another file witch had the right lenght and type.

Re: Problem with call > No active module found

PostPosted: Fri Dec 28, 2012 7:51 pm
by enrico-sorichetti
just copying things around, without understanding why and what You are doing is just a waste of time.

Re: Problem with call > No active module found

PostPosted: Fri Dec 28, 2012 8:26 pm
by dick scherrer
Hello,

There is an incredible amount of mis-communication from Dashimir. Almost everything posted is inconsistent.

I want to edit or resent the file with the format fb and lenght 150 but i dont know how
Only if the data matches these attributes.

How did you get the data into a file on the maniframe? What created the data on the remote system to be uploaded to the mainframe? Why do you believe deleting the file and resending it would help? You need to determine exactly what is in the input file and define the file accordingly in your code.

If you are sending the file via FTP, one thing that often helps is to pre-allocate the target file with the needed attributes on the mainframe and then upload knto this pre-allocated file.

Re: Problem with call > No active module found

PostPosted: Sat Dec 29, 2012 5:38 pm
by NicC
We started off with a program error caused by a file open error caused by a file with incorect DCB attributes (or a program with incorrect DCB attributes) many requests for how the file is being received (note: not the received DCB attributes) blah blah blah. I think time to lock the topic as it has wandered. The cause of the original error has been found wha is causing the mismatch between actual DCB attributes and expected attributes is another topic.