Just to echo what everyone else is saying, VS FORTRAN is licensed
per-machine, not per-LPAR.
Your work may already be done, in other words. I concur with the advice to
ask an IBM rep. He/she should be able to tell you what impact (if any)
there would be if you take a certain action. There are a fe
On Wed, 12 Nov 2008 19:57:32 +, Bill Wilkie <[EMAIL PROTECTED]> wrote:
>You may also want to consider renaming them first to make sure nobody is
referencing them in JCL, procs, or subroutines. After a a few days with no
incidents, then remove them.
>
>Bill
Another possibility, if you cannot
You may also want to consider renaming them first to make sure nobody is
referencing them in JCL, procs, or subroutines. After a a few days with no
incidents, then remove them.
Bill
> Date: Wed, 12 Nov 2008 16:48:19 +0100> From: [EMAIL PROTECTED]> Subject: Re:
> Removing
Hi,
additionaly you should remove the FORTRAN libraries from your SMP/E
environment by installing a ++DELETE - function, if you have a separate
SMP/E environment for this LPAR. Otherwise you may get service for this
product in future.
Jacky Bright schrieb:
Hi,
I guess slowdown started affe
---
I guess slowdown started affecting us...my manager asked me to remove VS
Fortran V2 Compiler/Library from one legacy LPAR so that license cost
can be saved.
Can anyone help me how can we remove this software from mainframe ? How
to go ab
Jacky Bright wrote:
Hi,
I guess slowdown started affecting us...my manager asked me to remove VS
Fortran V2 Compiler/Library from one legacy LPAR so that license cost can be
saved.
Can anyone help me how can we remove this software from mainframe ? How to
go about this ?
Fill CoD (Certificate
Hi,
I guess slowdown started affecting us...my manager asked me to remove VS
Fortran V2 Compiler/Library from one legacy LPAR so that license cost can be
saved.
Can anyone help me how can we remove this software from mainframe ? How to
go about this ?
JAcky
-
7 matches
Mail list logo
