Understanding Error Messages
amir
There is two questions:
1- As mentioned below, there is 6 warnings. Where is exact place for
each-one? How can I find it? Which line?
2- A OBJ file created. How can I run it or link it to make executable
and then run.
Thanks
PP 5648-A25 IBM COBOL for OS/390 & VM 2.2.0
TEST1 Date 05/03/2008 Time 09:54:34 Page 5
LineID Message code Message
text
IGYSC0185-I Messages were issued during library phase
processing. Refer to the beginning of the listing.
1 IGYDS0001-W A blank was missing before character "." in
column 34. A blank was assumed.
1 IGYDS0027-S Non-COBOL character(s) were found starting with
"." in column 34. The characters were discarded.
2 IGYDS0001-W A blank was missing before character "." in
column 28. A blank was assumed.
2 IGYDS0027-S Non-COBOL character(s) were found starting with
"." in column 28. The characters were discarded.
3 IGYDS0001-W A blank was missing before character "." in
column 31. A blank was assumed.
3 IGYDS0027-S Non-COBOL character(s) were found starting with
"." in column 31. The characters were discarded.
4 IGYDS0001-W A blank was missing before character "." in
column 24. A blank was assumed.
4 IGYDS0027-S Non-COBOL character(s) were found starting with
"." in column 24. The characters were discarded.
5 IGYPS0001-W A blank was missing before character "." in
column 29. A blank was assumed.
5 IGYPS0027-S Non-COBOL character(s) were found starting with
"." in column 29. The characters were discarded.
6 IGYPS0001-W A blank was missing before character "." in
column 42. A blank was assumed.
6 IGYPS0027-S Non-COBOL character(s) were found starting with
"." in column 42. The characters were discarded.
Messages Total Informational Warning Error Severe
Terminating
Printed: 13 1 6
6
Arnold Trembley
It looks to me like all the errors occurred on lines 1 thru 6. For
example, the last two messages (IGYPS0001-W and IGYPS0027-S) appear to
both be on line 6. Perhaps you could post the first six lines of the
program.
While there may have been an object file created, the fact that you
have five "severe" errors (the "-S" at the end of some of the message
id's) means the linkedit step will be bypassed. It is not safe to
build an executable program from this compile.
amir
wrote:
I just ran a Hello-Word program:
identification division.
program-id. test1.
environment devision.
data devision.
procedure division.
display "hello" upon console.
Not more.
What's the problem?
Appreciated for your help.
docd...@panix.com
amir <ahsh...@gmail.com> wrote:
>I got messages below after my first program compilation under OS/390.
Congratulations on your attempt and rest easy in knowing that many, many
more messages will follow. It was in one of my early attempts (it might
even have been my first) where I keyed in SOURCE-COMPUTTER... quite the
mess followed.
Now, please do your own homework.
DD
SkippyPB
wrote:
If you refer to your text book you should see that division names must
begin in column 8, not column 1. Cobol commands must begin in at
least column 12.
Regards,
////
(o o)
-oOO--(_)--OOo-
"My dog is worried about the economy because Alpo
is up to $3.00 a can. That's almost $21.00 in dog money."
-- Joe Weinstein
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Remove nospam to email me.
Steve
T. Rex
59g2000hsb.googlegroups.com>, ahsh...@gmail.com says...
> I just ran a Hello-Word program:
So this program supposedly produced those errors, right?
> identification division.
> > > 1 IGYDS0001-W A blank was missing before character "." in
> > > column 34. A blank was assumed.
> >
> > > 1 IGYDS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 34. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 34 of a line that's only 24 characters long. What
program did you really compile?
> program-id. test1.
> > > 2 IGYDS0001-W A blank was missing before character "." in
> > > column 28. A blank was assumed.
> >
> > > 2 IGYDS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 28. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 28 of a line that's only 18 characters long. What
program did you really compile?
> environment devision.
> > > 3 IGYDS0001-W A blank was missing before character "." in
> > > column 31. A blank was assumed.
> >
> > > 3 IGYDS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 31. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 31 of a line that's only 21 characters long. What
program did you really compile?
It's also vanishingly unlikely that the compiler would fail to complain
about the misspelling of "division". What program did you really
compile?
> data devision.
> > > 4 IGYDS0001-W A blank was missing before character "." in
> > > column 24. A blank was assumed.
> >
> > > 4 IGYDS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 24. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 24 of a line that's only 14 characters long. What
program did you really compile?
It's also vanishingly unlikely that the compiler would fail to complain
about the misspelling of "division". What program did you really
compile?
> procedure division.
> > > 5 IGYPS0001-W A blank was missing before character "." in
> > > column 29. A blank was assumed.
> >
> > > 5 IGYPS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 29. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 29 of a line that's only 19 characters long. What
program did you really compile?
> display "hello" upon console.
> > > 6 IGYPS0001-W A blank was missing before character "." in
> > > column 42. A blank was assumed.
> >
> > > 6 IGYPS0027-S Non-COBOL character(s) were found starting with
> > > "." in column 42. The characters were discarded.
It's not possible that the compiler is complaining about something it
found in column 42 of a line that's only 33 characters long. What
program did you really compile?
> Not more.
> What's the problem?
Tell you what -- why don't you copy and paste the *entire* compile
listing, so that we can see what source program you *really* compiled?
It's obviously not the six lines you posted above.
William M. Klein
If you are compiling on OS/390 (or z/OS) and want your error messages to appear
in the source code where the error occurred, check out compiling with the
FLAG(I,I) compiler option.
As others have indicated, it looks likely that you haven't coded your source
code with data in column 7, or column 8 or column 12 where the '85 Standard of
COBOL (and Enterprise COBOL require.
Check out:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/igy3lr40/1.6?
and following pages for the rules for COBOL source code.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:2fc60fd6-485d-4812...@w74g2000hsh.googlegroups.com...
amir
wrote:
> Lots of replies so far (some more useful that others).
>
> If you are compiling on OS/390 (or z/OS) and want your error messages to appear
> in the source code where the error occurred, check out compiling with the
> FLAG(I,I) compiler option.
>
> As others have indicated, it looks likely that you haven't coded your source
> code with data in column 7, or column 8 or column 12 where the '85 Standard of
> COBOL (and Enterprise COBOL require.
>
> Check out:
> http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/igy3lr40/1.6?
>
> and following pages for the rules for COBOL source code.
>
> --
> Bill Klein
Dear Friends,
Thanks all. I compiled with the Flag(I,I) as William said and This is
my compilation result.
I don't know what's wrong exactly.
Best,
T. Rex
25g2000hsx.googlegroups.com>, ahsh...@gmail.com says...
> Dear Friends,
> Thanks all. I compiled with the Flag(I,I) as William said and This is
> my compilation result.
*What* is your compilation result? There's nothing here.
> I don't know what's wrong exactly.
Neither does anyone else, if we can't see it. Post the whole compilation
listing, including the source code and all the errors.
Howard Brazee
wrote:
>I just ran a Hello-Word program:
>identification division.
>program-id. test1.
>environment devision.
>data devision.
>procedure division.
> display "hello" upon console.
>Not more.
>What's the problem?
>Appreciated for your help.
Have you compiled on a Vax before where you can start in column 1, or
was your program written in the correct IBM columns but displayed
differently here?
Do you have your compiler settings set to show your listing?
tlmfru
lines. And 'division' is twice mis-spelled.
Howard Brazee <how...@brazee.net> wrote in message
news:4o4u145949p8jcui3...@4ax.com...
T. Rex
> All the error messages so far shown indicate garbage on the RHS of the
> lines. And 'division' is twice mis-spelled.
Hence my insistence that what he posted cannot possibly be what he
compiled.
amir
I tried a sample code as I told before. I got some errors which I
could not understand what the problem is?
Anyway, I tried the code to compile under another compiler (MSCobol).
Compilation Result was successful. I tried different parts to change
and everything done with no problem.
Can anyone help me to write my program under MVS and compile it? (I am
using ISPF editor)
Any help appreciated before.
(Special Thanks to DD about help to solve some problems.)
Thanks,
William M. Klein
don't ever show it.
My guess (and everyone else's) is that you have your code in the wrong columns.
(Starting in column 1 might work on a PC - but will NEVER work on the
mainframe).
If you would just do as you have been asked, you MIGHT get a useful reply.
If you don't know HOW to get the listing (with source code and error messages)
on MVS, then ask someone at the site that gave you JCL to compile there.
However, as I say, I think your source code just starts in the wrong column and
you have never answered any of us who have suggested that this is the problem.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:9d89bc65-3acd-4417...@e39g2000hsf.googlegroups.com...
docd...@panix.com
amir <ahsh...@gmail.com> wrote:
[snip]
>Can anyone help me to write my program under MVS and compile it? (I am
>using ISPF editor)
>Any help appreciated before.
>
>(Special Thanks to DD about help to solve some problems.)
I would blush, if I could remember how to. You are trying to learn a
moderately intricate platform and software tools, something that is not
usually done in the stillness of a small, dark room.
Is there a reason you know of that your boss has not said to one of his
MVS-qualified workers 'sit down with this fellow and show him the basics'?
There may be better ways to make use of study-time.
DD
amir
wrote:
> Everyone has asked for you to show the LISTING with the problems under MVS. You
> don't ever show it.
>
> My guess (and everyone else's) is that you have your code in the wrong columns.
> (Starting in column 1 might work on a PC - but will NEVER work on the
> mainframe).
>
> If you would just do as you have been asked, you MIGHT get a useful reply.
>
> If you don't know HOW to get the listing (with source code and error messages)
> on MVS, then ask someone at the site that gave you JCL to compile there.
>
> However, as I say, I think your source code just starts in the wrong column and
> you have never answered any of us who have suggested that this is the problem.
>
> --
> Bill Klein
>
> news:9d89bc65-3acd-4417...@e39g2000hsf.googlegroups.com...
>
> >I tried to run my first program under MVS as I said before.
>
> > I tried a sample code as I told before. I got some errors which I
> > could not understand what the problem is?
> > Anyway, I tried the code to compile under another compiler (MSCobol).
> > Compilation Result was successful. I tried different parts to change
> > and everything done with no problem.
>
> > Can anyone help me to write my program under MVS and compile it? (I am
> > using ISPF editor)
> > Any help appreciated before.
>
> > (Special Thanks to DD about help to solve some problems.)
> > Thanks,
I got the file through FTP. I could not cut and paste it. maybe some
special characters, I don't know.
If you specify what peace of code is necessary to help, I will type it
again if needed.
amir
> In article <9d89bc65-3acd-4417-ba91-7c5f990bc...@e39g2000hsf.googlegroups.com>,
>
> amir <ahsha...@gmail.com> wrote:
>
> [snip]
>
> >Can anyone help me to write my program under MVS and compile it? (I am
> >using ISPF editor)
> >Any help appreciated before.
>
> >(Special Thanks to DD about help to solve some problems.)
>
> I would blush, if I could remember how to. You are trying to learn a
> moderately intricate platform and software tools, something that is not
> usually done in the stillness of a small, dark room.
>
> Is there a reason you know of that your boss has not said to one of his
> MVS-qualified workers 'sit down with this fellow and show him the basics'?
>
> There may be better ways to make use of study-time.
>
> DD
Maybe some special configuration like code page maybe did not seted up
in the right manner, I think.
docd...@panix.com
amir <ahsh...@gmail.com> wrote:
>On May 7, 12:28 pm, docdw...@panix.com () wrote:
>> In article
><9d89bc65-3acd-4417-ba91-7c5f990bc...@e39g2000hsf.googlegroups.com>,
>>
>> amir <ahsha...@gmail.com> wrote:
[snip]
>> >(Special Thanks to DD about help to solve some problems.)
[snip]
>> Is there a reason you know of that your boss has not said to one of his
>> MVS-qualified workers 'sit down with this fellow and show him the basics'?
[snip]
>someone told me about working with the editor and I do it, right now.
Once again, with detail: an MVS environment is complex and the data
passing throught it are usually worth Big Money to someone. Is there a
reason you know of that your your boss has not told someone 'sit down with
this fellow and show him the basics'?
(if you are trying to learn this on your own time so you can, as the
correspondence-schools used to advertise on matchbooks, 'Be A Computer
Programmer And Make Big Money!'... the limits of your knowledge may be
exposed very, very quickly)
DD
Howard Brazee
wrote:
>I tried to run my first program under MVS as I said before.
So how do you have access to an MVS machine without an environment
with either teachers, co-workers, or supervisors?
Howard Brazee
wrote:
>I got the file through FTP. I could not cut and paste it. maybe some
>special characters, I don't know.
>If you specify what peace of code is necessary to help, I will type it
>again if needed.
Did you FTP it to your PC? And your PC's OS is not one that I'm
familiar with and does not have cut and paste facilities?
Richard
Under Windows on a PC each line will be terminated by an ASCII CR and
LF character. If you ftped then tyhe file may wind up with whatever
ebcdic value the CR and LF converted to. As the errors indicated the
columns _after_ the actual characters shown then it may be that it
is complaining about these alien values.
Check your FTP manual so that the correct hex values are converted to,
and perhaps strip off the line terminators. This may be as simple as
specifying 'ascii' or 'ebcdic' rather than 'binary' (which it may
default to) in the FTP transfer.
William M. Klein
with IGY). These must have been "visible" to you in a file somewhere. What we
need to see is that entire file with those messages.
P.S. If you are FTP'ing your source code to and from the mainframe, you need to
make certain that it is
DCB=(LRECL=80,RECFM=F) (or FB) on the mainframe.
As others have indicated, if you don't understand this, then you should contact
the person who got you "started" with compiling on the mainframe. They would
understand all of this.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:86f755fe-26fe-4e97...@d1g2000hsg.googlegroups.com...
Doug Miller
@d1g2000hsg.googlegroups.com>, ahsh...@gmail.com says...
>
> I got the file through FTP. I could not cut and paste it. maybe some
> special characters, I don't know.
> If you specify what peace of code is necessary to help, I will type it
> again if needed.
>
If you want help, you need to show us *exactly* what you're compiling.
The whole listing. You should be able to display this on a PC and copy
and paste (NOT RE-TYPE) into a post here. If you don't know how to do
this, have someone in your office show you how.
Hell, print the whole thing, scan the printout, and post JPEGs of the
scans on flickr.com if you have to. We CAN'T tell you what the problem
is until you show us what you're doing, and what happens.
amir
> In article <86f755fe-26fe-4e97-bb96-9fe535901036
>
> > I got the file through FTP. I could not cut and paste it. maybe some
> > special characters, I don't know.
> > If you specify what peace of code is necessary to help, I will type it
> > again if needed.
>
> You don't seem to understand.
>
> If you want help, you need to show us *exactly* what you're compiling.
> The whole listing. You should be able to display this on a PC and copy
> and paste (NOT RE-TYPE) into a post here. If you don't know how to do
> this, have someone in your office show you how.
>
> Hell, print the whole thing, scan the printout, and post JPEGs of the
> scans on flickr.com if you have to. We CAN'T tell you what the problem
> is until you show us what you're doing, and what happens.
Thanks for all.
I could not attach my file which I got by FTP in ASCII mode and
windows do not let me to copy-paste it.
Best,
Robert
Your government (Iran) blocked clipboard functions after someone used them to copy
anti-Islamic messages. They blocked YouTube for the same reason. They say, if it happens
again, they'll block all writes to memory.
Nothing changes in a read-only society. It is little known that the mainframe division of
IBM adopted such a policy in the 1980s. The problem it raised is what to do with
programmers. If nothing changes, there is no need for developers.
The problem was solved when they realized branched changes could not be committed to the
trunk of IBM version control. Each new relaease requires re-applying and re-testing
changes made since the trunk was created in 1982, even though nothing changed in the
current release. If this maintenance is overlooked, bugs fixed a decade ago will reappear.
Facetious? There are mainframe shops where this is practiced today.
Doug Miller
@e53g2000hsa.googlegroups.com>, ahsh...@gmail.com says...
Like I said -- if you don't know how to copy and paste, have someone in
your office show you. Or print the whole stupid thing, scan it, and post
the scanned images. If you want help, you MUST show us ALL of what
you're doing, and ALL of what happens.
amir
I can send the file to everyone through attachment.
But, I can not copy and paste it. Maybe some incompatibility between G!
Groups editor and Windows. I don't know.
Best,
Michael Mattias
> I can send the file to everyone through attachment.
> But, I can not copy and paste it. Maybe some incompatibility between G!
> Groups editor and Windows. I don't know.
This might not be a 'clipboard' problem per se...
If there is an embedded NUL (0x00) character in the contents, clipboard
copies will terminate the text at that null, while attaching would be
unaffected.
This will be dependent on the behavior of the specific editor in which you
open the file to do the select/copy and into what email client you do the
pasting, but it is something worth investigating.
MCM
Doug Miller
>"amir" <ahsh...@gmail.com> wrote in message news:37df9c12-26be-4735-8430->
>> I can send the file to everyone through attachment.
>> But, I can not copy and paste it. Maybe some incompatibility between G!
>> Groups editor and Windows. I don't know.
>
>This might not be a 'clipboard' problem per se...
>
>If there is an embedded NUL (0x00) character in the contents, clipboard
>copies will terminate the text at that null, while attaching would be
>unaffected.
It seems unlikely in the extreme that there's a null embedded in the compiler
output, unless there's one in the source file -- which may be the OP's
problem.
William M. Klein
> On May 10, 2:28 pm, Robert <n...@e.mail> wrote:
> I can send the file to everyone through attachment.
> But, I can not copy and paste it. Maybe some incompatibility between G!
> Groups editor and Windows. I don't know.
> Best,
As I said in private email (after finding out that he was using ISPF to edit the
file)
1) Change to HEX MODE and look at the non-visible characters (the listing tells
which line and column) and if they aren't X'40' - then change them.
2) More importantly, if this file was NOT uploaded from the PC and only worked
on via ISPF, there is a bigger problem - figuring out HOW the non-visible
characters got into the file in the first place.
P.S. I can't remember. What is the ISPF command to find "non[visible"
characters? It has a "p" and an "=" in it, as I recall, but I can't remember
the exact syntax (and don't use ISPF any more).
Clark F Morris
I think it is f p"=" but somehow the "=" seems wrong. Nulls on might
have caused the x"00" although the nulls should have been changed to
spaces on save.
amir
The file was filled with X'00' characters and Windows did not let me
to cut exactly.
Anyway, with your help, I replaced it by X'20' and now everything is
ok.
This is my listing file content.
1PP 5648-A25 IBM COBOL for OS/390 & VM
2.2.0 Date 05/06/2008 Time 11:24:29
Page 1
0Invocation parameters:
OBJECT,LIB,NOTEST,FLAG(I,I)
0Options in effect:
NOADATA
ADV
NOANALYZE
QUOTE
ARITH(COMPAT)
NOAWO
BUFSIZE(4096)
NOCMPR2
NOCOMPILE(S)
NOCURRENCY
DATA(31)
NODATEPROC
NODBCS
NODECK
NODIAGTRUNC
NODLL
NODUMP
NODYNAM
NOEXIT
NOEXPORTALL
NOFASTSRT
FLAG(I,I)
NOFLAGMIG
NOFLAGSTD
NOIDLGEN
INTDATE(ANSI)
LANGUAGE(EN)
LIB
LINECOUNT(60)
NOLIST
NOMAP
NONAME
NONUMBER
NUMPROC(NOPFD)
OBJECT
NOOFFSET
NOOPTIMIZE
OUTDD(SYSOUT)
PGMNAME(COMPAT)
NORENT
RMODE(AUTO)
SEQUENCE
SIZE(MAX)
SOURCE
SPACE(1)
NOSQL
NOSSRANGE
NOTERM
NOTEST
TRUNC(STD)
NOTYPECHK
NOVBREF
NOWORD
NOXREF
1PP 5648-A25 IBM COBOL for OS/390 & VM
2.2.0 Date 05/06/2008 Time 11:24:29
Page 2
0 YEARWINDOW(1900)
ZWB
1PP 5648-A25 IBM COBOL for OS/390 & VM
2.2.0 Date 05/06/2008 Time 11:24:29
Page 3
0LineID Message code Library phase message text
IGYLI0090-W 3 sequence errors were found in this program.
-Messages Total Informational Warning Error Severe
Terminating
0Printed: 1 1
1PP 5648-A25 IBM COBOL for OS/390 & VM 2.2.0
NWTEST01 Date 05/06/2008 Time 11:24:29 Page 4
LineID PL SL ----+-*A-1-B--+----2----+----3----+----4----
+----5----+----6----+----7-|--+----8 Map and Cross Reference
0 000001 identification
division.
==000001==> IGYDS0001-W A blank was missing before character " " in
column 32. A blank was
assumed.
==000001==> IGYDS0027-S Non-COBOL character(s) were found starting
with " " in column 32. The
characters were discarded.
000002** program-id.
nwtest01.
==000002==> IGYDS0001-W A blank was missing before character " " in
column 29. A blank was
assumed.
==000002==> IGYDS0027-S Non-COBOL character(s) were found starting
with " " in column 29. The
characters were discarded.
000003** environment
division.
==000003==> IGYDS0001-W A blank was missing before character " " in
column 29. A blank was
assumed.
==000003==> IGYDS0027-S Non-COBOL character(s) were found starting
with " " in column 29. The
characters were discarded.
000004**
data
division.
==000004==> IGYDS0001-W A blank was missing before character " " in
column 22. A blank was
assumed.
==000004==> IGYDS0027-S Non-COBOL character(s) were found starting
with " " in column 22. The
characters were discarded.
000005 procedure
division.
==000005==> IGYPS0001-W A blank was missing before character " " in
column 27. A blank was
assumed.
==000005==> IGYPS0027-S Non-COBOL character(s) were found starting
with " " in column 27. The
characters were discarded.
000006 1 end program
nwtest01.on.
==000006==> IGYSC0001-W A blank was missing before character "o" in
column 29. A blank was
assumed.
==000006==> IGYSC0142-E Expected end of source file or the beginning
of a separately compiled
program, but found "ON". Skipped to end of
source file or the beginning
of the next program.
==000006==> IGYSC0001-W A blank was missing before character " " in
column 32. A blank was
assumed.
==000006==> IGYSC0027-S Non-COBOL character(s) were found starting
with " " in column 32. The
characters were discarded.
1PP 5648-A25 IBM COBOL for OS/390 & VM 2.2.0
NWTEST01 Date 05/06/2008 Time 11:24:29 Page 5
0LineID Message code Message text
IGYSC0185-I Messages were issued during library phase
processing. Refer to the beginning of the listing.
1 IGYDS0001-W A blank was missing before character " " in
column 32. A blank was assumed.
Same message on line: 6
1 IGYDS0027-S Non-COBOL character(s) were found starting with
" " in column 32. The characters were discarded.
Same message on line: 6
2 IGYDS0001-W A blank was missing before character " " in
column 29. A blank was assumed.
Same message on line: 3
2 IGYDS0027-S Non-COBOL character(s) were found starting with
" " in column 29. The characters were discarded.
Same message on line: 3
4 IGYDS0001-W A blank was missing before character " " in
column 22. A blank was assumed.
4 IGYDS0027-S Non-COBOL character(s) were found starting with
" " in column 22. The characters were discarded.
5 IGYPS0001-W A blank was missing before character " " in
column 27. A blank was assumed.
5 IGYPS0027-S Non-COBOL character(s) were found starting with
" " in column 27. The characters were discarded.
6 IGYSC0001-W A blank was missing before character "o" in
column 29. A blank was assumed.
6 IGYSC0142-E Expected end of source file or the beginning of
a separately compiled program, but found "ON". Skipped to end
of source file or the beginning of the next
program.
-Messages Total Informational Warning Error Severe
Terminating
0Printed: 15 1 7 1 6
-* Statistics for COBOL program NWTEST01:
* Source records = 6
* Data Division statements = 0
* Procedure Division statements = 0
0End of compilation 1, program NWTEST01, highest severity 12.
0Return code 12
Thanks to all again for your help,
AS
William M. Klein
32 of the line with "identification division" on it. It is a "non-COBOL"
character (possibly a x"00" or x"0A" or something similar. Change it to x'40'
(EBCDIC space) and then do the same thing to all characters that aren't valid
COBOL characters as seen in HEX MODE edit of your source code.
You need to believe your listings. When they tell you that you have bad data in
a specific column in a specific line, then that is what has happened.
Now, HOW you got the bad data in your source file in the first place is another
question. Have you had any training on how to use the ISPF editor to create
text files (source code or otherwise)? If not, you should ask whoever is
working with you to help you get such training.
P.S. See:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ISPZEM61/1.3.4.1.3
for how to do an ISPF search (in your source file) for non-visible characters.
(You probably should review that entire manual if you haven't been trained on
using ISPF for editing)
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:6aa67b68-28c7-4b7f...@56g2000hsm.googlegroups.com...
Binyamin Dissen
:>Thanks to all friends,
:>The file was filled with X'00' characters and Windows did not let me
:>to cut exactly.
:>Anyway, with your help, I replaced it by X'20' and now everything is
:>ok.
:>This is my listing file content.
Looks like you had major problems uploading the source to MVS. Many garbage
characters.
I would suggest going into ISPF edit and doing a
change p'.' ' ' all
and trying again.
Also, why do you have .on on your end program statement?
--
Binyamin Dissen <bdi...@dissensoftware.com>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.
I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.
SkippyPB
It is f p'.'.
I upload lots of stuff from the PC to the mainframe and I always just
automatically edit the uploaded member with C x'20' x'40' all. That's
the only ASCII character that is usually in a text document.
Regards,
////
(o o)
-oOO--(_)--OOo-
"Where lipstick is concerned, the important thing is not color,
but to accept God's final word on where your lips end."
-- Jerry Seinfeld
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Remove nospam to email me.
Steve
Clark F Morris
<wmk...@nospam.netcom.com> wrote:
>Go into HEX mode in ISPF edit of your SOURCE code and look at what is in column
>32 of the line with "identification division" on it. It is a "non-COBOL"
>character (possibly a x"00" or x"0A" or something similar. Change it to x'40'
>(EBCDIC space) and then do the same thing to all characters that aren't valid
>COBOL characters as seen in HEX MODE edit of your source code.
All of a sudden the light dawns. There may be a problem copying out
of the emulator when NULLS ON is in effect. All fields in the screen
(sequence number in 1 - 6, rest of line 7 - 72, and comment 73 - 80
have all trailing spaces replaced with NULLS (x'00'). If this data is
transferred to a PC file through the emulator via whatever magic weird
things may happen. Since I have been away from a mainframe since the
end of 2006, I am not quite certain of the details but NULLS ON does
have interesting considerations.
amir
My problem with the COBOL compiler on the 360 was my primary problem
and I have not solved it yet.
Is there anyone can help me.
Best,
Howard Brazee
wrote:
>Dear friends,
How did you write the code? If you wrote it on your PC, how did you
get it to the mainframe? I'm wondering if your problem might be an
ASCII/EBCDIC confusion. If you're in TSO/SPF look at one of the
lines saying showing " " and say HEX ON, and see what is in that
space.
William M. Klein
told you to use on your source code? If not, why are you still asking?
P.S. I assume that "360" was a typo and that you aren't really using a
mainframe THAT old!!!
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:75b64575-70b8-4c8c...@b64g2000hsa.googlegroups.com...
amir
I wrote my code on the ISPF-editor exactly and transfered to PC using
FTP.
> P.S. I assume that "360" was a typo and that you aren't really using a
mainframe THAT old!!!
Our System is OS/390 installed on Parallel Enterprise Server 9672, as
I know.
> How did you write the code? If you wrote it on your PC, how did you
> get it to the mainframe? I'm wondering if your problem might be an
> ASCII/EBCDIC confusion. If you're in TSO/SPF look at one of the
> lines saying showing " " and say HEX ON, and see what is in that
> space.
000001 .... identification
division..............................................................................
44FFFFFF44444444401004448889A88888A899488A8A89940000000000000000000000000000000000000000000000000000000000000000000000000000044444444444444444444444444444444444
000000010000000000F0000094553969313965049592965B0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
The problem started exactly at 9th charachter after 000001.
It will be in the "A899488A", if we assume each two hex numbers as one
character.
What is your idea?
Attention! The non-usual characters resulted from the COBOL
compilation process on the mainframe and I did not created it.
Thanks,
SkippyPB
wrote:
>Dear friends,
If you wrote the code in the ISPF editor, why not compile it from
there on the mainframe? Why are you FTPing to the PC? Waste of time
and you obviously don't know what you are doing going between the two
platforms.
Write the COBOL on the mainframe in the ISPF editor. Compile that
source on the mainframe. Correct typos. Repeat until desired results
are achieved. K.I.S.S.
amir
> there on the mainframe? Why are you FTPing to the PC? Waste of time
> and you obviously don't know what you are doing going between the two
> platforms.
I wrote the code there and compiled by mainframe.
and used FTP to get data into PC and send to the internet.
I am using MF COBOL until I could start running code on the mainframe.
Thanks,
William M. Klein
"Attention! The non-usual characters resulted from the COBOL >compilation
process on the mainframe and I did not created it."
Compilation NEVER changes the source code. Somewhere you did something to
introduce the non-visible characters into the ISPF source code.
The compilation process *might* introduce non-visible characters into the
LISTING - but not into the source code.
Any way, have you fixed the source code yet and does it compile?
--
Bill Klein
wmklein <at> ix.netcom.com
"SkippyPB" <swie...@nospam.neo.rr.com> wrote in message
news:e93m24lhte8n5pf8r...@4ax.com...
amir
The source code did not changed.
It compiled and I had the non-visual characters in my listing as I
checked it again.
I used a command "unix2dos" in Linux Bash, before.
this may solve my problem. But I did not found it in this environment.
William M. Klein
environment?
HINT:
Lots of your source code that works with PC compilers will NOT work with
mainframe ones - because you are using the "wrong" COPY techniques.
REAL HINT:
Go thru a COBOL course before trying to use COBOL.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:06e441f4-7e11-4d17...@w7g2000hsa.googlegroups.com...
Doug Miller
b3cd1e...@m36g2000hse.googlegroups.com>, ahsh...@gmail.com says...
> 000001 .... identification division................(etc)
> 44FFFFFF44444444401004448889A88888A899488A8A8994000000000000000(etc)
> 000000010000000000F0000094553969313965049592965B000000000000000(etc)
> The problem started exactly at 9th charachter after 000001.
> It will be in the "A899488A", if we assume each two hex numbers as one
> character.
You don't even *begin* to understand what you're looking at.
The two hex digits making up each character are read *vertically*,
appearing directly underneath the text they correspond to. The problem
actually starts at the 10th character after "000001", not the 9th, and
"A899488A" is not what you think it is:
A899488A
39650495
is read as
A3 89 96 95 40 84 89 A5 = "tion div"
Following the "000001", you have:
444444444
000000000
read as 40 40 40 40 40 40 40 40 40 = " "
followed by
0100
0F00
read as 00 1F 00 00 = NUL, IUS, NUL, NUL
then three more spaces, then "identification division.", followed by a
whole lot more nulls.
amir
> In article <19604818-f965-4e30-899a-
> b3cd1e7ac...@m36g2000hse.googlegroups.com>, ahsha...@gmail.com says...
I got it. As I checked it, My problem is after 9 character from 000001
and is:
0100
0F00
So My problem in Windows Cut/Paste cause was these characters.
Thanks,
Doug Miller
@k37g2000hsf.googlegroups.com>, ahsh...@gmail.com says...
That's NOT the ONLY problem; as noted just a few lines above, you ALSO
have a whole lot of nulls following the period after "division".
amir
> In article <0ab03ab8-c3e8-40cb-8cb7-c81ffd642b98
> @k37g2000hsf.googlegroups.com>, ahsha...@gmail.com says...
Of course, I have too much null characters in my listing.
William M. Klein
What can we do to convince you that your problem is NOT the bad characters in
the LISTING - but in the source program. The bad characters in the listing may
make "cut-and-paste" a problem.
HOWEVER,
Your problem is the bad characters in your source program on the Mainframe
(not the PC). We told you what ISPF command to use to see them. We told you
what commands to use to FIX them.
Please STOP posting about bad characters in your listing; we just DON"T CARE
!!!!
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:f45f4240-95a0-4adb...@k37g2000hsf.googlegroups.com...
Doug Miller
f5e359...@k37g2000hsf.googlegroups.com>, ahsh...@gmail.com says...
PROGRAM. Get rid of them.
amir
> In article <f45f4240-95a0-4adb-b172-
> f5e3595f0...@k37g2000hsf.googlegroups.com>, ahsha...@gmail.com says...> On May 16, 3:04 am, Doug Miller <spamb...@milmac.com> wrote:
>
> > > That's NOT the ONLY problem; as noted just a few lines above, you ALSO
> > > have a whole lot of nulls following the period after "division".
>
> > Of course, I have too much null characters in my listing.
>
> No, you idiot, your problem is you have null characters in your SOURCE
> PROGRAM. Get rid of them.
000001 identification
division.
4448889A88888A899488A8A8994444444444444444444444444444444444444444444444
00094553969313965049592965B000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000002 program-id.
nwtest01.
4449998989688449AA8AAFF4444444444444444444444444444444444444444444444444
0007967914094B056352301B000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000003 environment
division.
44489A8999989A488A8A8994444444444444444444444444444444444444444444444444
00055599654553049592965B000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000004 data
division.
44488A8488A8A89944444444444444444444444444444444444444444444444444444444
0004131049592965B0000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000005 procedure
division.
444999888A98488A8A899444444444444444444444444444444444444444444444444444
000796354495049592965B00000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000006 display "hello" upon
console
444444488A998A478899974A9994899A9984444444444444444444444444444444444444
000000049273180F85336F04765036526350000000000000000000000000000000000000
------------------------------------------------------------------------------
000007 stop
run
4444444AA9949A9444444444444444444444444444444444444444444444444444444444
000000023670945000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000008 .
444444444444444444444444444444444444444444444444444444444444444444444444
0000000B0000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
This is my source code.
Exactly, I could not find null and bad characters in my source.
Would you please help me?
Binyamin Dissen
:>On May 17, 9:04 pm, Doug Miller <spamb...@milmac.com> wrote:
:>> In article <f45f4240-95a0-4adb-b172-
:>> f5e3595f0...@k37g2000hsf.googlegroups.com>, ahsha...@gmail.com says...> On May 16, 3:04 am, Doug Miller <spamb...@milmac.com> wrote:
:>> > > That's NOT the ONLY problem; as noted just a few lines above, you ALSO
:>> > > have a whole lot of nulls following the period after "division".
:>> > Of course, I have too much null characters in my listing.
:>> No, you idiot, your problem is you have null characters in your SOURCE
:>> PROGRAM. Get rid of them.
:>000001 identification
:>division.
:>4448889A88888A899488A8A8994444444444444444444444444444444444444444444444
:>00094553969313965049592965B000000000000000000000000000000000000000000000
[ Snipped ]
:>This is my source code.
Which is different than your previous source.
:>Exactly, I could not find null and bad characters in my source.
This one doesn't appear to have them. Why not attempt a compilation?
:>Would you please help me?
Nobody could be that clueless.
Are you trying for the "longest usenet thread" championship?
amir
wrote:
> On Sun, 18 May 2008 01:00:00 -0700 (PDT) amir <ahsha...@gmail.com> wrote:
>
> :>On May 17, 9:04 pm, Doug Miller <spamb...@milmac.com> wrote:
> :>> In article <f45f4240-95a0-4adb-b172-
> :>> f5e3595f0...@k37g2000hsf.googlegroups.com>, ahsha...@gmail.com says...> On May 16, 3:04 am, Doug Miller <spamb...@milmac.com> wrote:
>
> :>> > > That's NOT the ONLY problem; as noted just a few lines above, you ALSO
> :>> > > have a whole lot of nulls following the period after "division".
>
> :>> > Of course, I have too much null characters in my listing.
>
> :>> No, you idiot, your problem is you have null characters in your SOURCE
> :>> PROGRAM. Get rid of them.
>
> :>000001 identification
> :>division.
>
> :>4448889A88888A899488A8A8994444444444444444444444444444444444444444444444
> :>00094553969313965049592965B000000000000000000000000000000000000000000000
>
> [ Snipped ]
>
> :>This is my source code.
>
> Which is different than your previous source.
>
> :>Exactly, I could not find null and bad characters in my source.
>
> This one doesn't appear to have them. Why not attempt a compilation?
>
> :>Would you please help me?
>
> Nobody could be that clueless.
>
> Are you trying for the "longest usenet thread" championship?
>
> --
>
> Director, Dissen Software, Bar & Grill - Israel
>
> Should you use the mailblocks package and expect a response from me,
> you should preauthorize the dissensoftware.com domain.
>
> I very rarely bother responding to challenge/response systems,
> especially those from irresponsible companies.
Some friends in this list, told me about bad characters.
I deleted first file and rewrite it again and again.
changed different parts. But, I did not get answers better than
before.
Anyway, I wrote what exactly is and I do not want to waste my or other
friends time.
Thanks to everyone for help as he/she could.
William M. Klein
the mainframe with ISPF) a file that did NOT have any bad characters in the
SOURCE program and then tried to compile it (on the mainframe) - you have never
shown us any compile errors of a file without bad characters.
You also haven't shown that when you compiled on the PC (with Micro Focus) that
use used the mainframe directive
dialect(entcobol)
It is the fact that you seem to ignore (or not understand) the answers you get
that causes frustrations with your posts.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:91159315-b82d-4898...@l42g2000hsc.googlegroups.com...
Doug Miller
27g2000hsf.googlegroups.com>, ahsh...@gmail.com says...
[big snip]
> This is my source code.
This is NOT the same source code that you posted before. It's a
different program.
> Exactly, I could not find null and bad characters in my source.
That's because there AREN'T any in THIS program. There were in the OTHER
program you posted.
> Would you please help me?
Help you with what? Have you tried compiling THIS one?
amir
> In article <a242c670-79a9-4273-a475-351bfd7bb490@
> [big snip]
>
> > This is my source code.
>
> This is NOT the same source code that you posted before. It's a
> different program.
>
> > Exactly, I could not find null and bad characters in my source.
>
> That's because there AREN'T any in THIS program. There were in the OTHER
> program you posted.
>
> > Would you please help me?
>
> Help you with what? Have you tried compiling THIS one?
I tried these sources all.
I did not got result but errors.
One of my friends sent me a source code to help.
It works.
I compared both.
I just find the column number differences.
THIS SOURCE WORKED AND COMPILED RIGHT.
---------------------------------------
IDENTIFICATION DIVISION.
PROGRAM-ID. DI01.
ENVIRONMENT DIVISION.
DATA
DIVISION. EZA00270
WORKING-STORAGE SECTION.
******************************************************************
01 TEST-DG.
03 NAME1 PIC X(20) VALUE 'TEST'.
03 NO1 PIC 9(4) VALUE 4444.
******************************************************************EZA01700
PROCEDURE
DIVISION. EZA01720
DISPLAY "NAME:".
ACCEPT NAME1 OF TEST-DG.
DISPLAY "NO:".
ACCEPT NO1 OF TEST-DG.
DISPLAY "--------------------------------------------"
DISPLAY NAME1.
DISPLAY NO1.
STOP RUN.
-------------------------
AND THIS IS MY BAD SOURCE
-------------------------
identification division.
program-id. nwtest01.
environment division.
data division.
procedure division.
display "hello" upon console
stop run
.
-------------------------
As you see the difference is just in column starting.
Therefore, Error messages did not show this problem.
I think so.
Anyway, thanks to all my friends for your help.
Best,
docd...@panix.com
amir <ahsh...@gmail.com> wrote:
[snip]
>THIS SOURCE WORKED AND COMPILED RIGHT.
[snip]
>AND THIS IS MY BAD SOURCE
Unless you are working in the curious world of 'options' it is frequently
the case that trying to sell something you do not have - in this case
knowledge of COBOL - is a kind of theft.
DD
William M. Klein
first replies you go talked about paying attention to starting your coed in
column 8 (the A-margin) or column 12 (the B-margin) and the fact that the PC
compilers don't require this.
We have asked for you to show us source code and error messages that MATCH.
I'll bet the message (on the mainframe) for when you started in columns before 8
were pretty clear. Furthermore, if you were using ISPF, I'll bet you didn't
call your source code something ending in ".COBOL" and/or that you didn't use
NUM COBOL.
Also, I remember specifically sending you the online reference for the column
information. See:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/IGY3LR40/1.6
Again, I'll bet your code with source being before column 8 didn't work with
Micro Focus if you used
DIALECT(ENTCOBOL)
as I have suggested multiple times.
***
The real issue is (or at least seems to be) that you have been given a task that
you aren't qualified to do - and without adequate support within your
organization to do it.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:03588188-081d-42ff...@f36g2000hsa.googlegroups.com...
Doug Miller
@f36g2000hsa.googlegroups.com>, ahsh...@gmail.com says...
[big snip]
> As you see the difference is just in column starting.
Exactly as you were told by several people more than a week ago.
> Therefore, Error messages did not show this problem.
Yes, they did. As you were told.
But you weren't listening.
amir
I did it according to References I have.
According to these references, I have to start at column 7 for
Indicator and 8 for Area-A and 12 for Area-B.
I did it according to my references.
Therefore, it did not worked and there were not any Error message show
me.
I showed you one of my exact error messages.
What you see in the right source code,
Areas is according to:
11->Indicator
12->Area-A
16->Area-B
If you subtract 3 from each number, you get the standard numbers.
ISPF-Editor showed these numbers, may some bad setting in the editor
and viewer configuration or an Standard in ISPF-Editor, I did not know
about it.
Best,
amir
> You also haven't shown that when you compiled on the PC (with Micro Focus) that
> use used the mainframe directive
> dialect(entcobol)
1-----7A---B--------------
$set dialect(entcobol)
$SET CURRENCY-SIGN"157"
And I got:
1$ set dialect(entcobol)
* 53-S*********************
** Invalid directive, or directive not allowed here
* Checking terminated
When I commented the first line, the program compiled successfully.
Remember that my compiler is:
Microsoft (R) COBOL Optimizing Compiler Version 5.0
COBOL software by Micro Focus
Copyright (C) Microsoft Corporation 1984,1993. All rights reserved.
Copyright (C) Micro Focus Ltd. 1984,1993. All rights reserved.
In this situation, is there any other directive or command to force me
to write my code as Ent.Cobol?
Best,
William M. Klein
Micro Focus) COMPILER, then what you need to do is compile with (DO NOT USE SET
statements, but use directives with the compiler):
NOFM,COBOL370, FLAG(COBOL370),FLAGAS(S)
P.S. What makes you think that using a PC compiler from 15 years ago will help
you find out about COBOL capabilities today on an IBM mainframe.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:dc33e239-aa64-4a24...@d1g2000hsg.googlegroups.com...
William M. Klein
the compiler rejects code in columns 8 and 12.
You say,
" Therefore, it did not worked and there were not any Error message show me."
what makes you think that it didn't work if there were no error messages. Are
you still compiling with FLAG(I,I)?
You CLAIM,
"> What you see in the right source code,
Areas is according to:
11->Indicator
12->Area-A
16->Area-B
"
Again, you have NOT shown us the exact source code and a listing to match it.
I'll bet that if you seriously look at the mainframe listing you will see that
those are NOT the columns used for a successful compile. If you just posted the
portion of the successful compiler listing that starts with the "header" line
showing columns of the source code, I can almost guarantee that what you are
claiming is NOT what you are actually compiling.
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:aa482c62-3b53-4905...@a70g2000hsh.googlegroups.com...
amir
wrote:
> You have NEVER posted a copy of source code WITH MATCHING error messages - where
> the compiler rejects code in columns 8 and 12.
>
> You say,
>
> " Therefore, it did not worked and there were not any Error message show me."
>
In the message above I told about there is not any error message which
shows me wrong column usage. Also you can see my listing in:
http://groups.google.com/group/comp.lang.cobol/msg/d8125cf35197cefa
In this message, you can see that columns matched and there were not
any problem in columns.
> You CLAIM,
>
> "> What you see in the right source code,
> Areas is according to:
> 11->Indicator
> 12->Area-A
> 16->Area-B
> "
You can see the source code listing as:
---------------------------------------------------------
1PP 5648-A25 IBM COBOL for OS/390 & VM
2.2.0 Date 05/18/2008 Time 18:48:54
Page 1
0Invocation parameters:
OBJECT,LIB,NOTEST,FLAG(I,I)
0Options in effect:
NOADATA
ADV
NOANALYZE
QUOTE
ARITH(COMPAT)
NOAWO
BUFSIZE(4096)
NOCMPR2
NOCOMPILE(S)
NOCURRENCY
DATA(31)
NODATEPROC
NODBCS
NODECK
NODIAGTRUNC
NODLL
NODUMP
NODYNAM
NOEXIT
NOEXPORTALL
NOFASTSRT
FLAG(I,I)
NOFLAGMIG
NOFLAGSTD
NOIDLGEN
INTDATE(ANSI)
LANGUAGE(EN)
LIB
LINECOUNT(60)
NOLIST
NOMAP
NONAME
NONUMBER
NUMPROC(NOPFD)
OBJECT
NOOFFSET
NOOPTIMIZE
OUTDD(SYSOUT)
PGMNAME(COMPAT)
NORENT
RMODE(AUTO)
SEQUENCE
SIZE(MAX)
SOURCE
SPACE(1)
NOSQL
NOSSRANGE
NOTERM
NOTEST
TRUNC(STD)
NOTYPECHK
NOVBREF
NOWORD
NOXREF
1PP 5648-A25 IBM COBOL for OS/390 & VM
2.2.0 Date 05/18/2008 Time 18:48:54
Page 2
0 YEARWINDOW(1900)
ZWB
1PP 5648-A25 IBM COBOL for OS/390 & VM 2.2.0
DI01 Date 05/18/2008 Time 18:48:54 Page 3
LineID PL SL ----+-*A-1-B--+----2----+----3----+----4----
+----5----+----6----+----7-|--+----8 Map and Cross Reference
0 000001 IDENTIFICATION DIVISION.
000002 PROGRAM-ID. DI01.
000003 ENVIRONMENT DIVISION.
000004 DATA
DIVISION. EZA00270
000005 WORKING-STORAGE SECTION.
000006
******************************************************************
000007 01 TEST-DG.
000008 03 NAME1 PIC X(20) VALUE
'TEST'.
000009 03 NO1 PIC 9(4) VALUE
4444.
000010
******************************************************************EZA01700
000011 PROCEDURE
DIVISION. EZA01720
000012 DISPLAY "NAME:"
000013 ACCEPT NAME1 OF TEST-DG
000014 DISPLAY "NO:"
000015 ACCEPT NO1 OF TEST-DG
000016 DISPLAY
"--------------------------------------------"
000017 DISPLAY NAME1
000018 DISPLAY NO1
000019 STOP RUN
000020 .
-* Statistics for COBOL program DI01:
* Source records = 20
* Data Division statements = 3
* Procedure Division statements = 8
0End of compilation 1, program DI01, no statements flagged.
0Return code 0
---------------------------------------------------------
This code compiled without any error as you see above.
Also according to last message I told you, can see the columns as
everything is ok.
---------------------------------------------------------
http://groups.google.com/group/comp.lang.cobol/msg/d8125cf35197cefa
1PP 5648-A25 IBM COBOL for OS/390 & VM 2.2.0
NWTEST01 Date 05/06/2008 Time 11:24:29 Page 4
LineID PL SL ----+-*A-1-B--+----2----+----3----+----4----
+----5----+----6----+----7-|--+----8 Map and Cross Reference
0 000001 identification
---------------------------------------------------------
> Again, you have NOT shown us the exact source code and a listing to match it.
> I'll bet that if you seriously look at the mainframe listing you will see that
> those are NOT the columns used for a successful compile. If you just posted the
> portion of the successful compiler listing that starts with the "header" line
> showing columns of the source code, I can almost guarantee that what you are
> claiming is NOT what you are actually compiling.
I don't know how did you get this result.
> > What you see in the right source code,
> > Areas is according to:
> > 11->Indicator
> > 12->Area-A
> > 16->Area-B
> > If you subtract 3 from each number, you get the standard numbers.
> > ISPF-Editor showed these numbers, may some bad setting in the editor
> > and viewer configuration or an Standard in ISPF-Editor, I did not know
> > about it.
I find my problem. Exact columns are:
15->Indicator
16->Area-A
20->Area-B
The ISPF consumed 6 characters for numbering lines and one space after
it and if you subtract 7 from this numbers you get the standard
numbers.
Anyway, I am wondering about the compiler errors, did not mean this to
me.
Thanks,
William M. Klein
The listing you can see my listing in:
http://groups.google.com/group/comp.lang.cobol/msg/d8125cf35197cefa
has TONS of messages - all of them showing that the source code that you were
compiling had invalid characters, for example, it explicitly states,
2 IGYDS0027-S Non-COBOL character(s) were found starting with " " in column
29. The characters were discarded.
You need to fix THOSE problems before you would see problems with columns.
So what you need to do is compile a mainframe source file with no bad
characters. See if you do get error messages (especially about columns) and then
tell us the results. If you get even ONE IGY message, you need to fix it before
you tell us that you don't have any messages.
Again, you fix mainframe compile problems by fixing the mainframe source code
(not the listing).
1) It should have no invalid characters (found by using the ISPF Find P"."
command
2) The source code should be in the correct columns
3) There should be no "bad data" at the end of lines like that source program
had in
end program nwtest01.on.
***
Part 2:
As far as the "good source" code listed below, I think you are
misunderstanding what you are seeing in both the listing and the source code.
First, as far as the listing below, it is using propostional font, so it is hard
to see what columns the listing shows things in. The "line unumbers" in that
listing are under the heading:
LineID PL SL
in the line showing you which column things are under. These are all explained
at:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/igy3pg40/2.6.4.2
It is also worth noting that you have posted below has "print control
characters" in it. For example, the first "0" in
0 000001 IDENTIFICATION DIVISION
You need to understand what you are looking at and how this impacts APPARENT
columns.
Now, if you go into ISPF edit of the GOOD source code and use the ISPF "COLS"
line command. See:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ispzem61/3.1.11
It will show you exactly what column the "I" in "IDENTIFICATION DIVISION" is in.
It can be anything between 8 and 11. (The A-margin).
It will show you what column the "D" in "DISPLAY "NAME:"" is. (It can be
antthing from 12 on - before 72, the B-margin).
It will show you what column the FIRST "*" is in in
000006 ******************************************************************
It will turn out to be EXACTLY column 7 (the indicator column).
This will show you (once again) that you need to understand both how to use ISPF
and what an IBM mainframe COBOL compiler listing is telling you.
****
Again, you NEED training to attempt to do what you are trying to do - or you
need someone that you can go to for these BASIC issues for trying to accomplish
what you are trying to do.
Finally, just like you are using a 15 year old compiler on the PC, you are also
using an OLD and out-of-service compiler on the IBM mainframe.
5648-A25 IBM COBOL for OS/390 & VM
hasn't been supported by IBM for several years now (unless you are running under
VM istead of z/OS - and in that case you have lots of other problems)
--
Bill Klein
wmklein <at> ix.netcom.com
"amir" <ahsh...@gmail.com> wrote in message
news:9390d5a9-abae-4ed1...@m44g2000hsc.googlegroups.com...