vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-volume-attachment 

View details of a volume attachment.

ibmcloud is instance-volume-attachment INSTANCE VOLUME_ATTACHMENT [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* VOLUME_ATTACHMENT: ID or name of the volume attachment.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-volume-attachments 

List all volume attachments to an instance.

ibmcloud is instance-volume-attachments INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-volume-attachment-add 

Create a volume attachment, connecting a volume to an instance.

ibmcloud is instance-volume-attachment-add NAME INSTANCE (VOLUME | --profile PROFILE --new-volume-name NEW_VOLUME_NAME --iops IOPS --encryption-key ENCRYPTION_KEY --capacity CAPACITY --tags TAGS --source-snapshot SOURCE_SNAPSHOT) [--auto-delete false | true] [--output JSON] [-q, --quiet]



 Command examples
"href": "$vpc_api_endpoint/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63",
"id": "199d78ec-b971-4a5c-a904-8f37ae710c63",
"iops": 12500,
"lifecycle_state": "updating",
"name": "share-name1",
.
.
"size": 2500,
.
.
.
}

When the file share expansion completes, the new value displays, and the status is stable.

{
"created_at": "2023-07-11T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63",
"id": "199d78ec-b971-4a5c-a904-8f37ae710c63",
"iops": 12500,
"lifecycle_state": "stable",
"name": "share-name1",
"profile": {
"href": "$vpc_api_endpoint/v1/share/profiles/tier5iops",
"name": "tier-5iops",
"resource_type": "share_profile"
},
"resource_group": {
"crn": "crn:[...]",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/875623bcde2b4ebda924d32640908845",
ID 0738-933c8781-f7f5-4a8f-8a2d-3bfc711788ee
Name demo-share-update
CRN crn:v1:staging:public:is:us-south-3:a/c16d1edde3fd4a71a0130aed371405a0::share:0738-933c8781-f7f5-4a8f-8a2d-3bfc711788ee
Lifecycle State stable
Zone us-south-2
Profile tier-5iops
Size 9600
IOPS 48000
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
04165941-44c5-4e20-acde-a11c922e3415 demo-share-target 13b34e2f-5038-4a95-8fe0-966910b41b4d -
fea02493-5536-40b8-8597-e0c14e1daf4f demo-share-target2 2a5e858a-3549-4bf2-bd2a-c302bc768759 -

Resource Group ID Name
875623bcde2b4ebda924d32640908845 Default

Created 2023-02-07T02:15:52-06:00





 Expand file share capacity with the API 

You can expand existing file shares by calling the VPC API.

As described in the [Beta VPC API](https://cloud.ibm.com/apidocs/vpc-beta) reference [versioning](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta) policy, support for older versions of the beta API is limited to 45 days. Therefore, beta API requests must specify a version query parameter date value within the last 45 days. You must also provide generation parameter and specify generation=2.
app: wasliberty
spec:
affinity:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
podAffinityTerm:
labelSelector:
matchExpressions:
- key: app
operator: In
values:
- wasliberty
topologyKey: kubernetes.io/hostname
containers:
- name: wasliberty
image: icr.io/ibm/liberty:latest
env:
- name: VERSION
valueFrom:
configMapKeyRef:
name: wasliberty
key: VERSION
- name: LANGUAGE
valueFrom:
configMapKeyRef:
name: wasliberty
key: LANGUAGE
- name: username
valueFrom:
secretKeyRef:
name: wasliberty
key: username
- name: password
valueFrom:
secretKeyRef:
name: wasliberty
key: password
ports:
- containerPort: 9080
resources:
requests:
memory: "512Mi"
cpu: "500m"
limits:
memory: "1024Mi"
cpu: "1000m"
livenessProbe:
httpGet:
path: /
port: 9080
initialDelaySeconds: 300
periodSeconds: 15
readinessProbe:
httpGet:
path: /
port: 9080
initialDelaySeconds: 45
periodSeconds: 5
volumeMounts:
- name: pvmount
mountPath: /test
volumes:
- name: pvmount
persistentVolumeClaim:
claimName: wasliberty
---

apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
name: wasliberty
spec:
maxUnavailable: 1
selector:
matchLabels:
"id": "2d1bb5a8-40a8-447a-acf7-0eadc8aeb054",
"IOPS": 100,
"name": "my-volume-1",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/volume/profiles/general-purpose",
"name": "general-purpose"
},
"resource_group": {
"href": "https://resource-manager.bluemix.net/v1/resource_groups/83daf012-5920-4ba9-9689-cc0d2d2281fb",
"id": "83daf012-5920-4ba9-9689-cc0d2d2281fb",
"name": "Default"
},
"status": "available",
"volume_attachments": [{
"delete_volume_on_instance_delete": true,
"device": {
"id": "4cbb38bc-57d5-4121-a796-d5b10cf0810a"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5/volume_attachments/4cbb38bc-57d5-4121-a796-d5b10cf0810a",
"id": "<4cbb38bc-57d5-4121-a796-d5b10cf0810aAttachment ID>",
"instance": {
"crn": "crn:...]",
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response

HTTP/1.1 200 OK
Date: Wed, 24 Aug 2016 17:46:35 GMT
X-Clv-Request-Id: 0c2832e3-3c51-4ea6-96a3-cd8482aca08a
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.115
X-Clv-S3-Version: 2.5
x-amz-request-id: 0c2832e3-3c51-4ea6-96a3-cd8482aca08a
Content-Length: 0

Example request

HEAD requests on buckets with Key Protect encryption will return extra headers.

HEAD /secure-files HTTP/1.1
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Authorization:Bearer {token}

Example request

HEAD /secure-files HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response

HTTP/1.1 200 OK
Date: Wed, 24 Aug 2016 17:46:35 GMT
X-Clv-Request-Id: 0c2832e3-3c51-4ea6-96a3-cd8482aca08a
Microsoft PowerPoint .ppt application/vnd.ms-powerpoint 
 .pptx application/vnd.openxmlformats-officedocument.presentationml.presentation 
 Microsoft Word .doc application/msword 
 .docx application/vnd.openxmlformats-officedocument.wordprocessingml.document 



Microsoft, Microsoft Excel, Microsoft Office, Microsoft PowerPoint, and Microsoft Word are trademarks of the Microsoft group of companies.





 Open Office file formats 

Table 2 lists the Open Office file formats that the service supports for translation.



Table 2. Open Office file formats

 File format File extension Content type 

 Open Office Calc .ods application/vnd.oasis.opendocument.spreadsheet 
 Open Office Impress .odp application/vnd.oasis.opendocument.presentation 
 Open Office Writer .odt application/vnd.oasis.opendocument.text 







 Subtitle file formats 

Table 3 lists the subtitle (or caption) formats that service supports for translation. These textual formats contain the transcript of a sound track or video source. The formats provide plain text that is intuitively comprehensible with minimal syntax. They include a list of cues that contain synchronization information for the media source. They can also include metadata that is not intended for display.

The table shows both the file extension and the content type for all subtitle formats. However, in some cases you must specify one or the other. The table makes clear where the file extension or the content type is needed. Also, for the .sub file extension, which is used for multiple formats, the service parses the file to determine the exact subtitle format of the file.



Table 3. Subtitle file formats

 File format File extension Content type 

 Apple® iTunes® Timed Text .itt <br>The file extension is required application/xml 
 DirectVobSub .sub <br>The file extension is required text/plain 
 Distribution Format Exchange Profile .dxfp <br>The file extension is sufficient application/ttaf+xml 
 .xml application/ttaf+xml <br>The content type is required
"href": "https://us-south.iaas.cloud.ibm.com/v1/volume/profiles/general-purpose",
"name": "general-purpose"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
"id": "4bbce614c13444cd8fc5e7e878ef8e21",
"name": "Default"
},
"status": "available",
"status_reasons": ],
"user_tags": ],
"volume_attachments":
{
"delete_volume_on_instance_delete": true,
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/33bd5872-7034-462b-9f3e-d400c49d347a/volume_attachments/b31c1a5a-122a-4e32-a10b-f2c31271de85",
"id": "b31c1a5a-122a-4e32-a10b-f2c31271de85",
"instance": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/33bd5872-7034-462b-9f3e-d400c49d347a",
"id": "33bd5872-7034-462b-9f3e-d400c49d347a",
"name": "instance-1",
"resource_type": "instance"
},
"name": "volume-attachment-1",
})
.catch(logError);
}

// Multi part upload
function multiPartUpload(bucketName, itemName, filePath) {
var uploadID = null;

if (!fs.existsSync(filePath)) {
logError(new Error(The file '${filePath}' does not exist or is not accessible.));
return;
}

return new Promise(function(resolve, reject) {
console.log(Starting multi-part upload for ${itemName} to bucket: ${bucketName});
return cos.createMultipartUpload({
Bucket: bucketName,
Key: itemName
}).promise()
.then((data) => {
uploadID = data.UploadId;

//begin the file upload
fs.readFile(filePath, (e, fileData) => {
//min 5MB part
var partSize = 1024 * 1024 * 5;
var partCount = Math.ceil(fileData.length / partSize);

async.timesSeries(partCount, (partNum, next) => {
var start = partNum * partSize;
var end = Math.min(start + partSize, fileData.length);

partNum++;

console.log(Uploading to ${itemName} (part ${partNum} of ${partCount}));

cos.uploadPart({
Body: fileData.slice(start, end),
Bucket: bucketName,
Key: itemName,
PartNumber: partNum,
UploadId: uploadID
}).promise()
.then((data) => {
next(e, {ETag: data.ETag, PartNumber: partNum});
})
.catch((e) => {
cancelMultiPartUpload(bucketName, itemName, uploadID);
To add a replica, define the replica share similarly to the following example. It creates a share with 220 GB capacity and the tier-3iops performance profile. The replica_share argument defines the replica share's name, the frequency of replication (in cron spec), the performance profile, and the zone where the replica share is to be created.

resource "ibm_is_share" "example-2" {
zone = "us-south-1"
size = "220"
name = "my-share"
profile = "tier-3iops"
replica_share {
name = "my-replica"
replication_cron_spec = "0 /5 * * "
profile = "tier-3iops"
zone = "us-south-3"
}
}





 Creating a file share with a mount target with VPC-wide access mode 

To create a file share with a mount target that is accessible to all virtual server instances within a VPC, use the ibm_is_share resource. Specify the access control mode as vpc, and define the mount target by providing a name for it and the VPC where it's going to be used in.

resource "ibm_is_share" "share3" {
zone = "us-south-2"
size = "700"
name = "my-share3"
profile = "tier-3iops"
access_control_mode = "vpc"
mount_target {
name = "target"
vpc = <vpc_id>
}
}





 Creating a file share with a mount target with security group access mode 

To create a file share with a mount target that allows for security group-based authentication within a VPC, use the ibm_is_share resource. Specify the access control mode as security_group, and define the mount target by providing a name for it, details of the virtual network interface such as name, subnet, or IP address. Also, specify the security groups that you want to use to control access to the file share.

resource "ibm_is_share" "share4" {
zone = "us-south-2"
This stanza indicates the minimum size in megabytes of the required volume in a SIZE_MB = size key value pair. The recorded size is used when creating the alternate disk image volume and attaching it to the _helper VM.

The restore -qf command:

 restore -qf gdrh10v1.sysb ./bosinst.data
x ./bosinst.data
 grep -p target_disk_data bosinst.data
target_disk_data:
PVID = 00c04e279d9ce46e
PHYSICAL_LOCATION = U9117.MMC.0604E27-V9-C3-T1-L8100000000000000
CONNECTION = vscsi0//810000000000
LOCATION =
SIZE_MB = 20480
HDI SKNAME = hdisk0

To create and attach a new volume to AIX-7200-03-03, complete the following steps:



1. Click Add new under Attached volumes.
2. Create a data volume and enter the recorded size in gigabytes (it must be large enough to hold the restored root volume group) by selecting the correct options. For example, you can enter the volume name as AIX-7200-03-03-altdisk.
3. After successfully attaching the AIX-7200-03-03-altdisk volume to the helper VM, log on to the VM. Use the cfgmgr and lspv commands on the helper VM to show the new disk. The new disk is named hdisk2.



Displaying storage information:

 cfgmgr
 lspv
hdisk0 00f6db0a6c7aece5 rootvg active
hdisk1 00c25ab0056a002a mksysbvg active
hdisk2 none None






 Restoring the alternate disk mksysb 

You can now create an AIX boot disk from the source mksysb archive. To create an AIX boot disk from the source mksysb archive, run the alt_disk_mksysb command with the following options:
Make a GET /shares request to list all file shares for a region.

curl -X GET "$vpc_api_endpoint/v1/shares?version=2023-07-05?limit=50&generation=2&maturity=beta" -H "Authorization: $iam_token"

A successful response looks like the following example. In the example, the limit query parameter specifies a limit of 50 file shares, all though there is only one in the response. The access_control_mode property value is vpc, which means that the file share can be mounted on all virtual server instances in a VPC.

{
"first": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares?limit=50"
},
"limit": 50,
"shares": [
{
"access_control_mode": "vpc",
"created_at": "2023-07-05T13:02:17Z",
"crn": "crn:...]",
"encryption": "provider_managed",
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/51bba578-0dce-4f8a-aa6e-f06c899e2c8e",
"id": "51bba578-0dce-4f8a-aa6e-f06c899e2c8e",
"iops": 3000,
"lifecycle_state": "stable",
"name": "share-name1",
"profile": {
"family": "tiered",
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/tier-10iops",
"name": "tier-10iops",
"resource_type": "share_profile"
},
"resource_group": {
"create_target": true,
"source": { "url": "'"$SOURCE_SERVICE_URL/source"'" },
"target": {
"auth": { "iam": { "api_key": "'"$API_KEY"'" } },
"url": "'"$TARGET_SERVICE_URL/target"'"
}
}'

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.PutReplicationDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabase;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabaseAuth;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabaseAuthIam;
import com.ibm.cloud.cloudant.v1.model.ReplicationDocument;

Cloudant service = Cloudant.newInstance();

ReplicationDatabase sourceDb = new ReplicationDatabase.Builder()
.url("<your-source-service-url>/source")
.build();

ReplicationDatabaseAuthIam targetAuthIam =
new ReplicationDatabaseAuthIam.Builder()
.apiKey("<your-iam-api-key>")
.build();

ReplicationDatabaseAuth targetAuth = new ReplicationDatabaseAuth.Builder()
.iam(targetAuthIam)
.build();

ReplicationDatabase targetDb = new ReplicationDatabase.Builder()
.auth(targetAuth)
.url("<your-target-service-url>/target")
.build();

ReplicationDocument replDocument = new ReplicationDocument();
Product guide 

 IBM Cloud Load Balancer 

--------------------



* Get started



* [Getting started with IBM Cloud Load Balancer ](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-getting-started)
* [About IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-about-ibm-cloud-load-balancer)
* [Load balancer basics](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-ibm-cloud-load-balancer-basics)
* [Exploring IBM Cloud load balancers](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-explore)
* [Demo: Network as a service](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-naas-video)
* [Other resources for IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-other-resources-for-ibm-cloud-load-balancer)
* [What is load balancing?](https://www.ibm.com/cloud/learn/load-balancing)
* [Release notes for IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-loadbalancer-service-release-notes)



* Tutorials



* Classic infrastructure



* [Hosting web applications from a secure private network](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-web-app-private-network)





* How to



* Using an elastic load balancer for server load balancing
Locating your Db2 Warehouse on Cloud credentials 

To find alternatives to IBM Cloudant's IBM® Db2® Warehouse on Cloud feature, see the [data-flow-examples repository](https://github.com/cloudant-labs/data-flow-examples) for tutorials on extracting IBM Cloudant documents and writing the data to a Db2 Warehouse on Cloud table.

This tutorial shows you how to find your Db2 Warehouse on Cloud credentials. Keep in mind that the Db2 Warehouse on Cloud feature is deprecated.

Before you can sign in to the Db2 Warehouse on Cloud console, you need the URL and credentials. This information is located in the warehouser document.



 Objectives 



1. Locate your Db2 Warehouse on Cloud credentials.
2. Sign in to Db2 Warehouse on Cloud console.







 Step 1: How to find your service credentials 



1. To retrieve information from the warehouser document, you must run the following curl command.

curl -u $USERNAME:$PASSWORD "https://$ACCOUNT.cloudant.com/_warehouser/$DOCUMENT_ID"
2. Before you run the command, replace $DOCUMENT_ID with example@source-db. In this case, example is the warehouser document's name. source-db is the source database's name that is used for replicating IBM Cloudant to DB2.

curl -u $USERNAME:$PASSWORD "https://$ACCOUNT.cloudant.com/_warehouser/example@source-db"
3. See the example response when you search for information in the warehouser document.

{
"_id": "example@source-db",
"dashboard_url": "https://dashdb-entry-yp-lon02-01.services.eu-gb.bluemix.net/login",
"dynamite_token": "XXXXXXXX",
"target": "jdbc:db2://dashdb-entry-yp-lon02-01.services.eu-gb.bluemix.net:50000/BLUDB",
"target": "https://ble...igl:YPN...Tfi@myaccount-dc2.cloudant.com/mydb",
"continuous": true
}'

Next, create a replication from database myaccount-dc2.cloudant.com/mydb to database myaccount-dc1.cloudant.com/mydb.

curl -XPOST "https://myaccount-dc2.cloudant.com/_replicator"
-u myaccount-dc2
-H "Content-Type: application/json"
-d '{ "_id": "mydb-myaccount-dc2-to-myaccount-dc1",
"source": "https://ble...igl:YPN...Tfi@myaccount-dc2.cloudant.com/mydb",
"target": "https://ble...igl:YPN...Tfi@myaccount-dc1.cloudant.com/mydb",
"continuous": true
}'

If this step fails because the _replicator database doesn't exist, create it.





 Step 5. Test your replication 

Test the replication processes by creating, modifying, and deleting documents in either database.

After each change in the database, check that you can also see that change in the other database.





 Step 6. Configure your application 

The databases are set up to remain synchronized with each other.

The next decision is whether to use the databases in an [active-active](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-configuring-ibm-cloudant-for-cross-region-disaster-recoveryactive-active) or [active-passive](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-configuring-ibm-cloudant-for-cross-region-disaster-recoveryactive-passive) manner.



 Active-active
Getting started with IBM Cloud Load Balancer 

The IBM Cloud® Load Balancer service helps customers improve availability of their business-critical applications by distributing traffic among multiple application server instances, and by forwarding traffic to healthy instances only.

To get started using IBM Cloud® Load Balancer, you require two main items:



*  An account with IBM - [IBMid](https://www.ibm.com/account/us-en/signup/register.html)
*  An IBM server, either [Bare Metal](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-getting-started) or [Virtual Server Instance (VSI)](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-getting-started-tutorial)



If you need assistance in obtaining an IBMid account, contact your IBM Sales representative for additional guidance.



  Ordering a load balancer 

To get started with IBM Cloud® Load Balancer, see [Using an elastic load balancer for server load-balancing overview](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-creating-and-using-an-ibm-cloud-load-balancer-for-elastic-server-load-balancing).
'api_key': '<your-iam-api-key>'
}
},
url: '<your-target-service-url>/target'
};

const replDocument: CloudantV1.ReplicationDocument = {
id: 'repldoc-example',
continuous: true,
create_target: true,
source: sourceDb,
target: targetDb
}

service.putReplicationDocument({
docId: 'repldoc-example',
replicationDocument: replDocument
}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1, ReplicationDocument, ReplicationDatabase, ReplicationDatabaseAuthIam, ReplicationDatabaseAuth

service = CloudantV1.new_instance()

source_db = ReplicationDatabase(
url='<your-source-service-url>/source'
)

target_auth_iam = ReplicationDatabaseAuthIam(
api_key='<your-iam-api-key>'
)
target_auth = ReplicationDatabaseAuth(
iam=target_auth_iam
)
target_db = ReplicationDatabase(
auth=target_auth,
url='<your-target-service-url>/target'
)

replication_document = ReplicationDocument(
id='repldoc-example',
continuous=True,
create_target=True,
source=source_db,
target=target_db
)

response = service.put_replication_document(
doc_id='repldoc-example',
replication_document=replication_document
).get_result()

print(response)

source, err := service.NewReplicationDatabase(
"seq":"11-g1A...c1Q",
"id":"6f8ab9fa52c117eb76240daa1a55827f",
"changes":[
{
"rev":"1-619d7981d7027274a4b88810d318a7b1"
}
]
}

To join the changes feed from a known position, pass a [since argument](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-databasesthe-since-argument) with the sequence number you want to start from.

See the following example (abbreviated) that uses HTTP to supply the since option to join a _changes feed at a known position:

GET /$DATABASE/_changes?feed=continuous&include_docs=true&since=11-g1A...c1Q HTTP/1.1
HOST: $SERVICE_URL
Authorization: ...

See the following example (abbreviated) that uses the command line to supply the since option to join a _changes feed at a known position:

curl "$SERVICE_URL/$DATABASE/_changes?feed=continuous&include_docs=true&since=11-g1A...c1Q"

To rejoin the changes feed from the current moment in time, set since=now.

See the following example that uses HTTP to supply since=now to join a _changes feed at the current moment in time:

GET /$DATABASE/_changes?feed=continuous&include_docs=true&since=now HTTP/1.1
Host: $SERVICE_URL
Authorization: ...

See the following example that uses the command line to supply since=now to join a _changes feed at the current moment in time:

curl "$SERVICE_URL/$DATABASE/_changes?feed=continuous&include_docs=true&since=now"

Accessing the _changes data programmatically is straightforward.