Scale-Out Repository availability at process start up

If a process starts whilst the regions are active and it cannot connect to a SOR, then:

• The message CASPA1000W will be displayed in the console indicating that it was not possible to connect and the reason for the failure.

In this case, you must ensure that the specified SOR is running and can be connected to from the machine hosting the region(s).

If the SOR is not the PSOR; that is, the SOR is only being used for temporary storage and/or transient data, then:

• The process will start and operate normally.
• If the SEP receives a request to access a queue whose target is that SOR, then an attempt will be made to reconnect to the SOR prior to the access attempt:
  • If this attempt is successful then the message CASPA1001I will be displayed in the console and the queue will be accessed as normal.
  • If the attempt fails then the CICS command will receive an IOERR.

In this case, you must ensure that the specified SOR is running and can be connected to from the machine hosting the region. Connection will be established automatically when required.

If the SOR being connected to is the PSOR, then:

• The process will be blocked and retry the connection.
• The message CASPA1002E will be displayed in the console.

If the process is a SEP, initiator or MPR, then it will repeatedly try to connect with increasing intervals between retries, eventually stopping and shutting down if it fails to connect.

If the process is one of the auxiliary process, such as casras, castrc, castsc, and so on, then the process will retry indefinitely or until it connects or the region(s) is shutdown.

In these cases, you must ensure that the specified SOR is running and can be connected to from the machine hosting the region(s).