Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1032
  • Last Modified:

Access 2007, Attachmate, VBA - Performance Issues

Hi All,

I need your help on a project that I am currently working on. I am using Microsoft Access 2007 to write information to Mainframe Systems using Attachmate Extra X-treme 8.0 (SP1).

The code is running fine. However, I am facing an issue when it comes to certain files (where the number of records to be written to Mainframe are more). If there are 100 records, the code works fine and writes to Mainframe in about a minutes time (which is good enough considering that there are default wait times).

However, when the number of records are more the macro slows down gradually... A file with 700 records took 38 minutes, 19 minutes and 21 minutes when ran simultaneously.

A point to note is that the macro is run over a Citrix Session. I understand that there may be variations in the connectivity. However, this difference between the time taken to update 100 records vs 700 records is alarming.. (1 minute vs 20 minutes average)

I have tried running the code with and without disabling the Productivity Tools on Attachmate (Disabling Screen History, etc..) and still there is no change in performance....

Any help that you can provide me in resolving this issue will be greatly appreciated.

Best regards...
0
VenuChakkoth
Asked:
VenuChakkoth
  • 5
  • 3
  • 2
2 Solutions
 
Jeffrey CoachmanMIS LiasonCommented:
...Have you tried contacting "Attachmate" on this issue directly...?

It would seem that they would know more about this than most of us here...

It is not clear (to me at least) from their site what this product even does...?

In other words, can you first take a step back and explain hat this system's ultimate goal is...?

There are just to many unknowns here...
0
 
VenuChakkothAuthor Commented:
Hi Jeff,

Thank you for your time... Yes, I did contact Attachmate Support as well and the reply is awaited.

Attachmate is a Terminal Emulation Software that acts as a secure interface to connect with IBM Mainframe Systems.

http://www.attachmate.com/Products/Terminal+Emulation/Extra/xtreme/extra-x-treme.htm

Best regards...

0
 
Jeffrey CoachmanMIS LiasonCommented:
Oh, OK, then I misunderstood the question...
Since you posted this to the MS Access zone, I thought that Attachmate was a technology that managed "Attachment" fields in MS Access...


Jeff
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
giltjrCommented:
Is the slow down "per screen"  or is is the overall time?  

Per screen meaning screens 1-10 take 5 seconds each, screen 11 take 8 seconds, screen 12 take 10 seconds and so on?

Or does each screen take the same amount of time, except for the last screen?

How is the application on the mainframe written?

Say you can enter 10 records per screen.  Does it actually process the 10 records once you press "enter"?

Or does it collect/batch up, all records until you enter all 100 (or 700) and then process all of the records at once?

If it is the later, then it may not be your macro, but how the mainframe is processing the records.

I know we detect when a screen scrapper/script is being used and slow down those sessions as they do more work.  That way they don't lock out real people doing work.
0
 
VenuChakkothAuthor Commented:
Hi giltjr,

Sorry for the delay in responding.

The macro is designed to enter information in 5 different screens of attachmate. The macro updates first 4 screens in less than 10 seconds. On the 5th screen that the macro has to update record by record from a table. For eg: Enters information, hits Enter Key, and then Shift+F12 for updating that entry.

This process on the 5th screen works fine if the number of recrods to be entered are within 150 range... but if it goes beyond that number, the speed at which the records are being entered slows down...

Till 150 records, the macro enters 2 records per second and then gradually that slows down, though the process of updating the records is the same.

This is what I am trying to nail down... Please let me know in case of any questions....
0
 
giltjrCommented:
Where are the records for screen 5 read from?


You need to find out how the mainframe/3270 side is programmed.

If you have not, you may want to try and create some type of time stamped transaction log for screen five.
Log entries that show at least:

getting ready to read record
read finished
starting to enter data on 3270 screen
finished entering data on 3270 screen
pressed shift-f12
got response back from 3270 screen

Then see between which two events the slow up is occurring.  If it is occurring between "pressed shift+F12" and "got response back from 3270 screen", then the issue is in the 3270 application.
0
 
VenuChakkothAuthor Commented:
Hi giltjr,

thanks for the tip. I will try this and revert.

Best regards...
0
 
VenuChakkothAuthor Commented:
Hi giltjr,

Once again thank you for guiding me... I did create a log file with the timings. The slowdown happens at two instances for each record.

1) When the Enter Key is hit
2) When Shift + F12 is hit

The response time from attachmate varies between 2 to 7 seconds per instance per record.

Please let me know if you have any tips on how to tackle this?

Best regards...
0
 
giltjrCommented:
O.K., You really can't do anything.  That is how long it is taking for the mainframe application to respond.

You script is pressing enter or "Shift+F12" and waiting for the mainframe application to respond.

What you need to do is discuss what you are doing with the group that provides support for the mainframe application you are using.  It could be that they are queuing records and after so many their application starts having response time problems.  It could be that the time of day you are doing this is a busy time of day and that is normal.

On our applications we avg. about 1/2 second response time, but if our system gets real busy we could have 10-15 second response time.  For humans it is a long wait, but for a program/script that is trying to do the work of 100 humans, that is a LONG time.
0
 
VenuChakkothAuthor Commented:
Thanks a lot giltjr... I will try taking this up with our Mainframe Support team and see if they can provide any solutions.

Appreciate your time...

Best regards...
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now