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
 

 

Cobol upgrade - source code missing for load modules.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools
View previous topic :: :: View next topic  
Author Message
gthmrj

New User


Joined: 22 Feb 2017
Posts: 8
Location: India

PostPosted: Wed Apr 26, 2017 6:04 pm    Post subject: Cobol upgrade - source code missing for load modules.
Reply with quote

Cobol upgradation is gonna happen soon. My application has many load modules which don't have source code. Need to recheck whether they are active/inactive. For now I have created a list of data for both COBOL load members as well as CICS load members which are using cobol codes. Initially the data was in text format. I pushed them into mainframes now as separate PDS datasets where they contain the names of load members.

Now my requirement is need to compare these datasets with JCL jobs library as well as Procedure library and cross-check whether they are active/inactive. Is there any shortcut/usage of any tool to perform this ?? Apart from the SRCHFOR option. Please let me know if there is a way !!!

Many thanks in advance !!
Goutham Raj.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8117
Location: East Dubuque, Illinois, USA

PostPosted: Wed Apr 26, 2017 7:21 pm    Post subject: Reply to: Cobol upgrade - source code missing for load modules.
Reply with quote

How do you know if they are active or not? This is NOT an easy thing to determine -- the system doesn't track this. Consider these scenarios:

- Main program executes in batch job. This is easy to identify but may require SMF data to know when / how often it executes.

- Subprogram executed from main program in batch job. This may be fairly easy to identify but not always -- a COBOL dynamic call, for example, may be in the form CALL WS-SUBPROGRAM where WS-SUBPROGRAM is a variable and the program name is put in the variable with a MOVE statement.

- Main program executes in CICS. The CICS statistics may help you identify them.

Your best bet would be to analyze the SMF type 30 records (and 110 for CICS) for a period of time -- at least going back to the last end of year (calendar AND fiscal if they are different). This won't necessarily identify all the subprograms but it should identify the main programs.
- Subprogram executed from a CICS main program. Again, this can present difficulties -- the subprogram can be called at least 4 different ways.
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 -> IBM Tools All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Could we identify the called modules ... elixir1986 COBOL Programming 5 Fri Jul 14, 2017 1:53 am
No new posts UNIT=AFF for Easytrieve code gandikk JCL & VSAM 7 Wed Jul 12, 2017 11:42 pm
No new posts XML Parse for COBOL 5.2 Bhanu Praveen COBOL Programming 1 Sat Jul 08, 2017 8:58 pm
No new posts Dynamic output file creation in cobol... smileheal COBOL Programming 7 Thu Jun 15, 2017 10:53 pm
No new posts Search utility(3.14) using JCl and Cobol RKS3 COBOL Programming 12 Sat Jun 10, 2017 10:24 pm


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