As a traveling consultant, my road took me to a massive Vegas Gaming operation, that runs it's shop with AS400/CICS. The legacy-4 rooms size- computer is protected more than fort Knox, and the level of trust that I earned is envious to many of the top leaders of the organization, and beyond.
Yet I see the Legacy system holding back many opportunities for success, compared to what UNIX can deliver. Fear of change + job security + paranoid security + Grey hair + Tough-guy-gambler image, keeps AS400(system i) /CICS running, with problems building up to a staggering level, that Unix can solve in a blink of an eye.
What line of thought you can say, that can be a good argument for Unix vs. AS400?
Anyone running CICS TX in a WPAR ?
In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue).
Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Dear All,
Can someone help to command or program to transfer the file from windows to Unix server and from one unix server to another Unix server in secure way.
I would request no samba client. (4 Replies)
Hi all,
I'm new to this forum.
I have a problem at work. I am a RPG programmer (AS400) but i have a new project to try something in QSHELL and i'm totally new to this.
I have to make a 'list' wich contains all our AS400 directories (+ on this level the size of the directory and how many... (0 Replies)
Hi all!
Is it possible to install AIX 6.1 over preinstalled Power Systems server with AS400?.
Now hardware platfoem is identical.
quote
IBM had two discrete Power Architecture based hardware lines since the early 1990's. Servers running processors based on the PowerPC-AS in the AS/400... (3 Replies)
Hi all,
We (AIX) currently mount to a ZFS on the Mainframe. When one of our local users wants to transfer a file to the Mainframe, they must first run binary MVSLOGIN passing user name and password. Our mainframe will be retired soon and business processes will be transferring to an... (2 Replies)
we have a as400 5rev4 and want to use a rhel server to use as a file server. We exported a drive on the rhel box and then mounted it on the as400. We can see the top directory in our mounted as400 directory but when we attempt access subdirectories we get a no matching object error.
When we open... (2 Replies)
Hi everyone,
I am in the need of some software which will allow me to access IBM AS400 from HP unix operating system.
I could download the software from IBM site for windows OS and it is working succesfully. I need to do the same on UNIX OS.
Could you please guide me to some site... (1 Reply)
CC_VEGAS(4) BSD Kernel Interfaces Manual CC_VEGAS(4)NAME
cc_vegas -- Vegas Congestion Control Algorithm
DESCRIPTION
The Vegas congestion control algorithm uses what the authors term the actual and expected transmission rates to determine whether there is
congestion along the network path i.e.
actual rate = (total data sent in a RTT) / RTT
expected rate = cwnd / RTTmin
diff = expected - actual
where RTT is the measured instantaneous round trip time and RTTmin is the smallest round trip time observed during the connection.
The algorithm aims to keep diff between two parameters alpha and beta, such that:
alpha < diff < beta
If diff > beta, congestion is inferred and cwnd is decremented by one packet (or the maximum TCP segment size). If diff < alpha, then cwnd
is incremented by one packet. Alpha and beta govern the amount of buffering along the path.
The implementation was done in a clean-room fashion, and is based on the paper referenced in the SEE ALSO section below.
IMPLEMENTATION NOTES
The time from the transmission of a marked packet until the receipt of an acknowledgement for that packet is measured once per RTT. This
implementation does not implement Brakmo's and Peterson's original duplicate ACK policy since clock ticks in today's machines are not as
coarse as they were (i.e. 500ms) when Vegas was originally designed. Note that modern TCP recovery processes such as fast retransmit and
SACK are enabled by default in the TCP stack.
MIB Variables
The algorithm exposes the following tunable variables in the net.inet.tcp.cc.vegas branch of the sysctl(3) MIB:
alpha Query or set the Vegas alpha parameter as a number of buffers on the path. When setting alpha, the value must satisfy: 0 < alpha <
beta. Default is 1.
beta Query or set the Vegas beta parameter as a number of buffers on the path. When setting beta, the value must satisfy: 0 < alpha <
beta. Default is 3.
SEE ALSO cc_chd(4), cc_cubic(4), cc_hd(4), cc_htcp(4), cc_newreno(4), h_ertt(4), mod_cc(4), tcp(4), khelp(9), mod_cc(9)
L. S. Brakmo and L. L. Peterson, "TCP Vegas: end to end congestion avoidance on a global internet", IEEE J. Sel. Areas Commun., 8, 13,
1465-1480, October 1995.
ACKNOWLEDGEMENTS
Development and testing of this software were made possible in part by grants from the FreeBSD Foundation and Cisco University Research Pro-
gram Fund at Community Foundation Silicon Valley.
HISTORY
The cc_vegas congestion control module first appeared in FreeBSD 9.0.
The module was first released in 2010 by David Hayes whilst working on the NewTCP research project at Swinburne University of Technology's
Centre for Advanced Internet Architectures, Melbourne, Australia. More details are available at:
http://caia.swin.edu.au/urp/newtcp/
AUTHORS
The cc_vegas congestion control module and this manual page were written by David Hayes <david.hayes@ieee.org>.
BSD September 15, 2011 BSD