CA Endevor

[askCA TRANSCRIPT] CA Endevor & CA Application Lifecycle Conductor – June 12, 2018 

Jun 13, 2018 10:47 AM

from Lenn Thompson (CA) to Everyone:

Good morning, everyone! Let's go ahead and get started.

from Lenn Thompson (CA) to Everyone:

Please remember to make sure you you have "Send to: Everyone" selected and let's use @NAME when responding!

from Lenn Thompson (CA) to Everyone:

@Phon: Thanks for joining us! Do you have any questions for the team?

from Lenn Thompson (CA) to Everyone:

@Rick: Good morning! Any questions for the team today?

from Lenn Thompson (CA) to Everyone:

@Pat Good morning! Do you have any questions for the team today?

from Lenn Thompson (CA) to Everyone:

@Everyone: Are there any questions today?

from Lenn Thompson (CA) to Everyone:

@Jim: Good morning and thanks for joining us. Do you have any questions for the team?

from Lenn Thompson (CA) to Everyone:

@Melva Good morning! How are you? Thanks for joining. Do you have any questions for the team today?

from Melva. Jackson to Everyone:

Yes, I have a question about Endevor and COBOL 6.  Is there anyone currently using a processor that compiles cobol

from June Abercrombie to Everyone:

@Melva, what version of Cobol are you coming from?

from Melva. Jackson to Everyone:

@June Currently on 4.2

from June Abercrombie to Everyone:

@Melva - Are your Cobol load libraries PDS or PDS/E?

from June Abercrombie to Everyone:

@Melva - Cobol 5 and 6 now require that the Cobol load libraries be PDS/E

from June Abercrombie to Everyone:

@Melva - If they are PDS then you will need to convert them to PDS/E using the Endevor BSTXCOPY utility to retain Footprints

from June Abercrombie to Everyone:

@Melva - we strongly recommend you convert the load libraries before doing the Cobol upgrade.

from Melva. Jackson to Everyone:

@June they are currently coded as library and not pdse

from June Abercrombie to Everyone:

@Melva - Library type of Library is PDS/E

from Melva. Jackson to Everyone:

@June okay when all of them are pdse

from June Abercrombie to Everyone:

@Melva - Good - if they are already PDS/E that is really good news.

from June Abercrombie to Everyone:

@Melva - Next is the processors.  There are several new DD statements required for the new Cobol compiler. That is the easy part.

from June Abercrombie to Everyone:

@Melva - the hard part is the Cobol options.  Some of the defaults have changed so it you were expecting some options to be set and were taking them as default, you need to review them and verify that the default has not changed.

from June Abercrombie to Everyone:

@Melva - what I have been recommending all users do is create a new Cobol compile and link job OUTSIDE of Endevor and test the compiles.  You can compare what options are getting set now in 4.2 with the options set in 6

from Richard Rozentals(CA) to Everyone:

@Melva have a look at this link: https://www.ibm.com/support/knowledgecenter/en/SS6SG3_6.2.0/com.ibm.cobol62.ent.doc/migrate/igymnew.html

from Melva. Jackson to Everyone:

@Richard I will go to the link.  Thanks for all the information this is going to be a big help to me.

from Lenn Thompson (CA) to Everyone:

@Melva Thanks for joining us!

from Melva. Jackson to Everyone:

@Lenn your welcome, enjoyed great information.

from Lenn Thompson (CA) to Everyone:

@Everyone We are almost at the top of the hour, so let's go ahead and wrap up. Are there any last questions?

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.