Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Easytrieve Version 6.4 upgrade query

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products
View previous topic :: :: View next topic  
Author Message
vina2010

New User


Joined: 06 Sep 2010
Posts: 19
Location: Bangalore

PostPosted: Tue Sep 24, 2013 8:32 pm    Post subject: Easytrieve Version 6.4 upgrade query
Reply with quote

Hi All

Our team has been recently working on a Easytrieve upgrade where we are currently facing an issue which is not seen under Version 6.3 of this product.

The issue is around a page number display which has been defined in the program as
Code:

PAGE-NO               S   3  N  VALUE 1


When we run the easytrieve program with Version 6.3 output comes out perfectly fine i.e. 001, 002 etc.

Whereas when we run with Version 6.4 output is just blank.

Please note that this has run without any program changes, only just a version change in the PROC from 6.3 to 6.4 is not working fine. Is there any new feature under Version 6.4 which could have caused this issue?

Can you please help?
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Sep 24, 2013 8:46 pm    Post subject:
Reply with quote

Hello,

Do keep in mind that Easytrieve 6.4 is Way Out of Date. . .

Is thie data being written to a report or to a file?
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7236

PostPosted: Tue Sep 24, 2013 8:58 pm    Post subject: Reply to: Easytrieve Version 6.4 upgrade query
Reply with quote

Is it the right-most field? Put it on a line on its own (temporary measure).

Compare the compile output from 6.3 to 6.4 paying attention to everything which is not your program code. Same for the syouts from both steps.
Back to top
View user's profile Send private message
vina2010

New User


Joined: 06 Sep 2010
Posts: 19
Location: Bangalore

PostPosted: Thu Sep 26, 2013 8:03 pm    Post subject: Reply to: Easytrieve Version 6.4 upgrade query
Reply with quote

Hi Bill Woodger

Thanks for you help. We are getting an output when we write this in next line. Is there any reason why this is happening? Something that we can fix to print page number on the same line.

dick scherrer

Thanks for the response. Reports are written both to report and file.

Thanks
Vina2010
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Thu Sep 26, 2013 9:05 pm    Post subject:
Reply with quote

Hello,

I seem to recall that Easytrieve handles report data in a different way than file data.

Possibly someone will remember this is more detail than i do.

You might also experiment with the data type. Unfortunately, i don't have the resources to test this just now . . .
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7236

PostPosted: Fri Sep 27, 2013 1:54 am    Post subject: Reply to: Easytrieve Version 6.4 upgrade query
Reply with quote

Without seeing your code or the output I suggested that you look at, I'd guess: your page-number is the last item on the line; your heading line with the page-number on is the longest line of the report; the default line size for the previous release you were using was overridden at installation; you are doing "something else" with the report. That means all of those things, although it is perhaps a simple LRECL problem, I'm not sure whether Easytrieve would complain if the LRECL was too short for all the output.

It is not possibile that a field in 6.4 does not behave as it did in 6.3. Your page-number is being truncated beacuse it is not appearing where it used to, and "something" is chopping it (doing the truncation).

The idea of putting the page-number on another line was simply to demonstate to you that the data field is working as it always has and always will so that you can start looking where the probliem is, not imagining the problem is something else.

Your comment about report being written to report and file might support the "something".

If you still can't get there, we need to see the PARM from the compile listing, the Easytrieve Plus output from the run (all the "stats" and stuf, anything which Easytrieve prints but is not REPORT outputf) and the REPORT statement from the program.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Fri Sep 27, 2013 2:56 am    Post subject:
Reply with quote

Hello,

Suggest you make sure all of the customization is the same. Something unintended may have been "improved" with the upgrade.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. Db2 SQL query to convert rows into co... subratarec DB2 5 Thu Nov 17, 2016 4:51 pm
No new posts Two Selects in a single select query Rohit Umarjikar DB2 1 Fri Nov 04, 2016 8:46 pm
No new posts COBOL Version 6.1 Virendra Shambharkar COBOL Programming 5 Tue Nov 01, 2016 11:24 am
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm
No new posts Single COPY CICS TS datasets and when... Kyle Carroll CICS 2 Tue Oct 11, 2016 9:47 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us