• No se han encontrado resultados

Análisis de la Rentabilidad sobre Ventas (ROS)

CAPÍTULO IV: DIAGNÓSTICO DEL PROCESO FINANCIERO

4.1. Análisis del Proceso de Gestión Financiera

4.1.5. Análisis de la Rentabilidad sobre Ventas (ROS)

In this section we provide steps to start and stop the object server, the library server and the SMS server. The object server must be shut down properly. If the object server has been stopped improperly, you cannot restart it without recovering the database. There is a utility for this; the icon is in the system administration utilities folder. The time required and result depends primarily on the size of the database.

Follow these steps for starting and stopping the servers properly.

6.4.3.1 Starting the Object Server

1. Log in as

viadmin2

, the administrative user of the object server.

2. Change the directory to /home/viadmin2/frn.

3. To set up the environment for the object server administrative user, enter:

$ . ./frnsetup.obj

4. Start the object server in the same shell and session where the object server environment is set up.

$ frnstart.obj

Recommendation: To get your prompt back, include an ampersand (&) in the command. To enable you to exit the osadmin ID and not kill your object server process, include the parameter nohup. The command would look like this:

# nohup frnstart.obj &

The output should be:

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Starting Object server with database ′OSR3′ and configuration ′IBMCONFIG FRN2310I: (OSR3) server status : Initializing

FRN2311I: (OSR3) server status : Accepting requests

 

5. Check for the server status

Accepting requests

.

6.4.3.2 Stopping the Object Server

1. Press c t r l + z in the object server session to get the command prompt.

2. Put the server process in the background by entering:

$ bg

 

(1) frnstart.obj&

 

3. Enter the command:

$ frncmd

4. You will see the following screen:

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Enter a command:

5. Connect to the object server (OSR3):

>>connect OSR3

6. Enter the

help

command at the > > prompt to receive the following menu:

 

7. Enter the

shutdown

command to bring the server down. Enter 1 to confirm, and wait for the message indicating

Server status : Down.

 

>> shutdown

FRN2032I: Enter 1 to confirm that you want to shutdown, enter anything other than 1 to cancel shutdown.

FRN2313I: (OSR3) server status : Closing FRN2033I: server shutdown initiated.

>> FRN2314I: (OSR3) server status : Down

 

8. The object server is now properly shut down.

9. Optionally, if there are orphaned processes left running, run the following command:

$ frnkill.all

10. We recommend using this procedure for proper shutdown, so keep the session accessible at the workstation.

If you need to clean up the object server processes, here is another procedure to use.

1. As root user, issue:

ps-ef | grep frn

If you see any active processes owned by viadmin1 (or 2 or 3), then VisualInfo was not stopped properly with the frncmd utility.

2. These resources can be cleaned up by issuing the command from the viadmin2 user ID:

$ frnkill.all

The output should be:

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Cleaning up system resources. Please wait.

Stopping processes. Please wait.

Cleaning up system resources. Please wait.

Successfully stopped.

 

3. You must then run the object server recovery program.

6.4.3.3 Starting the Library Server

1. Log in as

viadmin

, the administrative user for the library server.

2. Change the directory to /home/viadmin/frn.

3. Run the following script to set up the environment for library server administrative user.

$ . ./frnsetup.lib

4. To start the library server, enter:

$ frnstart.lib

The output should be:

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Starting Library server with database ′LSR3′ and configuration ′IBMCONFIG FRN2310I: (LSR3) server status : Initializing

FRN2311I: (LSR3) server status : Accepting requests

 

5. Check for the server status message

Accepting requests

.

6. To see the library server status, enter the following command from the library server session:

frncmd

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Enter a command:

7. Connect to the library server as:

>> connect LSR3

8. Enter the

help

command at the > > prompt to get this menu:

 

You can now use the interactive menu.

6.4.3.4 Stopping the Library Server

1. To stop the library server now (in the same session), enter:

>> shutdown

2. Enter 1 to confirm the shutdown:

 

>> shutdown

FRN2032I: Enter 1 to confirm that you want to shutdown, enter anything other than 1 to cancel shutdown.

FRN2313I: (LSR3) server status : Closing FRN2033I: server shutdown initiated.

>> FRN2314I: (LSR3) server status : Down

 

3. The library server is properly shut down.

4. We recommend using this procedure for proper shutdown, so keep the session accessible at the workstation.

If you need to clean up the library server processes, here is another procedure to use.

5. As root user, issue:

ps-ef | grep frn

Any active processes owned by viadmin1 (or 2 or 3) indicate that VisualInfo was not stopped properly with the frncmd utility.

6. These resources can be cleaned up by issuing the command from the viadmin2 user ID:

$ frnkill.all

The output should be:

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Cleaning up system resources. Please wait.

Stopping processes. Please wait.

Cleaning up system resources. Please wait.

Successfully stopped.

 

7. Cleanup system resources by running:

$ frnkill.all

The output should be:



VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.



(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Cleaning up system resources. Please wait.

Stopping processes. Please wait.

Cleaning up system resources. Please wait.

Successfully stopped.

 

6.4.3.5 Starting the SMS Server for Object Server

1. Log on as the user of the SMS Server,

viadmin3

. 2. Change the directory to /home/viadmin3/frn.

3. Run the following script to set up the environment for the SMS server user.

$ frnsetup.objsms

 

OK, environment set for the Object server SMS server ′OSR3′ component.

 

4. Start the SMS Server:

$ frnstart.objsms

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

FRN2057I: The SMS server is active.

FRN2055I: If you want to stop the SMS server, type stop and press Enter.

 

5. Check for a server status of

active

.

6.4.3.6 Stopping the SMS Server for Object Server

1. If you want to stop the SMS server, enter:

>>stop

from the SMS server window.

If you need to clean up the SMS server processes, here is another procedure to use.

1. As root user, issue:

ps-ef | grep frn

Any active processes owned by viadmin1 (or 2 or 3) indicate that VisualInfo was not stopped properly with the frncmd utility.

2. Set up the environment for the SMS server for object server:

$ frnsetup.objsms

3. Enter

$ frnkill.all

4. A message will confirm the server is stopped.

 

VISUALINFO VERSION 2 RELEASE 3.0 - 5697-250.

(C) COPYRIGHT IBM CORP. 1994, 1997.

ALL RIGHTS RESERVED.

US GOVERNMENT USERS RESTRICTED RIGHTS USE, DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP.

LICENSED MATERIALS - PROPERTY OF IBM

Cleaning up system resources. Please wait.

Stopping processes. Please wait.

Cleaning up system resources. Please wait.

Successfully stopped.