vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Old VM network devices For VM network devices that are not kept up-to-date, network performance and application performance might be impacted. For more information about deploying a new virtual network device and driver, see [Choosing a network adapter for your virtual machine (1001805)](https://kb.vmware.com/s/article/1001805). 
 Virtual Machine Memory Limit Memory limits are often used. However, if a guest OS cannot access the memory that it needs, the applications inside the guest OS might perform poorly. For more information about resolving the issue, see [Configuring resource allocation settings](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-14102AB7-2CF9-42E3-9642-3EB6629EF530.html). 
 VM snapshots While snapshots are useful, the quantity and age of a VM's snapshots directly impact the performance of the VM. For more information about resolving the issue, see [Consolidate snapshots](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-2F4A6D8B-33FF-4C6B-9B02-C984D151F0D5.html). 
 VM logging When logging is not configured correctly the capacity of the datastore might be adversely impacted. For more information about resolving the issue, see [Configuring logging levels for the guest OS](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-F465D340-6556-49E8-B137-C0B4A060E83B.html).
Configuring and managing z/OS virtual server instances 

After you connect to your z/OS virtual server instance, you can perform the following additional tasks for your instance.



*  [Viewing products and services in z/OS stock images](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-viewing-products-services-in-zos-stock-images)
*  [Configuring additional disk volumes for z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=czvicv-configuring-additional-disk-volumes-zos-virtual-server-instances)
*  [Installing software products for z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-installing-software-products-zos-virtual-server-instances)
*  [Installing APARs or PTFs for z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-installing-apars-ptfs-zos-virtual-server-instances)
*  [Initiating a stand-alone dump with z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=czvicv-initiating-stand-alone-dump-zos-virtual-server-instances)
*  [Changing active I/O software configuration for z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=czvicv-changing-active-io-software-configuration-zos-virtual-server-instances)
*  [Shutting down z/OS virtual server instances](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-shutting-down-zos-virtual-server-instances)
VLANs and subnets in VMware Solutions 

The following table provides information about the subnets that are used in each VLAN. You can either order new VLANs or subnets for VMware vCenter Server® or you can select existing VLANs. You can define your firewall rules based on the subnets and ports that the network traffic goes through.

It is not recommended to put a firewall on a secondary private VLAN that has storage and vSphere® vMotion® traffic.



Table 1. Subnets for public, private, and secondary private VLANs

 Public VLAN                                                                                                                                                                                  Private VLAN                                                                                                                                                                                                                                                                                                                                                                          Secondary private VLAN                                                                                                                                                                                                                                                                         

 Primary subnet<br><br>Portable subnets<br><br><br><br> *  Management edge gateway public<br> *  Customer edge gateway public<br><br><br>  Primary subnet<br><br>Portable subnets<br><br><br><br> *  Infrastructure VMs (vCenter, NSX managers, NSX edges,  <br>    Active Directory VMs, IBM CloudDriver automation VSI)<br> *  NSX host tunnel endpoint (TEP) traffic (NSX-T™)[1]<br> *  VMware NSX® Host TEP (NSX-V)<br> *  Customer edge gateway private<br><br><br>      Portable subnets<br><br><br><br> *  vSAN™ traffic<br> *  Shared storage traffic<br> *  vMotion traffic<br> *  NSX host TEP traffic (NSX-T)[2]<br> *  NSX edge TEP traffic (NSX-T)<br> *  Customer edge TEP traffic (NSX-T)<br><br><br>      





  Related links 



*  [Ports that are used for deployment and Day 2 operations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vmwaresol_ports-deploy-day2ops)
[Subnets commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_subnets) List available subnets in your IBM Cloud infrastructure account. 
 [VLAN commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clivlan) List public and private VLANs for a zone and view the VLAN spanning status. 
 [VPCS commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_vpcs) List all VPCs in the targeted resource group. If no resource group is targeted, then all VPCs in the account are listed. 
 [Flavor commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_machine_types) Get the information of a flavor or list available flavors for a zone. 
 [Locations commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_supported-locations) List the locations that are supported by IBM Cloud Kubernetes Service. 
 [Messages commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_messages) View the current user messages. 
 [Versions commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_versions_command) List the container platform versions that are available for IBM Cloud Kubernetes Service clusters. 
 Deprecated[API commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cli_api) View or target the API endpoint and API version for the service.
The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
<-- </section "id="section-project-get-cli-options" "> --><-- <section "id="section-project-get-examples" "> --> Example ibmcloud project get --id=exampleString
<-- </section "id="section-project-get-examples" "> --><-- <section "id="section-project-get-cli-output" "> --> Example output Sample response for retrieving a project. {
"id" : "cfbf9050-ab8e-ac97-b01b-ab5af830be8a",
"crn" : "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::",
"created_at" : "2023-02-22T19:51:23.253Z",
"cumulative_needs_attention_view" : {
"event" : "project.instance.update"
}, {
"event_id" : "489f0090-6d7c-4af5-8f20-9106543e4974"
}, {
"config_id" : "069ab83e-5016-4bf2-bd50-cc95cf678293"
}, {
"config_version" : 1
} ] ! ! ! ! ,
"definition" : {
"name" : "acme-microservice",
"description" : "A microservice to deploy on top of ACME infrastructure.",
"destroy_on_delete" : true
Instantiate the ListReclamationsOptions struct and set the fields to provide parameter values for the ListReclamations method.



* Curl
* Java
* Python
* Go
* Node



curl -X GET https://resource-controller.cloud.ibm.com/v1/reclamations?account_id=b80a8b513ae24e178438b7a18bd8d609 -H 'Authorization: Bearer <IAM_TOKEN>'

ListReclamationsOptions listReclamationsOptions = new ListReclamationsOptions.Builder()
.accountId(accountId)
.build();

Response<ReclamationsList> response = service.listReclamations(listReclamationsOptions).execute();
ReclamationsList reclamationsList = response.getResult();

System.out.printf("listReclamations() response:n%sn", reclamationsList.toString());

reclamations_list = resource_controller_service.list_reclamations(
account_id=account_id
).get_result()

print('nlist_reclamations() response:n',
json.dumps(reclamations_list, indent=2))

listReclamationsOptions := resourceControllerService.NewListReclamationsOptions()
listReclamationsOptions = listReclamationsOptions.SetAccountID(accountID)
reclamationsList, response, err := resourceControllerService.ListReclamations(listReclamationsOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(reclamationsList, "", " ")
fmt.Printf("nListReclamations() response:n%sn", string(b))

const params = {
accountId: accountId,
};
Use the admin user to run one of the following commands:

PostgreSQL 10.x and newer

SELECT slot_name, pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(),restart_lsn)) AS lag, active from pg_replication_slots WHERE slot_type='logical';

PostgreSQL 9.x

SELECT slot_name, pg_size_pretty(pg_xlog_location_diff(pg_current_xlog_location(),restart_lsn)) AS lag, active FROM pg_replication_slots WHERE slot_type='logical';



If you see higher than expected disk usage on your deployment, troubleshoot by checking that your replication slot has a consumer and isn't running your deployment out of disk space.
The error occurs because the carried forward column CW.type at the top of the extract statement belongs to the view name CW, which is in the repeat element <CW.word>{1,3} of the pattern specification.

create view CapsWord as
extract 'UpperCase' as type,
regex /[A-Z]./ on 1 token in D.text as word
from Document D;

---> This results in and error due to the repeating element CW.word
create view CapsWordOneToThree as
extract CW.type as type,
pattern <CW.word>{1,3} as match
from CapsWord CW;

output view CapsWordOneToThree;

For columns that are carried forward from view names that appear in alternation or optional elements of the pattern specification, the value of the output column is null when the corresponding alternative or the optional element is not present in the text. An example that illustrates this point is in the Person view of Example 1.
* Groups that occur under a repeat element cannot be output in the return clause of the statement. For example, the following statement causes an exception:

create view CapsWordOneToThree as
extract
pattern (<CW.word>){1,3}
return group 0 as fullmatch
and group 1 as word -- not allowed due to repeat
from CapsWord CW;







 Examples 

Example 1: Sequence pattern with capturing groups

The goal of this example is to find person names by identifying occurrences of given name, optionally followed by middle initial, followed by a surname, and the entire match that is optionally preceded by a common salutation. In addition, the extractor returns the entire match as reference, the first group as salutation, and the second group as name and carry forward the values of the given name, middle initial, and surname from the respective input views.

create view MiddleInitial as
extract regex /b([p{Lu}p{M}].s){1,5}b/
on between 1 and 10 tokens in D.text as initial
from Document D;

create view Person as
extract F.first as first,
M.initial as middle,
cc7faf46-43cf-43b2-be98-7d1815371639 my-test-key-8
cf0a3d8b-4856-4aa5-be6a-88cca465eab0 my-test-key-20
df530c55-39c0-44e8-b7db-397593f70d90 my-test-key-3
e9b08526-3227-406c-b83f-c28844bd952b my-test-key-9
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5

 define a function for listing keys
$ list_keys () {
N=$1
S=$2
KEYS=$(ibmcloud kp keys --number-of-keys $N --starting-offset $S --output json | jq -r '.[] | .id')
for KEY_ID in $(echo "${KEYS}"); do
KEY_ID=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["id"]')
KEY_NAME=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["name"]')
echo $KEY_ID $KEY_NAME
done
}

 list the first group of keys
$ list_keys 5 0

10954149-0217-472d-8137-42fc330dbd03 my-test-key-16
16276369-ba81-4eb5-be92-f13512147ad4 my-test-key-14
215f592c-3e42-47b6-867c-3cc1cce8a8fd my-test-key-2
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Selector Extensions: View ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Service Authorization: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) !
768c9ceb-368b-46f7-9b1d-be211e036fe1 my-test-key-4

87679194-52d0-42af-81e1-bffd64f87315 my-test-key-7
90138be5-1dd1-4eea-b7c1-73cc8609e7f7 my-test-key-19
b70f62a1-4d52-4526-91a9-ce47bf14c2a5 my-test-key-1
b8794334-eea6-4c0d-8fe1-8086300b13f7 my-test-key-6
bc459a2f-56cb-445e-b4ee-9d1866b57560 my-test-key-11

cc7faf46-43cf-43b2-be98-7d1815371639 my-test-key-8
cf0a3d8b-4856-4aa5-be6a-88cca465eab0 my-test-key-20
df530c55-39c0-44e8-b7db-397593f70d90 my-test-key-3
e9b08526-3227-406c-b83f-c28844bd952b my-test-key-9
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5

 define a function for listing keys
$ list_keys () {
N=$1
S=$2
KEYS=$(ibmcloud kp keys --number-of-keys $N --starting-offset $S --output json | jq -r '.[] | .id')
for KEY_ID in $(echo "${KEYS}"); do
![Shows synonym recommendations for the word apple](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/entities-recommended-synonyms.png)



1. Select any synonyms you want to include, and then click Add selected.

You must click the Add selected button for any synonyms you selected to be added. If you move to the next set without clicking this button first, your selections will be lost.

The synonyms are added to your entity, and Watson suggests more synonyms.

If you receive no additional synonym recommendations, it could be because your entity is already well defined, or it contains content that the recommender is not currently able to expand upon.

If you choose not to select a recommended synonym, the system will treat that as a term you are not interested in, and will alter the next set of recommendations you see when you press Add selected or Next set. This inference only persists while you are choosing synonyms; information about skipped synonyms is not used for any other purpose by your assistant.

![Shows a set of synonym recommendations that will be added to the entity value](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/entities-synonyms-added.png)
2. Continue adding synonyms as desired. When you're finished accepting recommendations, click the X to close the recommendations panel.



4. If you want your assistant to recognize terms with syntax that is similar to the entity value and synonyms you specify, but without requiring an exact match, set the Fuzzy Matching switch to On.

For example, if you add apple as a value for a @fruit entity, and a user enters apples or appel, if fuzzy matching is enabled, your assistant will recognize the word as a @fruit mention.
You can use the following example request to retrieve a different set of keys.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys?extractable=<extractable>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the extractable variable in your request according to the following table.



Table 5. Describes the extractable variable.

 Variable Description 

 extractable The type of keys to be retrieved. Filters keys based on the extractable property. You can use this query parameter to search for keys whose material can leave the service. If set to true, standard keys will be retrieved. If set to false, root keys will be retrieved. If omitted, both root and standard keys will be retrieved. For example, if you want to only list keys with extractable material in your Key Protect instance, use ../keys?extractable=true. You can also pair extractable with offset, limit, and state to page through your available resources. 



For usage notes, check out the following examples for setting your extractable query parameter.



Table 6. Provides usage notes for the extractable query parameter.

 URL Description 

 ../keys Lists all of your available resources, up to the first 200 keys. 
 ../keys?extractable=true Lists standard keys. 
 ../keys?extractable=false Lists root keys. 







 Sorting a list of keys 

Using the sort parameter in the query string [sorts the list of keys](https://cloud.ibm.com/apidocs/key-protectkp-get-key-sort-api) returned based on one or more key properties. To sort on a property in descending order, prefix the term with "-". To sort on multiple key properties, use a comma to separate each properties. The first property in the comma-separated list will be evaluated before the next.
768c9ceb-368b-46f7-9b1d-be211e036fe1 my-test-key-4

87679194-52d0-42af-81e1-bffd64f87315 my-test-key-7
90138be5-1dd1-4eea-b7c1-73cc8609e7f7 my-test-key-19
b70f62a1-4d52-4526-91a9-ce47bf14c2a5 my-test-key-1
b8794334-eea6-4c0d-8fe1-8086300b13f7 my-test-key-6
bc459a2f-56cb-445e-b4ee-9d1866b57560 my-test-key-11

cc7faf46-43cf-43b2-be98-7d1815371639 my-test-key-8
cf0a3d8b-4856-4aa5-be6a-88cca465eab0 my-test-key-20
df530c55-39c0-44e8-b7db-397593f70d90 my-test-key-3
e9b08526-3227-406c-b83f-c28844bd952b my-test-key-9
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5

 define a function for listing keys
$ list_keys () {
N=$1
S=$2
KEYS=$(ibmcloud kp keys --number-of-keys $N --starting-offset $S --output json | jq -r '.] | .id')
for KEY_ID in $(echo "${KEYS}"); do
* You receive a message stating that the queue was not found.



5. Run end



* The runmqsc session is closed.











 Conclusion 

You've successfully:



* Connected to a queue manager using either MQ Explorer or runmqsc and have created a new test queue
* Put a test message onto the test queue
* Either browsed the the test queue to view the test message or used amqsgetc to view the test message
* Cleared and deleted the test queue to clean up







 Next steps 

Now that you have successfully learnt how to administer your queue manger using MQ explorer and runmqsc, try out the following:



* [Secured administration using MQ Explorer](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_remote_ssl_exp_admin)
* [Secured administration using runmqsc](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_remote_ssl_runmqsc_admin)
* [Connecting an application to a queue manager](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_connect_app_qm)
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5

 define a function for listing keys
$ list_keys () {
N=$1
S=$2
KEYS=$(ibmcloud kp keys --number-of-keys $N --starting-offset $S --output json | jq -r '.[] | .id')
for KEY_ID in $(echo "${KEYS}"); do
KEY_ID=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["id"]')
KEY_NAME=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["name"]')
echo $KEY_ID $KEY_NAME
done
}

 list the first group of keys
$ list_keys 5 0

10954149-0217-472d-8137-42fc330dbd03 my-test-key-16
16276369-ba81-4eb5-be92-f13512147ad4 my-test-key-14
215f592c-3e42-47b6-867c-3cc1cce8a8fd my-test-key-2
3a5a3b52-6942-463d-9f7a-5b216bbf5123 my-test-key-18
3b4b0511-00df-48e6-ad65-fad35bb6ce17 my-test-key-13

 list the second group of keys
$ list_keys 5 5

3d683d56-d340-40cb-b8b6-605dcfded01f my-test-key-15
3ee0d859-2968-4444-8e4d-3d28614f055c my-test-key-10
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5

 define a function for listing keys
$ list_keys () {
N=$1
S=$2
KEYS=$(ibmcloud kp keys --number-of-keys $N --starting-offset $S --output json | jq -r '.] | .id')
for KEY_ID in $(echo "${KEYS}"); do
KEY_ID=$(ibmcloud kp key show $KEY_ID --output json | jq -r '."id"]')
KEY_NAME=$(ibmcloud kp key show $KEY_ID --output json | jq -r '."name"]')
echo $KEY_ID $KEY_NAME
done
}

 list the first group of keys
$ list_keys 5 0

10954149-0217-472d-8137-42fc330dbd03 my-test-key-16
16276369-ba81-4eb5-be92-f13512147ad4 my-test-key-14
215f592c-3e42-47b6-867c-3cc1cce8a8fd my-test-key-2
3a5a3b52-6942-463d-9f7a-5b216bbf5123 my-test-key-18
3b4b0511-00df-48e6-ad65-fad35bb6ce17 my-test-key-13

 list the second group of keys
$ list_keys 5 5

3d683d56-d340-40cb-b8b6-605dcfded01f my-test-key-15
3ee0d859-2968-4444-8e4d-3d28614f055c my-test-key-10
In the Jobs tab in the Schematics workspace, select the job and expand the log file for a better view.
2. If the job fails to create any of the resources that are a part of the deployment, then your workspace goes to a failed state. Deployment might error out if any of the deployment values are incorrect or if there are any issues at the infrastructure level.
3. Fix the errors, and then click Apply plan again. See the following sample response of a failed deployment:



Sample response

2022/05/09 12:51:12 Terraform plan | Error: [ERROR] No SSH Key found with name ssh-key-east-new
2022/05/09 12:51:12 Terraform plan 
2022/05/09 12:51:12 Terraform plan | on main.tf line 85, in data "ibm_is_ssh_key" "compute_ssh_key":
2022/05/09 12:51:12 Terraform plan | 85: data "ibm_is_ssh_key" "compute_ssh_key" { This block is trying to fetch the key_pair details for compute node, which is dependent on the code present on public repo
2022/05/09 12:51:12 Terraform plan 
2022/05/09 12:51:12 Terraform plan 
2022/05/09 12:51:12 Terraform plan 
2022/05/09 12:51:12 Terraform plan | Error: [ERROR] No SSH Key found with name ssh-key-east-new
2022/05/09 12:51:12 Terraform plan 
2022/05/09 12:51:12 Terraform plan | on main.tf line 89, in data "ibm_is_ssh_key" "storage_ssh_key":
2022/05/09 12:51:12 Terraform plan | 89: data "ibm_is_ssh_key" "storage_ssh_key" { This block is trying to fetch the key_pair details for compute node, which is dependent on the code present on public repo
2022/05/09 12:51:12 Terraform plan
Click the link in the error to add the exception to your browser, and then hit the "invoke" button again.![test-invoke-all.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/test-invoke-all.png)





 Test with the Explore tool 

The Explore Tool allows users to test the correct operation of the API by enforcing any parameter requirements that are set in the OpenAPI definition. This enforcement is not done in the API Test Tool found in the Assemble tab, so it allows the user to verify the API behavior when the parameter is missing.



1. To test your API proxy endpoints, select Explore, then select Sandbox. ![test-explore-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/test-explore-1.png)
2. Select the Weather Provider API from the list of available APIs.
3. Select the GET /current operation from the palette.
4. Select "Try it".
5. Enter a valid U.S. zipcode (e.g. 10504) in the test box. ![test-explore-2.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/test-explore-2.png)
6. Click Call operation to see the response.