AS400 CISC TO RISC???
Enrique Machado
Can anyone provide any details on coverting from CISC to RISC? I am
working with a company now who needs a consultant to help with this
conversion. Apparently this is all in an AS400 environment. Is this
an unusual requirement or do you AS400 people do this all the time?
If you guys can point me to somebody who has done this before, there's
a referral bonus in it for you.
Thanks,,
Rick Machado
ComSys
ph:888.717.7266
HAPPY HOLIDAYS
John I. Bishop
Try the online version of the "AS/400 Road Map for Changing to PowerPC
Technology",
SA41-5150-00 at the following URL:
http://AS400BKS.rochester.ibm.com:80/cgi-bin/bookmgr/BookMgr.cmd/DOCNUM/SA41-5150/CCONTENTS
John Bishop
AS/400 Technical Studio Team
danh...@millcomm.com
In <5EBF100672E52E64.E524DEB8...@library-proxy.airnews.net>, emac...@comsysinc.com (Enrique Machado) writes:
>Can anyone provide any details on coverting from CISC to RISC? I am
>working with a company now who needs a consultant to help with this
>conversion. Apparently this is all in an AS400 environment. Is this
>an unusual requirement or do you AS400 people do this all the time?
>If you guys can point me to somebody who has done this before, there's
>a referral bonus in it for you.
Basically it's just a hardware/software release upgrade, but you need to
do some checks before you start to make sure that all of your code is
"observable" so that it can be converted. There is a "roadmap" document
you can get from IBM that gives a step-by-step procedure.
Dan Hicks
Hey!! My advice is free -- take it for what it's worth!
http://www.millcomm.com/~danhicks
Robin Chakravarti
Enrique Machado <emac...@comsysinc.com> wrote in article
<5EBF100672E52E64.E524DEB8...@library-proxy.airnews.ne
t>...
> Can anyone provide any details on coverting from CISC to RISC? I am
> working with a company now who needs a consultant to help with this
> conversion.
<snip>
Hi Enrique:
I have converted CISC to RISC in > 1 location, including my own companies
large software packages, which get shipped to multiple customers. There is
_no_ problem converting software - you just SAVLIB on the CISC & RSTLIB on
the RISC! This simple solution is subject to the "observability" being
available,as Dan Hicks mentions in his response. And yes, AS/400 people do
this all the time -- most OS/400 releases (with certain shining recent
exceptions) are rock solid.
Basically, "observability" is tokenized code embedded in the object by the
compiler; the RISC Restore program determines that this is CISC code and
_recompiles_ it on the fly, giving you full 64-bit code! If it is u r own
software, it should be observable by default -- if it is package
software,some (paranoid) software suppliers remove observability.
ObAside: It is bad business practice to deal with observability-removing
software goofs^H^H^H^Hsuppliers. These guys are dimwitted hacks working
under the assumption that their code is _so_ unique that you would reverse
engineer it via the observability function and steal their precious ideas.
Most of them write such rotten code that you'd be stupid to waste your time
reverse engineering their junk. In any case, if they are so smart. how come
they're still on CISC?
Your _biggest_ problem is porting your machine configurations (security
profiles, jobq, outq, etc.) over to the CISC machines. Most people buy a
new RISC box, so this too is esentially SAV & RST solution, but you do have
to be organized. The IBM "roadmap" mentioned in the earlier replies will
help. My own (humble, personal, based on an early release) opinion is that
it is _IBMawful_. 200 pages to tell you how to turn a page. However, it is
highly organized and will help organ you (if u know what I mean).
My own opinion: unless you are a real newbie, you don't need no stinkin'
consultant.
Hope this helps & cheers,
Robin Chakravarti
"This advice is worth every penny you have paid for it."