IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Is Enterprise PL/I v4.2 compatible with Assembler V2.1 ?


IBM Mainframe Forums -> PL/I & Assembler
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sundarkudos

New User


Joined: 16 Oct 2008
Posts: 39
Location: Chennai

PostPosted: Wed Aug 19, 2015 11:15 pm
Reply with quote

Hello All,

Currently, as part of PL/I language upgrade, we are migrating PL/I programs from PL/I V1.1 to Enterprise PL/I V4.2. Initial few phases went successfully (with simple PL/I programs) into production without any issues.

Now, we hit a problem while testing TELON-PLI-Assembler-DB2 combination programs. When TELON screen transaction is triggered, screen is abending with S0C1 and these programs also calling some assembler programs.

So, just wanted to make sure whether Enterprise PL/I v4.2 is compatible with Assembler V2.1.

I have checked various documentation and our forum threads but could not find any info on this. Need your help please.

Thanks,
Sundar.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Thu Aug 20, 2015 12:46 am
Reply with quote

Why would Enterprise PL/I 4.2 NOT be compatible with HLASM 2.1? Have you contacted the vendor of TELON for support? Is your assembler code compatible with LE and the run-time environment for Enterprise PL/I 4.2? It is difficult to say much here since we don't know how much research you have already done yourself.
Back to top
View user's profile Send private message
prino

Senior Member


Joined: 07 Feb 2009
Posts: 1306
Location: Vilnius, Lithuania

PostPosted: Thu Aug 20, 2015 12:55 am
Reply with quote

I guess that their might be a problem in that EPLI nowadays uses the OPTLINK linking convention. If the Telon assembler modules don't, you may have a problem, although declaring them as

Code:
dcl whatever entry options(assembler);


should cure that. The other thing that might cause a S0C1 is using an ARCH(n) that is too high for the underlying hardware.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> PL/I & Assembler

 


Similar Topics
Topic Forum Replies
No new posts Build dataset list with properties us... PL/I & Assembler 4
No new posts Finding Assembler programs PL/I & Assembler 5
No new posts How Can I Recall a Migrated Data Set ... PL/I & Assembler 3
No new posts step by step trace 4 ISPF dialog call... TSO/ISPF 17
No new posts Getting SOC4 while calling a Cobol DB... PL/I & Assembler 4
Search our Forums:

Back to Top