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
 

 

QTP-PCOMM Issue in SetText Method

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
usharaniA

New User


Joined: 22 Jan 2008
Posts: 85
Location: India

PostPosted: Tue Mar 06, 2012 12:23 pm    Post subject: QTP-PCOMM Issue in SetText Method
Reply with quote

Hi,
Am automating the Mainframe Screens(PCOMM emulator) through QTP.

am sending the text into the screen, using the

Set gobjautECLPS = CreateObject("PCOMM.autECLPS")
Set objMsgFileText = gobjautECLPS.autECLFieldList.FindFieldByRowCol(Row,Column)
objMsgFileText .SetText "S"

the QTP script runs fine in most of the machines , but fails in some machines(Not setting the value in the Screens).

Kindly let me know the reason for the fail or if any alternate command to set the text in Screen.

Regards,
Usha
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10232
Location: italy

PostPosted: Tue Mar 06, 2012 12:49 pm    Post subject: Reply to: QTP-PCOMM Issue in SetText Method
Reply with quote

Quote:
Kindly let me know the reason for the fail or if any alternate command to set the text in Screen.


such questions do not deserve any kind reply...
we do not belong to your organization, we do not have access to Your facilities, so we are not in a position to do any problem determination

furthermore You just told ... it does not work,
so the only kind/sarcastic reply You deserve is...
How bad, i sincerely hope that You will be able to fix it soon.

if You want good/useful answers learn to post <good> questions !

Quote:
the QTP script runs fine in most of the machines , but fails in some machines(Not setting the value in the Screens).


UYu have access to those machines, find out the differences in the setup
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2431
Location: Netherlands, Amstelveen

PostPosted: Tue Mar 06, 2012 1:04 pm    Post subject:
Reply with quote

And beside Enrico's statements, this a not a windows forum.
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Tue Mar 06, 2012 9:56 pm    Post subject:
Reply with quote

Since you're asking about a mainframe emulator...

Things I have run into using PCOMM/QTP:

- You need to make sure you isolate the differences between sessions that work and ones that don't. Usually, different "machines" have different userids. In your case, the working users might have access to that field, while the non-working users do not.

- You need to check all of the links in the chain. When using QTP for mainframe scripting, there are probably more licenses involved than you realize. You need to make certain that non-working machines are working for other things using QTP. (ie did the script work up until this point?)

- PCOMM has it's own profile settings. You can send the same commands to the same screens and get different results based on keyboard layout defined on that one session. Check to make sure all of the PCOMM settings are the same on all machines.

- PCOMM has different versions. Make sure all of yours are the same.

- The connection properties of PCOMM can make a difference. If some machines are on a connection that does screen compression, the interface API may treat them differently. Check to make sure the network settings are the same on all machines.

- Windows settings can make a difference. Something as simple as the repeat speed can change how a QTP script works, especially for a SendText command. You can also get torpedoed by a left/right hand mouse change.

Bottom line...isolate isolate isolate. You have to assume NOTHING when you are debugging it.
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 -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Receive a file using PCOMM macro Harald.v.K IBM Tools 0 Thu Mar 23, 2017 6:50 pm
No new posts Execessive parameter issue Sumeendar JCL & VSAM 5 Mon Dec 19, 2016 4:35 pm
No new posts DFHRESPONSE returns issue divated CICS 3 Wed Nov 02, 2016 6:32 pm
No new posts Can sending 5 MB data between cobol p... Kevin Vaz CICS 12 Tue Oct 18, 2016 4:50 pm
No new posts PCOMM macro to call another PCOMM macro boyti ko All Other Mainframe Topics 4 Tue Jul 12, 2016 4:30 pm


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